> 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/using-elements/components/data-and-organisation/cms.md).

# CMS

Elements CMS adds structured, dynamic content to RapidWeaver Elements websites without requiring a database. Content is stored in portable Markdown files with YAML front matter, so it can be edited, moved, backed up, and version controlled without being locked into a proprietary format.

Use it to create blogs, portfolios, knowledge bases, team pages, product listings, client-managed websites, and other content-driven sections.

{% hint style="info" %}
This page is an overview. For installation, system requirements, Markdown formatting, components, templates, pretty URLs, and troubleshooting, see the full Elements CMS documentation.
{% endhint %}

<a href="https://docs.realmacsoftware.com/elements-docs/cms" class="button primary" data-icon="database">Read the Full CMS Documentation</a>

### Requirements

Elements CMS requires a web server running **PHP 8.4 or newer** with the `mbstring` extension enabled. Pages that use CMS data must have their page extension set to `.php`.

{% hint style="warning" %}
Confirm that your hosting meets the current [CMS system requirements](https://docs.realmacsoftware.com/elements-docs/cms/getting-started/system-requirements) before building or publishing a CMS-powered site.
{% endhint %}

### How Elements CMS Works

1. Add the CMS components you need to an Elements page.
2. Point them at a folder containing Markdown files.
3. Create and edit content as Markdown, or use the browser-based Online Editor.
4. Publish the site and let the CMS components display, filter, search, and paginate the content.

Each Markdown file can contain a YAML front matter header for structured information such as its title, date, tags, author, image, or other custom fields. The body contains the main content.

### What You Can Build

* **Blogs and articles** — Publish posts with structured metadata, tags, authors, related content, and feeds.
* **Portfolios and listings** — Present projects, products, people, or other collections in filterable layouts.
* **Knowledge bases** — Create searchable documentation and support libraries.
* **Client-managed websites** — Give clients a browser-based editor so they can update approved content without opening Elements.
* **Global content** — Make frequently updated text, images, and other site content editable online.

### Why Markdown

* Content remains readable and editable outside Elements CMS.
* Plain files are easy to back up, move, and manage with Git.
* There is no database to configure, export, or maintain.
* YAML front matter allows the content structure to adapt to the website.

### Learn More

Visit the [Elements CMS website](https://cms.elementsplatform.com) for an overview of components, use cases, the Online Editor, and available plans.

Use the [full Elements CMS documentation](https://docs.realmacsoftware.com/elements-docs/cms) when you are ready to install the CMS or configure a website.


---

# 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.realmacsoftware.com/elements-docs/using-elements/components/data-and-organisation/cms.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.