> 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.md).

# Listings

## How to: Create a new and importantly ‘great’ listing

* Do strong and thorough research to obtain the information for a comprehensive [listing](https://make.works/companies)
* Exercise quality control across all your listings, e.g. double check technical terms, ensure file qualities are as required
* Use clean, straightforward, jargon free language
* Use succinct and clear information, that has been spell checked and proof read
* Ensure your photographs, and if you are using film, are well edited, cropped, etc.
* Use tags to their strengths. Ensure you conduct thorough searches of the terms to enable appropriate selection of tags for the listing you are working on and to inform your suggestion of a new term

We recommend keeping your own copy of your research and information for factory listings.


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.
