No site selected

Settings

Sites

About this section: SitesEach customer-facing website your team runs.

Purpose

A site is one website you operate (for example PureLife2). Set its name, domain, and basic defaults here. Other settings tabs let you turn sections, packages, and tags on or off for each site.

Key fields

  • Site Code: Short internal name for the site. Keep it short and lowercase. Try not to change it after other settings start using it.
  • Domain Name: The website's address, without https:// or any path. For example: example.com.
  • Lifecycle Status: Choose Active when the site is live to customers. Use Draft while you set things up.
  • Defaults: Things like whether comments and blogs are on by default. You can change these for each section later.

Example

Create a new site in Draft, fill in its name and domain, pick the defaults, turn on the sections and packages you need, then mark it Active.

Consequences

  • Changing the site code after other settings reference it can confuse your tools and reports.
  • If you do not turn on any sections or packages, customers will see an empty site.
  • Defaults set here are used everywhere unless a section or page overrides them.

Edit Site

Update site identity and the site_config defaults used by NEW ADMIN.

Site Identity

Stable identity fields used by routing, caching, and admin tooling.

lowercase snake_case; stable admin slug
hostname only, no https:// or path
admin-facing styled name
Only active sites should be served by runtime projections.
Optional operator description, max 500 characters.

Site Config

Defaults consumed by NEW ADMIN runtime projections. Per-section overrides land later.

optional personality.id; required later before enabling INSPIRE