> For the complete documentation index, see [llms.txt](https://code-collective.gitbook.io/launch-flow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://code-collective.gitbook.io/launch-flow/features/theme-publishing.md).

# Theme & page publishing

{% hint style="info" %}
Available on the **Growth** plan.
{% endhint %}

Beyond prices, Launch Flow can publish a **theme** and **page updates** on a schedule. Sseful when a sale needs a matching storefront design or a landing page to appear at the same moment the prices change.

1. Prepare the theme or page you want to go live (for a theme, have it ready as an unpublished theme in your admin).
2. In Launch Flow, create a launch and select the theme publish and/or page update.
3. Set it to the same start time as your price changes so the whole store flips together.
4. Save. At the scheduled time, Launch Flow publishes the theme/page automatically.

{% hint style="success" %}
**Pair theme + price changes in one launch window.** Scheduling them for the same time gives customers a consistent "sale is on" experience the instant it begins.
{% endhint %}


---

# 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://code-collective.gitbook.io/launch-flow/features/theme-publishing.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.