A complete starter site on escala: a home page, a blog with categories, the legal pages, and a header and footer. Clone it to start a new site rather than building one up from nothing.

In a database, one copy per environment. Every page, section, link and image is an entry, and an entry's renderer decides how it looks.

That's why the same section can be a plain block today and an accordion tomorrow, with no change to its words.

Yes, at three levels, from the broadest to the narrowest.

The theme

Colours, fonts, spacing and corner rounding come from the theme. Change a colour role and every block that uses it follows, in light and dark mode alike. Most of a brand is set here, once.

Colour schemes

A scheme is a named set of colours for one block: its surface, its text, its accent and its buttons. A section on an inverse band uses a scheme, and everything inside it follows.

Each block's options

Every block offers its own options in admin: its layout, width, spacing and heading size. A section can sit its image beside its text, put its text over the image, or lay its items out in columns.

• Options are chosen from a list, never typed.
• An option that would do nothing is hidden.
• A renderer can save a set of options as a preset, so the next block starts from it.

Between them, those three cover nearly every change a site needs without a developer.

Yes. A cloned site gets its own domain, certificate and environments.

A static site costs very little to host: its pages are files, served from a CDN. The content database is only read when a site is built.

Edit in admin, then publish the entry. The site rebuilds with the change, and it's live a few minutes later.

Three copies of the site and its content. Changes are made and checked in dev, reviewed in uat, and go live in prod.

Yes. Until you publish, the live site still shows the published version, and you can discard your edit. After publishing, edit the entry back and publish again.