What every screen in the Console is for

The Console is a content management system (CMS) with one website selected at a time. The dropdown at the top of the sidebar switches websites. Everything below it applies to the selected site and nothing else.

Overview

The landing screen for a site. It tells you the one thing worth knowing right now, in plain language: that the site is not published yet, that changes are waiting for a preview build, that the last publish failed, or that everything is published and nothing is waiting.

Each of those states comes with the action that resolves it. Treat the Overview as a to-do list that writes itself.

Content

Seven collections, each a list of entries you create and edit.

The split between Blog Posts and Articles is editorial, not technical. A post that is true this month belongs in Blog. A guide that is still true next year belongs in Articles.

Design

Two kinds of screen sit here, and confusing them costs time.

Global Design Settings holds the design system: brand colors, fonts, and logo. Every page reads from it. Change a color here and the whole site changes.

Custom CSS is a Cascading Style Sheets (CSS) file applied on top of everything else. The Console's own description is the warning worth repeating: a mistake here shows on every page.

Navigation, Headers, Footer and the per-collection templates (Article template, Blog post template, Collaborator template, Event template, Product template) are shared layouts. One footer renders on every page of the site. One article template renders every article. Edit one of these and you have edited hundreds of pages at once.

Settings

Global Settings: site name, domain, and language. These reach the browser tab, search results, and structured data.

Social Media: your profiles, rendered as icons across the site and embedded in the site metadata.

Page Map: the navigation structure and the list of addresses the site builds. Drag to reorder. A page absent from here has no address.

Redirects: rules that send an old address to a new one, so links people already have keep working.

Tools

Event emails writes to everyone signed up for one of your events, from a saved template or in your own words.

Connected services stores the keys that let your site talk to Zoom, TicketTailor, and MailerSend.

Owner Actions

Four actions, only two of them reversible.

Everyone you grant access to can edit content and settings. There is no read-only role.

More

Build Logs: the record of every build, and the first place to look when a publish fails.

MCP Tokens: Model Context Protocol (MCP) keys that let an AI assistant read and edit this site. Owner only. Covered in MCP tokens.

Billing and Usage sit alongside them: invoices, and charts of publishes and editor requests over time.

The one keyboard habit worth forming

The Console has a command palette that searches every screen, every collection, and every owner action by name, and remembers what you opened recently. Reaching a screen by typing its name is faster than remembering which group it lives under.

Next