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

# Introduction

**StoryPress** is your CRM and content hub for building and managing your website. This guide gets you from zero to a live, on-brand site—without code.

***

## The problem: two flawed camps

The market is split in two, and both sides leave most people stuck.

1. **The "Wix/Squarespace" camp** — Built for non-developers. You get drag-and-drop and templates, but also bloat: slow sites, too many tools, scattered focus, and high monthly costs.
2. **The "dev stack" camp** — Built for developers. Tools like Cloudflare and headless CMS deliver real speed and low cost, but you need to code. Inaccessible if you're not a developer.

***

## The StoryPress solution

**StoryPress bridges the gap.** We give you the speed, power, and cost-efficiency of the dev stack—through an interface built for everyone.

* **How we do it** — We didn’t just resell a CMS. We built our own **interface layer**: a simple, mobile-first dashboard that talks to enterprise-grade backends (headless CMS, CDN, and more). More integrations are on the roadmap.
* **The result** — You get an enterprise-grade setup (fast, scalable, low cost) at a fraction of the price, managed through an interface as easy as a social app.

***

## The StoryPress way

1. **Set your theme first** — [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). One place controls how your whole site looks and feels.
2. **Then build your site** — Add pages and blocks. Use [rich text](/storypress-docs/content-blocks/rich-text.md) for copy, [images](/storypress-docs/content-blocks/gallery.md) (or assets) for stills and video. Put them together with [containers](/storypress-docs/content-blocks/container.md) (columns, alignment) and [image + text](/storypress-docs/content-blocks/image-text-rich.md) blocks so content looks the way you want.
3. **Go further** — [Maps](/storypress-docs/content-blocks/map.md), [lead forms](/storypress-docs/content-blocks/lead-form.md), [galleries](/storypress-docs/content-blocks/gallery.md), [Instagram feeds](/storypress-docs/content-blocks/instagram-feed.md), and more. Everything stays consistent with your theme.

***

## What you'll find here

* [**Theme & setup**](/storypress-docs/theme-and-setup/overview.md) — [Fonts](/storypress-docs/theme-and-setup/fonts.md), [colors](/storypress-docs/theme-and-setup/colors.md), [nav](/storypress-docs/theme-and-setup/navigation.md), [footer](/storypress-docs/theme-and-setup/footer.md), [favicon](/storypress-docs/theme-and-setup/favicon.md). Configure once, apply everywhere.
* [**Building your site**](/storypress-docs/building-your-site/start-building.md) — How to start adding content and how blocks work together ([containers](/storypress-docs/content-blocks/container.md), columns, [image + text](/storypress-docs/content-blocks/image-text-rich.md), alignment).
* [**Content blocks**](/storypress-docs/content-blocks/content-blocks.md) — Reference for each block and when to use it.

Use the sidebar to jump to [**Theme & setup**](/storypress-docs/theme-and-setup/overview.md) first, then [**Building your site**](/storypress-docs/building-your-site/start-building.md), then [**Content blocks**](/storypress-docs/content-blocks/content-blocks.md) when you need the details.


---

# 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/readme.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.