> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/guidebook-design-principles.md). # Guidebook Design Principles ## Define a Clear Set of Phases A project may require all four project phases or a subset, but the starting point for the project, subsequent phase deliverables, and final deliverable should be clear and consistent. ## Design for an Appropriate Level of Complexity and Knowledge Each project should carefully consider the readiness of the target students and provide the needed scaffolding and technical support to be successful. ## Maximize Technology Accessibility Specify the technological needs to match the expected accessibility of students. Recognize that the most successful entry level projects will limit the needs to an Internet-connected computer with a standard browser. ## Create Engaging Contexts and Goals Create a project having a context and general goals that engage student interests while looking for any opportunity to inject social relevance into the project. ## Use State of the Art Techniques and Knowledge Provide a project path that employs the current practices and technology applied in industry today or in the foreseeable future. ## Develop Templates and Code Libraries Provide clear templates or examples for each deliverable and develop any code templates or libraries needed to make the technology accessible for the target students. ## Support Interdisciplinary Skills Each project should provide a measure of breadth in the skills needed to complete each phase that reflect the interdisciplinary teams found in industry. --- # 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://docs.launchboard.app/cxd/guidebook-design-principles.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.