> 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/communications/how-to-use-make-works-stories.md). # How to: Use Make Works' Stories Make Works [Stories](https://make.works/blog) is the place where we chose to share research, experiences and inspiration with our community. From Google Analytics and our knowledge we know Stories not only inform Make Works' users, they are also the primary entry point for traffic to [Make Works](https://make.works/). This is due to the opportunity of Stories’ content aiding SEO. Now this doesn’t mean that Stories should be written purely for SEO, however it is something to be considered to enable web users who are looking to access local manufacturing to find your Make Works region and its factory listings. See ‘How to: Optimise your content (SEO)’ below. Stories categories are: * Article * Made Works * Introducing Make Works * How to Guides * Inspiration * Bookshelf Examples of possible Stories to inspire you to write some for your region are: * Interview with a factory owner * Insight into a factory’s process, machinery, specialist skill / capabilities * Top 5 – who doesn’t love a top 5, e.g. suppliers, factories who work with a material * Review of your recent activity, e.g. projects, research, engagement with your community * Case study of where Make Works has made a difference, e.g. enabled a maker to realise a project, introduced a skill / process / piece of equipment in a factory to a new user / creative * Engagement with national / regional / local opportunities – e.g. Wool Week, Maker Month, Maker Faire, etc. * Insight into what you have been reading – e.g. books, reports, blog posts, perhaps more than one on a topic * Demystifying jargon – explaining e.g. processes, materials, techniques to enable users to access information and be inspired to use it Stories should be sent to Make Works coordination before posting. Please send edited and proof ready copy, with high res format images to . The Make Works Coordination Team will edit Stories for style. After that the Story can be either posted directly by you or the Coordination Team. ## FAQ * **Why should we submit content for Stories?** \ \ Stories are not only informational but they are an important gateway to the website and in fact are the main entry point for all traffic on the Make Works website. They are also a great way to profile (and say thanks to) the amazing people and companies you work and engage with, whether factories, individual creatives, funders or partners! --- # 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/communications/how-to-use-make-works-stories.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.