These docs are organized by product surface, not by job: there is a category for the editor, a category for publishing, a category for the CLI. That is the right shape for looking something up and the wrong shape for learning the product, so this page is the job-shaped index. Pick the route that matches what you are doing today, and come back when that changes.
Which one are you?
| If your job is… | You will mostly use… | Your route |
|---|---|---|
| Writing and publishing content | Design and Plan in the rail — the editor, the page tree and the calendar | If you write and publish content |
| Running the site, the team and the funnel | Know, Engage and Settings — dashboards, contacts, roles, forms, email | If you run the site |
| Building how the site looks and behaves | None of the rail — your terminal, the CLI and the site repository | If you build the site |
If you are not yet sure what Leed is, rather than which part of it you need, the map is What is Leed?.
If you write and publish content
Ten pages, in this order. The first two are the only ones you need before you can do real work; the rest are the surfaces you will meet in your first week.
- Quick Start — get one page live before you learn anything else, so the vocabulary that follows attaches to something you have actually done.
- Core Concepts — now that you have published a page, this gives you the words for what you just did: drafts, revisions, page types, labels and deployments.
- Managing Pages — the page tree is the thing you will click a hundred times a day, so learn its status icons and filters early.
- Page Editor — where you will spend most of your time; the right rail in particular carries five tabs that are easy to miss.
- Editor Toolbar Reference — every control, including the ones that collapse into the kebab menu when the window is narrow, which is where people usually conclude a feature is missing.
- Page Settings — summary, keywords, authors, feature image, redirects. Read it before your first publish is blocked by a required field.
- Revisions and Versions — what happens when you edit a page that is already live, and how to get the old version back.
- Publishing and Scheduling a Page — publishing now, publishing later, and the difference between a scheduled date and a target date.
- How Publishing Works — the answer to “why isn’t my change live yet”, which is the question every writer asks in their first fortnight.
- Keyboard Shortcuts — worth ten minutes once the rest is familiar.
If you run the site
You are the person who owns the workspace rather than any one page: the team, the settings, the funnel and the numbers. Eleven pages.
- Touring the Workspace — the five-tab rail and what each tab owns, so the rest of these docs have somewhere to hang.
- Settings Home and the Settings Map — Settings is a map, not a mirror; this page tells you which card leads to which feature and which docs page owns it.
- How Content Is Organized — page types, menus, labels and paths decide your site’s shape, and changing them later is more expensive than getting them right now.
- Roles and Permissions — read this before you invite anyone: the six roles decide what each person even sees, and a role is a floor that overrides can only raise.
- Managing Team Members — the team list, changing someone’s role, and the two checkboxes that grant billing and developer access.
- How Forms Work — form to submission to contact to follow-up, end to end; this is the spine of everything in Engage.
- Engage Workspace — accounts, contacts, personas and campaigns, and why the URL is the state of the screen.
- How Email Works in Leed — the transactional/marketing split, because only one of the two counts against your quota.
- Know Dashboard — your performance home, its date ranges and the comparison period that most people misread on first sight.
- Feature Availability by Plan — the authoritative table of what your plan includes.
- Domains and DNS — pointing your own domain at the site, and what it answers on until you do.
Several things on this route depend on your plan rather than your role — marketing email, contact-level identity, campaigns and the deeper analytics among them. When a screen shows an upgrade prompt instead of the feature, the plan is the reason; Feature Availability by Plan is the list, tier by tier.
If you build the site
The CMS holds the content; you own the code that renders it. Your whole surface is the CLI and the site repository, so the route starts in a terminal.
- Quick Start for Developers — installer, local build, push, in one sitting.
- Installing the Leed CLI — the one-line installer, its prerequisites, and how it keeps itself current.
- Your Site Repository — the repo folder by folder, and the two branches that matter.
- How Templates Work — markdown, then HTML, then Handlebars: the processing order explains most of the surprises.
- How Helpers Work — registration, inline versus block versus subexpression, and the trailing options object every helper receives.
- Helper Index — the lookup table you will keep open in a second tab.
- How Styling Works — two surfaces: the CMS stores theme names, your repository holds the CSS those names refer to.
- Validate, Commit and Push — the four-step contract, the staging-only rule, and the automatic rebase that happens before your push lands.
- What Happens After You Push — traced end to end, including why your push reached preview and not the live site.
- Leed Markdown Overview — skipped on the writer route, and genuinely relevant here: it is what import and MCP writes speak, and what a published page is committed as.
If you are connecting an AI client
This is a detour, not a career — three pages, and you will be done in an afternoon.
- AI in Leed — the five AI surfaces and which one you actually want, since “connect Leed to my AI” means at least three different things.
- Connecting to the Operator MCP — the endpoint, the sign-in, and the setup for each client.
- What the Operator MCP Can and Cannot Do — read this before you ask a client to do something it will refuse: writes land as drafts, and publishing is not on the menu.
The three questions everyone asks first
“Why isn’t my change live?” Almost always because nothing has published it yet — How Publishing Works explains what publishing actually starts, and how long it runs.
“Who can see this?” Who Can See What maps roles to screens, so you can answer it for a person rather than for a permission.
“What does this word mean?” Every Leed term has a one-line entry in the Glossary, each linking to the page that defines it properly.