> For the complete documentation index, see [llms.txt](https://program.hackyourfuture.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://program.hackyourfuture.dk/course-content/frontend/final-project/session-plan.md). # Session Plan ## Week 1: Team Formation & Ideation * Form teams and participate in an ideation session. * Collaborate to agree on a project idea and define the core concept. ## Week 2: Planning & Foundation * Expand ideas into a structured plan. * Divide tasks among teammates and begin building the project foundation. * We will use Trello to track tasks and progress. ## Week 3: Development & Refinement * Focus on adding features and complexity to the application. * Dedicate time to resolving errors, bugs, and merge conflicts. ## Week 4: Mid-Project Demo * Prepare a short progress demo. * Goal: Share initial goals, progress so far, a live demo, and next steps. ## Week 5: Finalization, Deployment & Presentation Prep * Complete the project and ensure it is fully deployed. * Enter a code freeze (no new features). * Use this week to build your demo and slides. * In this workshop we help you to learn best practices and prepare effectively. * Presentation workshop to prepare for graduation. ## Graduation Day: Final Presentation * Each team will be given a specific time limit for their presentation. This duration will be communicated during the session itself. * Every member must speak. As a team, you are responsible for dividing the presentation topics so that each person explains one part of the process. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://program.hackyourfuture.dk/course-content/frontend/final-project/session-plan.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.