> For the complete documentation index, see [llms.txt](https://storypress.gitbook.io/storypress-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://storypress.gitbook.io/storypress-docs/getting-started/key-concepts.md).

# Key concepts

A few ideas that make the rest of the docs easier to follow.

***

## Theme first, then build

Your [**theme**](/storypress-docs/theme-and-setup/overview.md) is the control center for look and feel: [fonts](/storypress-docs/theme-and-setup/fonts.md) (Google or Adobe), [colors](/storypress-docs/theme-and-setup/colors.md), [navigation](/storypress-docs/theme-and-setup/navigation.md), [footer](/storypress-docs/theme-and-setup/footer.md), and [favicon](/storypress-docs/theme-and-setup/favicon.md). Set it first. Then add pages and blocks; they’ll use the theme automatically. You’re not styling each block by hand—you’re building on a foundation.

***

## Pages and blocks

Your site is **pages**. Each page is built from **blocks**—[rich text](/storypress-docs/content-blocks/rich-text.md), [images](/storypress-docs/content-blocks/gallery.md), [containers](/storypress-docs/content-blocks/container.md), [forms](/storypress-docs/content-blocks/lead-form.md), [maps](/storypress-docs/content-blocks/map.md), and so on. You add blocks in the order you want them to appear. Some blocks are **layout** (e.g. [Container](/storypress-docs/content-blocks/container.md) with columns); others are **content** (e.g. [Rich text](/storypress-docs/content-blocks/rich-text.md), [Images](/storypress-docs/content-blocks/gallery.md)). Put content blocks inside layout blocks to get columns, alignment, and sections.

***

## How blocks work together

* [**Container**](/storypress-docs/content-blocks/container.md) has **columns** (1, 2, or 3). Use 2 columns to put text on one side and an image on the other; set alignment and column position so they line up.
* [**Image + text**](/storypress-docs/content-blocks/image-text-rich.md) is one block that does “image + copy” side-by-side or text-over-image. Use it when you want that pattern without building it from a container.
* [**Rich text**](/storypress-docs/content-blocks/rich-text.md) = words. [**Images**](/storypress-docs/content-blocks/gallery.md) / Asset = stills and video. Combine them inside [containers](/storypress-docs/content-blocks/container.md) or in the [Image + text](/storypress-docs/content-blocks/image-text-rich.md) block.

See **Building your site → How blocks work together** for layout patterns and options.

***

## Nested blocks

Many blocks **contain other blocks**. Examples:

* [**Theme**](/storypress-docs/theme-and-setup/overview.md) contains [Colors](/storypress-docs/theme-and-setup/colors.md), [Fonts](/storypress-docs/theme-and-setup/fonts.md), [Navigation](/storypress-docs/theme-and-setup/navigation.md), [Footer](/storypress-docs/theme-and-setup/footer.md), Favicons.
* [**Container**](/storypress-docs/content-blocks/container.md) contains the blocks that sit in each column (e.g. [Rich text](/storypress-docs/content-blocks/rich-text.md), [Images](/storypress-docs/content-blocks/gallery.md)).
* [**Lead form**](/storypress-docs/content-blocks/lead-form.md) contains Form field blocks.
* [**Map**](/storypress-docs/content-blocks/map.md) contains Map pin (or Map pins) blocks.

When you add a block that allows nested content, StoryPress will show you how to add and order the inner blocks.

***

## Your theme drives the look

[Colors](/storypress-docs/theme-and-setup/colors.md), [fonts](/storypress-docs/theme-and-setup/fonts.md), [nav](/storypress-docs/theme-and-setup/navigation.md), and [footer](/storypress-docs/theme-and-setup/footer.md) come from the theme. If you don’t see an option to change something (e.g. a global color), it’s likely in the theme. Check **Theme & setup** in this guide.


---

# 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://storypress.gitbook.io/storypress-docs/getting-started/key-concepts.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.