How a site is put together

Sites

One install holds any number of sites. Each has its own content, menus, template, people and settings, and answers on its own domain names. People get access per site through groups such as Owner, Editor, Author and Viewer.

Collections and entries

Content lives in collections: pages, articles, products, events, forms and whatever your extensions add. Each collection lists its fields, so the admin shows the right form and every saved value is checked against it. Rich text is cleaned, links are checked and unknown keys are dropped.

Entries can be drafts, scheduled for later, published or unpublished. Sites can be in several languages, with translations of an entry linked together.

Pages and blocks

Pages are built from blocks: hero, text, image, gallery, columns, cards, stats, call to action, quote, FAQ, video, latest entries, spacer, plus blocks from extensions such as forms, products and comments. The page builder previews them through the site's real template as you edit.

Menus route

A menu item gives a page its address. Items can point at one page, a list of entries (a blog, a product list), a link elsewhere, or a heading that groups items. List items give each entry in the collection its own page under the list's address. If you rename a menu item, its address changes with it.

Modules and positions

A template names positions such as header actions, sidebar, content top and bottom, and footer columns. Modules fill them: a menu, a block of HTML, contact details, a latest-entries list, a language switcher, a cart link or comments. Each module can show on every page or only on chosen ones.

Templates

A template is an extension that holds the page frame and the look. It lists its positions and the settings it offers, such as a logo, a tagline and colors. The default template, Aurora, has nine positions. Any template can override another extension's views by placing files at overrides/<extension>/<path>. A template can also list the parts of its look that the Design screen may change, such as its colors, fonts, sizes and corner rounding. AI agents change the same values through MCP.

Extensions

Everything beyond the core comes from extensions: the blog, shop, forms, events, comments, restaurant and help desk apps. Switch them on per site under Extensions. See Building extensions to make your own. Extensions can also be packed and signed into .sxp packages, and an install accepts a package only when a key it trusts signed it.

Publishing

By default visitors get published files. Publishing renders every page into a new release folder, checks it and switches over. That makes pages fast and cacheable, and leaves nothing to attack on the public side but plain files. Account pages, forms, the cart, comments and extension routes stay live, because they need the program. A site can also be set to render every request live instead.

Sites can republish themselves daily or hourly, which keeps date-based lists such as upcoming events current.