> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/getting-started/welcome-to-roma.md).

# Welcome to Roma

Discover the design and content system that powers our product ecosystem.

Roma is our design and content system created by our **Design**, **Front-end**, and **Content** teams.  <br>

Here, you will find comprehensive and detailed guidelines for each of our components, patterns, and content. Each section offers guidance on usage, accessibility, writing, with examples.

## Get started

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Components</strong></td><td>A comprehensive list of our UI components, from atoms to organisms level. Learn about their design, variants and accessibility details.</td><td></td><td><a href="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2FxuSs4Bho7ZOEfBn4Y0jd%2FComponent%20card.png?alt=media&amp;token=660d4b69-cafa-4498-8dc3-4c8acc6eb744">Component card.png</a></td><td><a href="/design/components.md">Design</a></td></tr><tr><td><strong>Patterns</strong></td><td>Description of recurring experiences throughout our products. Keep consistency by reusing defined design at specific key points.</td><td></td><td><a href="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2FV9bpjs9TLaz4pbqyg5Hp%2FPatterns%20card.png?alt=media&amp;token=06721de0-22c8-409e-8a61-12df8f7c9378">Patterns card.png</a></td><td><a href="broken://pages/vu7c3Prmeh2lyI38WJAo">Broken link</a></td></tr><tr><td><strong>Content</strong></td><td></td><td>Learn more about our key principles on how to write into our products.</td><td><a href="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2F0WgyzOzoLAEQWfap3a07%2FContent%20card.png?alt=media&amp;token=6822a3d8-2e64-4b51-9e3e-90726128e986">Content card.png</a></td><td><a href="/content/writing-for-mirakl.md">content</a></td></tr></tbody></table>


---

# 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://design.mirakl.com/getting-started/welcome-to-roma.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.