> For the complete documentation index, see [llms.txt](https://contentbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://contentbox.ortusbooks.com/usage/using-contentbox/content/consume-content/content-store.md).
# Content Store
The Content Store allows you to create reusable elements, which can be rendered in Pages, Entries, or other Content Store items
Often, there are items which a user wishes to be dynamic in a content layout, template or even a custom view. The ContentBox Content Store allows you to create and group these reusable elements.
Let's say, for example, that you wish to include a block of Contact information in the footer of your site. You could code that directly in to your [Layout](/font-end-development/theme-development/theme-layouts.md), but by using the Content Store, you make that content easily editable by Editors and Administrators of your site.
To create Content Store custom content, navigate to Content > Content Store in the sidebar menu and click the "Create Content" button. Then provide your custom content in the editor.
Note the `slug` value in the editor. You will use this slug to retreive the custom content item in your layout.
Open your them layout or footer view and insert the custom content reference using the shorthand annotation like so:
`{{{ContentStore slug='contact-information' }}}`
Now your Content Store item will render in the footer of your site theme and can easily be changed from within the administration
---
# 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://contentbox.ortusbooks.com/usage/using-contentbox/content/consume-content/content-store.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.
