> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/cms/readme.md).

# Elements CMS

Markdown based Content Management System

The Elements CMS is a simple, powerful way to add dynamic content to your Elements sites, without the complexity of traditional CMS platforms.

Built around Markdown, it gives you full control over your content while keeping everything fast, clean, and easy to manage. No databases, no plugins, no maintenance headaches. Just structured content that fits naturally into your Elements workflow.

It’s ideal for static websites that need dynamic content updates, i.e. blogs, portfolios, team pages, product listings, and more.

{% hint style="warning" %}
The base version of the **E**lements CMS is included for free with every Elements licence. If you require additional advanced CMS features, you can purchase a separate CMS Pro license.

The CMS Pro license is NOT included with your Elements license, and is an additional one-time purchase, per domain. [Learn more about the CMS Pro license](/elements-docs/cms/online-cms-editor.md).
{% endhint %}

### Benefits of a Markdown Based CMS

Using flat Markdown files for content comes with numerous benefits, especially when paired with a static site builder like Elements.

1. **There’s no database to configure or maintain**. Content is stored in plain .md files with optional YAML frontmatter. It’s easy to edit, version, and move around.
2. **Markdown is intuitive and readable** even without a CMS UI. It’s easy for non-technical users to make changes, and even easier for developers to troubleshoot.
3. Because all content is stored in text files, it **works perfectly with Git** and other version control systems. You can track changes, roll back updates, and collaborate like you would with code.
4. No backend server, no database, no requests, just static files. **This makes your site lightning fast and incredibly reliable**.
5. With no dynamic backend, there’s a much smaller attack surface. **Markdown-based CMS setups are more secure.**
6. You define the structure and fields using YAML. **The CMS adapts to your content**, not the other way around.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmacsoftware.com/elements-docs/cms/readme.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.