Documentation menu

Landing pages

Compose pages from typed fields and reusable modules.

Each page is a set of fields keyed by a dotted path (for example home.hero.headline) with a type: text, long text, URL or media. Fields are grouped into sections, and the same structure is used in every market, Japan included.

Page keys

  • Main pages: home, about, services, pricing, contact
  • Detail page examples: service-seo, service-content, pricing-basic, pricing-enterprise

Field types

  • text: short text such as headlines and labels.
  • textarea (long text): multi-line text such as descriptions.
  • url: URLs such as CTA destinations.
  • image (media): an image, either uploaded or pasted as a URL.
json
{
  "home.hero.eyebrow": "Global logistics, simplified",
  "home.hero.headline": "Ship to 20+ countries with ease",
  "home.hero.subcopy": "Door-to-door forwarding with live tracking.",
  "home.hero.ctaLabel": "Get a quote",
  "home.hero.ctaHref": "/quote"
}

Editing guidance

  • Each field shows where it appears, what it is for, an example and tone guidance.
  • Fields with a recommended length show a character counter that turns red when you go over. It is a guideline only and does not block saving.
  • Key fields are marked on their label.
  • Image fields show a recommended minimum width.

Drafts, publishing and defaults

Saving a draft stores only the fields you changed, and publishing folds the whole draft into the published version. Each field shows whether it is unpublished, published or using the default value.

Draft and published fields are stored separately, so edits never touch the live page until you publish.
If you clear a field and publish, its published value is removed and the field falls back to its default copy.