> 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/content.md).

# Content

### Summary

The Content component is used to add content via a WYSIWYG editor.

This section shows you how to add a Content component. Below is some sample content that uses the Content component.

<figure><img src="https://3596844540-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F79QhtrrFEncRGId6RF6A%2Fuploads%2Fgit-blob-476b5916cda0c16598463dda9e479f369d4bdad1%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Step 1 - Add the Content Component <a href="#contentcomponent-step1-addthecontentcomponent" id="contentcomponent-step1-addthecontentcomponent"></a>

Under the “Content” tab, click on “Add Content” .

### Step 2 - Fill in the various fields <a href="#contentcomponent-step2-fillinthevariousfields" id="contentcomponent-step2-fillinthevariousfields"></a>

1. WYSIWYG editor - Enter your custom text here.
2. Theme - Select your theme preference, light or dark.
3. Vertical spacing - There are 3 options: Top, Bottom, Both. Your choice adds padding to the respective area. For example, if you select “Both”, the padding is added to the top *and* bottom of the custom text.
4. Background - This will apply a themed background colour depending on your choice of the theme color in point #2 above.


---

# 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/content.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 `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.