# How we documented the prototypes The documentation is following the best practices of good documentation in the "maker communities" (see also the section: Sharing documentation how to facilitate replicability of processes and results of the [opencare Maker Playbook](https://makerplaybook.opencare.cc/).) The documentation is released using a lot of the features available on Github where many of the open source projects are made public and open to collaboration. All **websites** are based on Jekyll ( a simple, blog-aware, static site generator for personal, project, or organization sites distributed under an open source license) and GitHub Pages (a static site hosting service by Github). This combination of a publishing system and hosting makes it easy to: * keep project's documentation and actual project files in the same place, the repository, thanks to GitHub Pages * create and publish a variety of content in an easy-to-use language (markdown) and arrange the site layout to match the project's needs, thanks to Jekyll (see also: [https://github.com/opencarecc/MicroWebsiteTemplate/wiki/](https://github.com/opencarecc/MicroWebsiteTemplate/wiki)) * foster contributions by a wider audience --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://wemakecc.gitbook.io/d3-2-full-documentation-of-all-prototypes/how-we-documented-the-prototypes/how-we-documented-the-prototypes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.