> For the complete documentation index, see [llms.txt](https://docs.mburger.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mburger.cloud/api-docs-1/going-deeper/available-elements.md). # Available Data Types (Elements) The following table contains all available elements. | Element | Description | | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Text | Simple text field like a title. | | Textarea | Longer multiline text field like a content or a description. | | Markdown | It's like a textarea but supports all markdown features. | | Checkbox | Checkbox that can assume 2 states. | | Image | An image file. | | Audio | An audio file. | | Video | A video file. | | Document | A readable document file like .txt, .docx, .pptx etc. | | File | A generic file like .zip, .ipa, .apk etc. | | Datetime | Field containing a datetime. | | Address | Text field containing an address with automatic reverse geocoding to retrieve the coordinates. | | Dropdown | Dropdown with multiple choices, of which only one is selectable. | | Multiple | Similar to Dropdown but you can select multiple values. | | Relation | With this element you can create relations between your data. | | SEO | For every section, it is possible to specify SEO meta fields. | | Multiple | With multiple select element you can easily set multiple choices. This component is ideal for add categories inside a blog or segment the clients where you want to spread out your contents. | | Color | With color picker element you can easily choose a color in hex format. | | Custom | With Custom element you can easily add any data to your sections. | ## SEO With the SEO element, it is possible to specify several meta fields such as title, description, keywords and image. In this way, you can take advantage of SEO optimizations performed by search engines to better index your content. An API response example: ```bash "value": { "title": "SEO Title", "keywords": ["Some", "SEO", "keywords"], "description": "SEO Description", "image": { "id": 1, "url": "https://cdn.mburger.cloud/storage/1/conversions/image-medium.jpg", "size": 45166, "mime_type": "image/jpeg" } } ``` ## Slug Slug element is present by default and allows a specification of a textual ID for sections. It can be used to request sections instead of a classic numeric ID. An API response example: ```bash "value": "slug-of-your-section" ``` --- # 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://docs.mburger.cloud/api-docs-1/going-deeper/available-elements.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.