TH SeedWebs
Documentation

Themes and templates

What a SeedWebs theme holds, what each kind of theme part is, how a template is chosen for each URL, and how Tailwind and email templates work.

Last updated 2026-11-17

Everything about how your public site looks comes from a theme, stored inside your own site. A theme holds the HTML of the header and footer, the global CSS and JavaScript, and the smaller pieces — theme parts — that decide how a post, a product or a category page is rendered.

Themes are managed at Settings → Themes (/admin/settings/themes); email templates at Settings → Emails (below).

What one theme holds

Each theme carries these values of its own, all edited on the General tab of the theme editor.

FieldLabel on screenWhat it does
header_htmlHeaderThe header HTML shown on every page
footer_htmlFooterThe footer HTML shown on every page
global_cssGlobal StylesEverything placed in <head> — Google Fonts <link> tags, the Tailwind script, <style> blocks
global_jsGlobal JavaScriptA script placed at the end of <body> on every page. Write the code only, no <script> tag
body_classBody classTailwind classes applied to the <body> tag, such as background colour and font

Each holds up to about 1 MB. Over that, the save is refused and you are told which field is too big.

The tabs in the theme editor

Opening a theme shows pill tabs at the top.

TabURLContents
General/admin/settings/themes/{id}Header, Footer, Global Styles, Global JavaScript, Body class
Nav/admin/settings/themes/{id}/navThe elements that build the menu (slugs starting nav-)
Elements/admin/settings/themes/{id}/elementsReusable elements, such as a post card or product card
Templates/admin/settings/themes/{id}/templatesThe template for each kind of page

Every tab shares the same right sidebar: the status box (Active / Inactive), the theme name, its slug and the save button.

Every field and theme part is edited as code and saved exactly as you type it; the header, footer and theme parts have a Format button that tidies the code. Collapsed, a part’s card shows a small rendered preview. Click the preview to expand, and the pencil icon in the card header to change that part’s name and slug.

Kinds of theme part

In the database a theme part’s type is one of header, footer, element, template or email.

In practice, in the current version:

  • element — a piece called from elsewhere with {{> slug}}, such as post-card inside a post-list loop. Elements whose slug starts nav- are split out into the Nav tab; the rest live under Elements.
  • template — the shell for one whole page, such as post-list for the post listing.
  • email — the body of a system email, such as the order confirmation, edited at Settings → Emails.
  • header and footer — still accepted by the API, but the header and footer actually rendered come from header_html and footer_html on the theme itself, not from parts. That is why there are no Headers or Footers tabs.

A part’s slug has to be unique within one theme and one type — so an element called post-detail and a template called post-detail can coexist.

The Elements and Templates lists hide parts belonging to content types you have switched off under Settings → General → Features, going by the slug prefix (post-, event-, product-, book-, staff-, doc-, slider-, member-, donation-). Parts not tied to a content type — page, category, tag, search-results, not-found — are always shown.

That filter does not cover slugs starting tour-, so tour templates always remain in the list. Tours are in no plan’s permissions; the SeedWebs team has to turn on the experimental flag for your site before they do anything. Until then, editing a tour template changes nothing, because no page calls it.

How a template is chosen

When somebody opens a URL, SeedWebs picks a template through three nested fallbacks.

Layer 1 — the active theme, then the default theme

Parts are taken from the Active theme first, and the gaps filled from the theme whose slug is default, matching on the pair of type + slug. That is why a brand-new theme with no parts at all still renders a complete site: it borrows every part from the default theme. Create a part with the same name in your own theme and yours immediately wins.

Layer 2 — a specific slug, then the general one

A category page looks for a template named for that category first, and falls back to the general one. The category news looks for category-news, and failing that uses category. This is how you make one category look different from the others without touching the shared template.

Layer 3 — type template, then type element

Once the slug is settled, SeedWebs looks for a part of type template first, and failing that a part of type element with the same slug.

The order per URL

{slug} below is the slug of the category, brand or page template being viewed.

PageSearch order
A Page written in Article modepage-{page template slug} → page
/postspost-list
/posts/:slugpost-detail-page → post-detail
/category/:slug (or /category/:parent/:slug, nested)category-{slug} → category
/tag/:slugtag
/eventsevent-list
/events/:slugevent-detail-page → event-detail
/productsproduct-list
/products/:slugproduct-detail-page → product-detail
/product-categories/:slug (or /product-category/…)product-category-{slug} → product-category
/product-tags/:slug (or /product-tag/:slug)product-tag-{slug} → product-tag
/product-brands/:slug (or the site’s brand word, such as /brands/:slug)product-brand-{slug} → product-brand
/tourstour-list
/tours/:slugtour-detail-page → tour-detail
/tour-category/:slugtour-category-{slug} → tour-category
/tours/bookings/:booking_numbertour-thankyou
/staffsstaff-list
/staffs/:slugstaff-detail-page → staff-detail
/staff-categories/:slugstaff-category-{slug} → staff-category → staff-list
/authorsauthor-list
/authors/:slugauthor-detail-page → author-detail
/booksbook-list
/books/:slugbook-detail-page → book-detail
/book-categories/:slugbook-category-{slug} → book-category
/docs/:slugdoc-detail-page → doc-detail
/searchsearch-results
/cartcart — only while the store is on (Store settings → Checkout enabled + a payment gateway); otherwise 404
/checkoutcheckout — same condition
/orders/:order_numberorder-received
A page that does not exist (404)not-found

A page of your own slugged cart, checkout or orders is served instead of the store page — pages come first, as everywhere else. A WooCommerce import brings such pages along; set them to draft to let the store pages through.

If nothing in the order matches, that content page answers 404 — except Pages, which still render their content plainly with no template. For not-found, a missing template falls back to a built-in page. The not-found template supports {{site_name}} and {{> partial}} (so a shared sidebar or footer block still appears); item tags are not rendered there, because a 404 has no item.

The tags used inside templates are documented in Template tags.

What the default theme ships with

Every new site gets a theme called Default (slug default), with this factory set of parts.

Templates

page · post-list · post-detail-page · category · tag · event-list · event-detail-page · product-list · product-detail-page · product-category · product-tag · product-brand · tour-list · tour-detail-page · tour-category · tour-thankyou · staff-list · staff-detail-page · staff-category · author-list · author-detail-page · book-list · book-detail-page · book-category · doc-detail-page · search-results · not-found · order-received · cart · checkout

Elements

post-card · event-card · product-card · tour-card · staff-card · book-card · author-card · post-detail · event-detail · language-switcher

Elements on the Nav tab

nav-item · nav-submenu · nav-mega-header · nav-mega-column · nav-mobile-item · nav-mobile-submenu · nav-mobile-mega · nav-mobile-mega-column · nav-mobile-drawer

Emails (at Settings → Emails)

email-welcome · email-newsletter · subscribe-form · email-order-confirmation · email-form-notification · email-form-autoreply · email-donation-receipt

The Templates tab starts with Page Templates, listing your page templates (Default and Landing come as standard). One never customised shows a dashed box saying it uses the default layout, with Customize, which creates page-default or page-landing to edit: Default starts as a copy of page, Landing as an empty shell with no header or footer, since a landing page controls the whole page.

Putting {{header}} and {{footer}} in a page template inserts the theme’s header and footer at exactly that point, and SeedWebs then does not insert them again. The exception is a page using the Landing page template, where both tags render as nothing.

The default theme: resettable, not deletable

The default theme differs from the others in three ways.

  1. It cannot be deleted. The bin icon in the corner of the status box becomes a reset button instead, and a delete through the API is refused.
  2. It cannot be deactivated. Pressing Inactive while the default theme is the Active one warns you to activate another theme first.
  3. Its factory parts cannot be deleted. Parts that shipped with the platform are protected, with a message saying they are built in and to use Reset instead. Parts you added to this theme yourself delete normally.

Reset to default (the circular-arrow icon right of the status box) renames the theme Default, restores Header, Footer, Global Styles and Body class to factory values, empties Global JavaScript, then deletes every theme part in this theme and re-inserts the factory set — your customisations and your own parts are gone. To experiment safely, work in a new theme.

Any theme other than default can be deleted, and deleting the Active theme switches back to the default theme automatically. Media library images the theme referenced are not deleted with it.

A new theme

There is no Add Theme button: a new theme comes from your AI app (Connect an AI assistant). Its create_theme copies the active theme’s header, footer, Global Styles, Global JavaScript, Body class and email templates into a new theme; every other part falls back to the default theme. A new theme is inactive; one the app creates to be activated at once waits, not yet created, for you to approve its Publish request.

Email templates (Settings → Emails)

Settings → Emails (/admin/settings/emails) edits the active theme’s email templates; activate a theme to edit its own. A standard email the active theme lacks shows its name with Copy from default: until copied, the welcome, newsletter, subscribe form and donation receipt use the default theme’s version, and the order confirmation and form emails go out as SeedWebs’ built-in email. A site that may not use Newsletters (its plan and the experimental flag) does not see the welcome, newsletter and subscribe form here. Add Email creates your own, such as email-order-notification or a template a form’s email settings pick. The subscription-confirmation and unsubscribe templates are hidden here and from a form’s picker (a form already using one still sends it). Tags: Template tags (welcome, newsletter, new order), Donations (receipt).

Tailwind: CDN or Optimize

Public pages are styled with the Tailwind classes written into your theme’s HTML, so the browser has to get the CSS for those classes from somewhere. Two buttons at the bottom of the Global Styles editor handle this.

Use CDN adds Tailwind v4’s browser build to Global Styles with a <style type="text/tailwindcss"> @theme starter of two colours (foreground, background). A Tailwind v3 script is removed; if v4 is already there you are told so and nothing is duplicated. Classes compile in the visitor’s browser — handy while designing, but every visitor loads an extra external file.

Optimize scans all of this theme’s HTML — header, footer, every theme part, page content written as HTML, and the Body class — compiles only the classes actually used into a <style>/* Tailwind CSS (built) */…</style> block, puts it back into Global Styles, removes the CDN script, and saves immediately. Pages load faster and depend on no external file, which is what you want in production.

The catch with Optimize is that it compiles what exists at the moment you press it. Every time you add a new Tailwind class to a theme part or a page, press Optimize again, or that class has no CSS behind it.

Colours and fonts (Global Styles)

Global Styles is plain code. The blocks SeedWebs manages — fonts (sw:fonts), the WordPress presets a Move adds (sw:wp-presets) and the CSS Optimize builds — show read-only; edit everything around them. If the theme changed after you opened it (an AI app set a font, say), Update stops instead of overwriting it; reloading replaces what you typed with the latest version.

Colours are declared in the @theme block (--color-accent: #e11d48; gives bg-accent and text-accent), or in tailwind.config on an older Tailwind v3 theme. The default theme comes with five: foreground, background, card, muted, primary.

Fonts are set by your AI app on a theme other than the default (on the active theme, as a Publish request you approve): set_theme_font installs font files from your media library (.woff2 smallest, .woff, .ttf, .otf), then set_theme_font_role points font-body or font-heading at the family (REST: /api/themes/{id}/fonts, any theme). Keep those files in the media library. A Google Font is a <link> plus a --font-* line in @theme, which you can edit yourself.

The default theme also ships a set of .prose CSS in Global Styles, which styles headings, paragraphs, lists and tables inside post content. Edit it as you like.

Who can edit themes

Themes and Settings → Emails fall under the settings.themes permission, held by two roles.

RoleCan open ThemesCan edit / create / delete themes and parts
super_adminYesYes
adminYesYes
editorNoNo
writerNoNo

Heavier operations are super_admin only: wiping the site’s content at Tools → Reset, and restoring from a backup at Tools → Backup (creating a backup goes up to admin). Roles are described in Users and permissions.

The theme system is not limited by plan: every plan edits and creates themes and templates alike. The plan decides which content types the site can enable, which hides the disabled types’ templates and makes their public pages answer 404; the per-site experimental flag covers Events, Docs, Books, Staffs, Members, Newsletters, Tours and Donations. See Plans and billing.

Common misunderstandings

Edited the theme, but the site has not changed. First check that the theme you edited is the Active one: the status box in the right sidebar must say Active, as must the theme list. The other common cause is adding new Tailwind classes after having pressed Optimize — press Optimize again.

Created a new theme and the site looks the same. A new theme is inactive until you press Activate. Active, it shows the header, footer, CSS and email templates it copied from the theme active when it was made, and borrows every other part from the default theme until you create one with the same name.

Want one category to look different from the others. Do not edit the category template. Create a new template called category-{that category's slug} and SeedWebs will use it for that category only.

Reset cannot be undone. After one confirmation it overwrites the default theme with factory values and deletes all its parts. The only way back is Tools → Backup, which rolls the whole site (not just the theme) back to a snapshot — and only super_admin can restore.