> For the complete documentation index, see [llms.txt](https://books.fablabbcn.org/make-works/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://books.fablabbcn.org/make-works/listings/checklist-for-creating-a-listing.md). # Checklist: For creating a listing Returning from your factory visit, you will have a lot of raw data in the form of notes, answers to questions about what they do, how, why, when and what, plus photographs and desired film footage. This checklist will help you turn all that into a listing: * Spend time with your notes and answers to questions as soon as you can after the factory visit to ensure they are fresh in your mind * Write up your notes and answers to questions: * follow up on / research any unknowns to ensure your notes are correct and accurate * check your facts! * map the information on the listing editor to double check you have everything you need to complete it * Ensure the photographer has all they need for post production to realise great images to feature in the listing * Ensure the film team have all they need for post production to realise a great film for the listing – raw footage, reminder of the film brief, your direction, etc. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://books.fablabbcn.org/make-works/listings/checklist-for-creating-a-listing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.