> For the complete documentation index, see [llms.txt](https://docs.civictheme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.civictheme.io/content-authoring/components/message.md).
# Message
The Message component is used to display important notifications and alerts to users. It communicates status, urgency, and context through clear visual styling such as colour and iconography.
### How to create a Message
1. Log in as a *Content author*.
2. Create a new *Page* or navigate to the page you want to add the Message to.
3. Click on the *Components* dropdown and select *Message*.
4. Open the *Type* dropdown to select the type of Message you want to display:
1. Information
2. Error
3. Success
4. Warning
5. Add an optional *Title*. This will display next to the icon at the top of the message.
6. Add optional *Content*.
7. Select *Light* or *Dark* theme.
8. Set the *Vertical* spacing.
9. Note: the *Background* is not enabled for the Message.
### Message examples
The colours below are examples using CivicTheme OOTB colour settings.
### Further Message resources
#### Storybook
Interact with the [Message component](https://uikit.civictheme.io/?path=/story/organisms-message--message) in Storybook.
#### UX evidence framework
Read the [UX evidence behind the Message component](/components/organisms/message.md).
---
# 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://docs.civictheme.io/content-authoring/components/message.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.
