Edit website theme files, preview changes, and publish updates through the workspace review flow.

What this feature is for

• The theme editor is for deeper website changes that affect templates, components, styles, or page structure.
• Use it when a visual page edit is not enough and the site needs a reusable theme-level update.

When to use it

• Navigation, footer, layout, styles, or repeated components need an update.
• A page template should change for several pages at once.
• AI prepares a theme change that needs human review before publishing.

Do it manually

1. Open Website or Theme Editor.
2. Choose the page, component, style, or template file to update.
3. Make a focused change and save the draft.
4. Preview the affected pages on desktop and mobile.
5. Publish only after the public pages match the preview.

Website chat theme selection

When Website chat opens without a theme already selected, Faster starts from the applied theme. If there is no applied theme, it uses the saved theme preference, then the first available theme. That keeps AI website and theme requests anchored to the design customers are most likely to see.

Use fallbacks for empty post queries

The {{#faster:posts}} helper supports an {{else}} branch when the post query returns no results. This is generic empty-state fallback support for post queries. It is not limited to resource pages, and it is not a separate CMS resource-slot primitive.

The fallback branch works for normal filters and dynamic filters, including filters such as tag:{{tag.slug}}. Use it when a theme should try a targeted post query first, then show broader or latest content if the targeted query is empty.

{{#faster:posts key="topic-posts" limit="3" filter="tag:{{tag.slug}}"}}
  <article class="post-card">
    <h3><a href="{{url}}">{{title}}</a></h3>
    <p>{{excerpt}}</p>
  </article>
{{else}}
  {{#faster:posts key="latest-posts-fallback" limit="3" order="published_at desc"}}
    <article class="post-card is-fallback">
      <h3><a href="{{url}}">{{title}}</a></h3>
      <p>{{excerpt}}</p>
    </article>
  {{/faster:posts}}
{{/faster:posts}}

Theme builders can use the same pattern for labeled content slots. For example, a landing page might have visual slots named Insight, Guide, and Checklist. Those names are theme labels, tags, or editorial conventions chosen by the team; they are not built-in CMS primitives.

<section class="resource-slots">
  <div class="resource-slot">
    <p>Insight</p>
    {{#faster:posts key="insight-slot" limit="1" filter="tag:insight+tag:{{tag.slug}}"}}
      <a href="{{url}}">{{title}}</a>
    {{else}}
      {{#faster:posts key="insight-fallback" limit="1" tag="insight" order="published_at desc"}}
        <a href="{{url}}">{{title}}</a>
      {{/faster:posts}}
    {{/faster:posts}}
  </div>

  <div class="resource-slot">
    <p>Guide</p>
    {{#faster:posts key="guide-slot" limit="1" filter="tag:guide+tag:{{tag.slug}}"}}
      <a href="{{url}}">{{title}}</a>
    {{else}}
      {{#faster:posts key="guide-fallback" limit="1" tag="guide" order="published_at desc"}}
        <a href="{{url}}">{{title}}</a>
      {{/faster:posts}}
    {{/faster:posts}}
  </div>

  <div class="resource-slot">
    <p>Checklist</p>
    {{#faster:posts key="checklist-slot" limit="1" filter="tag:checklist+tag:{{tag.slug}}"}}
      <a href="{{url}}">{{title}}</a>
    {{else}}
      {{#faster:posts key="checklist-fallback" limit="1" tag="checklist" order="published_at desc"}}
        <a href="{{url}}">{{title}}</a>
      {{/faster:posts}}
    {{/faster:posts}}
  </div>
</section>

Use unique key values for each posts block so pagination, search, and runtime updates target the correct query. If a {{#faster:posts}} block has no {{else}} branch and no results, it still renders the default empty posts state.

Fallbacks can repeat content. If multiple empty slots all fall back to the same latest post, duplicate cards may appear. Teams should either tag enough content for each slot, accept the duplicates, or add explicit curation or dedupe logic in the theme when the design requires every card to be unique.

Ask Faster AI

Update the services page template to use clearer section spacing, keep the brand style consistent, and show me the changed files before publishing.

Add {{else}} fallbacks to these {{#faster:posts}} blocks so targeted queries show first and latest relevant posts show when a slot is empty.

Review before saving or publishing

• Preview every page type affected by the theme change.
• Avoid hardcoding business data that should remain editable in content or plugin settings.
• Check forms, navigation, buttons, dynamic post slots, fallback cards, and mobile layout before publishing.

Common mistakes and fixes

• If a change affects more pages than expected, review whether it belongs in a component or page only.
• If preview looks stale, refresh the branch and preview again.
• If a page breaks after publish, use the previous checkpoint or branch history to recover.
• If a fallback card repeats across several slots, add more tagged content, accept the repeated latest card, or add explicit curation or dedupe logic.

Service website page structure

For how theme-level choices should support the core pages a service business needs, read the service website page structure article. The 6 Pages Every Service Business Website Needs.

Connected workflows

• Create a lead capture form
• Connect trackers to pages, forms, and campaigns
• Add motion to a page
• Review and approve AI page changes

Placeholder media

• Screenshot placeholder: Replace with an annotated screenshot of use the theme editor.
• Video placeholder: Replace with a short walkthrough showing the manual path and review step.

Related help

• Manage branches and checkpoints
• Publish a page safely
• Update your site navigation

Use it in daily operations

• Preview the affected public pages on desktop and mobile, especially if the change touches navigation, design, SEO, forms, media, dynamic post queries, or plugin-powered sections.
• Keep placeholder screenshots and videos marked until final assets are approved and replaced during the launch review.
• Ask Faster AI to summarize the draft changes and review checklist so a teammate can approve the page without retracing the full edit history.