# Content Introduction

### No Content - All About the Project

The Full Stack Circle focuses entirely on working on a project. That also means there is little content being shared with the students. The first three sessions help introduce students to concepts (how to collaborate, team building, and setup). Besides that, we share material ad-hoc if needed to solve a specific issue.&#x20;

### Project Setup

Students can choose which platform or website to clone. This approach allows teams to work on a project they're genuinely interested in while learning essential full-stack development skills. Last semester, the students cloned Pinterest ([GitHub Repo](https://github.com/ReDI-School/S25-Full-Stack-Circle)).

### Requirements for the Project

#### The final product that we want to produce:

1. A project with a frontend communicating with a backend connected to a data store, transmitting data back and forth and modifying data on the backend
2. The project represents an understanding of testing, debugging and clean code principles
3. One meaningful visual test and one meaningful behavior/unit test set
4. One meaningful complexity level apart from a plain backend/frontend communication (ex.: maps, complex auth, 3rd party API integration, realtime comms)
5. Log of tickets/cards/milestones in the project

### Project Setup

Once a platform is selected (in the first 3 weeks), we define the initial set of tickets and establish the project structure, ensuring a solid foundation for development (a volunteer PM named Stefan helps us with this!). The project will be broken down into manageable sprints, each focusing on recreating specific features of the chosen platform.&#x20;

***

Let's complete the self-onboarding now: [Complete your Self-Onboarding](../../../self-onboarding)
