Every word Leed uses that is not ordinary English, in alphabetical order, one line each, with a link to the page that owns it. The narrative version — the same ideas in the order you actually meet them, with a paragraph apiece — is Core Concepts. Jump to a band: A–C · D–H · I–M · N–R · S–Z.
A–C
| Term | What it means | Where it’s documented |
|---|---|---|
| A2A agent card | The /.well-known/agent.json file your published site serves so a remote AI agent can discover what the site offers before asking it anything. | Site AI Agent |
| Account (Engage) | An identified business, with the contacts you know at it grouped under it. | Accounts |
| Alert | A colored callout box in page content — note, tip, info, warning or danger — written as a :::note fence. | Alerts |
| Alias | An address a page used to live at, kept alive as a 301 redirect to its current one. | Aliases and Redirects |
| Analytics view | A read-only editor mode that replaces the page with its traffic data, entered with View Analytics and left with Back to Editing. | Page Analytics in the Editor |
| API page type | A page type whose pages are generated from an OpenAPI specification and are read-only in the editor. | API Reference Pages |
| Asset | An image, video, audio file or document held in your workspace’s one shared library and referenced by pages. | Asset Library |
| Attribution | Joining a visitor’s separate sessions into one journey so a conversion can be credited to what started it — plan-gated, see Feature Availability by Plan. | Journeys, Funnels and Attribution |
| Autolink | A word or phrase you register once so Leed links it automatically everywhere it appears on your site. | Autolinks |
| Autosave | The editor’s only save mechanism: every keystroke persists to the draft immediately, which is why there is no Save button. | Autosave, Collaboration and Locking |
| Block | One top-level unit of a page — a paragraph, heading, list, table, code fence or alert — and the thing comments and suggestions attach to. | Block Types and Block Settings |
| Build | One render of your entire site from its templates plus your published content; every deployment runs exactly one. | Every Deployment Is a Full Rebuild |
| Campaign | A planned piece of outreach with an audience and a set of dated deliverables — plan-gated, see Feature Availability by Plan. | Campaigns and Deliverables |
| Code theme | The syntax-highlighting palette applied to code blocks on your published site. | Themes, Fonts and Code Themes |
| Collection | A grouping of pages that a template can loop over — for example every page carrying one label. | Collections and Pagination Data |
| Comment | A threaded note attached to a block in the editor, with emoji reactions; comments are never published. | Comments and Reactions |
| Contact | A person Leed knows about, created by a form fill, an import or an integration. | Contacts |
| Contact group | A named set of contacts used as an audience for email. | Contact Groups and Audiences |
| Contributor | Someone credited on a page alongside its authors, which also grants them access to that page. | Authors and Contributors |
| Custom hostname | Your own domain, registered with Leed’s edge so your site answers on it over HTTPS instead of on a workers.dev address. | Domains and DNS |
D–H
| Term | What it means | Where it’s documented |
|---|---|---|
| Deliverable | One dated item inside a campaign — a page, an email, a social post — carrying its own approval state. | Campaigns and Deliverables |
| Deployment | One full rebuild and republish of your site, recorded as a row you can watch on the Deploy screen. | Deployment History and Status |
| Deployment reason | The label on a deployment saying what triggered it — Pages, Menus, Labels, Page Types, Developer CLI and so on; one deployment can carry several. | Deployment History and Status |
| Design workspace | The rail tab holding everything you edit: site pages, documentation, menus, forms, email layouts, site layouts and assets. | Design Workspace |
| Docs MCP | The MCP server your published documentation exposes on your own domain, for your readers’ AI clients. | Docs MCP: AI Access for Your Readers |
| Documentation set | A documentation-type page type plus its left-hand menu — the pages, folders and navigation that make up one manual. | What a Documentation Set Is |
| Domain Connect | A guided flow that configures your DNS with participating providers so you do not have to edit records by hand. | Domains and DNS |
| Draft | A page that has never been published, visible only inside the CMS. | Core Concepts |
| Eject | Copying one of Leed’s built-in templates into your own repository with leed site eject so you can edit it. | leed site eject |
| Engage score | A contact’s or account’s readiness, fit and intent numbers, recomputed from what Leed knows about them. | Engage Scores |
| Entitlement | What your plan makes available; the CMS consults it before drawing a gated screen. | When a Feature Is Gated |
| Feature (gated) | A capability that is switched on or off by plan tier, as opposed to a quota, which is a number. | Feature Availability by Plan |
| Feature image | The image a page carries for its listing card and its social preview. | Page Settings |
| Folder (menu) | A menu item with children and no link of its own; in a documentation menu its name becomes a segment of every child page’s URL. | Folders Set Your URLs |
| Form | A set of fields you build in the CMS and place on a page; submissions become contacts. | How Forms Work |
| Handlebars helper | A function a template can call to render something — an image, a menu, a date, a list of pages. | How Helpers Work |
| Home tab | The rail tab you land on when you open the CMS, Know unless you change it; the choice is remembered per browser. | Touring the Workspace |
I–M
| Term | What it means | Where it’s documented |
|---|---|---|
| In revision | A published page that has unpublished edits waiting; readers still see the last published version. | Core Concepts |
| Journey stage | A stage you define under Settings to mark where a page or a contact sits in your buying journey. | Journey Stages |
| Know | The rail tab holding your analytics dashboard. | Know Dashboard |
| Label | A tag on a page that groups content, drives index listings and can scope who may edit it. | Labels and Series |
| Label (menu item) | The display text of an entry in a menu — unrelated to content labels, and edited on the menu itself. | Building and Editing a Menu |
| Layout | The template that wraps a page’s content on the published site; a page type chooses one. | Layouts and Page Types |
| Lead profile | Everything Leed has joined together about one visitor, anonymous or identified. | Lead Profiles and Visitor Identity |
| Leed Markdown | The markdown dialect Leed stores page content in, and the format import and AI clients read and write. | Overview and Cheat Sheet |
| Live site | The site built from your main branch and served on your own domain — what the public sees. | Preview Site vs Live Site |
| Marketing email | A bulk send to a contact group, metered against your plan’s monthly allowance — plan-gated, see Feature Availability by Plan. | Sending a Marketing Email |
| Menu | A named navigation structure — a header, a footer, or a documentation set’s left-hand tree. | Menus and Navigation |
| Menu item | One entry in a menu: a link to a page, an external URL, or a folder holding other entries. | Building and Editing a Menu |
| Must-publish | Leed’s rule that a saved change is not a public change; the amber dots across the CMS mark what is still waiting. | Publish Reminders and the Must-Publish Model |
N–R
| Term | What it means | Where it’s documented |
|---|---|---|
| Operator MCP | Leed’s own MCP server at https://app.leed.ai/mcp, which lets your team’s AI clients read and draft in your workspace under your permissions. | What the Operator MCP Can and Cannot Do |
| Organization | The same thing as a workspace; the word the sign-in screens and the profile menu use. | Joining and Switching Workspaces |
| Page | The unit of content in Leed — one article, post or reference page, with one status and one page type. | Managing Pages |
| Page type | A page’s category, which settles its URL structure, layout, menu, required fields and available formatting. | Page Types |
pageid: link | An internal link written by page id rather than address, so it survives the target page moving or being renamed. | Linking Between Docs Pages |
| Partial | A reusable fragment of a template, included by name from a layout or another partial. | Leed Partial Index |
| Path | A page’s full address, composed from its page type slug, its menu folders and its own slug — and settable no other way. | URL Paths and Slugs |
| Pending change | A CMS change that is saved but not yet on your site, waiting in the Your edits list on the Deploy screen. | Publishing Changes |
| Persona | A described buyer type used to group contacts and aim campaigns at them. | Personas |
| Plan (calendar) | The rail tab showing a week at a time: scheduled publishes, deployments and campaign deliverables. | Plan Calendar |
| Plan (tier) | Your billing plan — Free, Starter, Growth or Enterprise — which decides which features and quotas you have. | Plans and Tiers |
| Preview site | The site built from your staging branch, served at staging. plus your domain, where template changes land first. | Preview Site vs Live Site |
| Privilege | One named permission, such as page:publish or developer:write, that a role or an override grants. | Privilege Matrix |
| Private page | A page visible only to the person who created it and which cannot be published; it can only be marked private through the API or MCP. | Private Pages |
| Promote | Pushing everything currently on your preview site to your live site, from the Deploy screen. | Promoting Preview to Live |
| Publish | The deliberate act that turns saved work into public content by queueing a deployment; it is never automatic and never done by an AI client. | How Publishing Works |
| Quota | A numeric limit your plan sets — contacts held, marketing emails a month, how long analytics are kept. | Usage and Limits |
| Rail | The narrow column of icons down the left edge of the CMS: Know, Design, Engage, Plan, Deploy and Chat, with settings and your avatar beneath. | Touring the Workspace |
| Readiness | One of the three Engage scores, estimating how close a contact is to acting; the other two are fit and intent. | Engage Scores |
| Recommendation | A related page suggested to a reader by your site — plan-gated, see Feature Availability by Plan. | Recommendations |
| Required field | A field a page type marks mandatory; publishing is blocked by a Missing fields dialog until it is filled in. | Configuring a Page Type |
| Resource override | A grant that raises one person’s access on one specific page, label or page type above what their role gives them. | Resource-Level Access Overrides |
| Revert | Discarding an unpublished revision so the live page stands as it was. | Revisions, Versions and Reverting |
| Revision | The unpublished edit of a page that is already live, held separately until you publish it. | Revisions, Versions and Reverting |
| Role | A workspace member’s baseline access level, one of six, which overrides can raise but never lower. | Roles and Permissions |
S–Z
| Term | What it means | Where it’s documented |
|---|---|---|
| Scheduled | A page set to publish itself at a future date and time, which then queues its own deployment. | Scheduling and Automatic Publishing |
| Search index | A named set of page types whose pages are searchable together on your published site. | Search for Your Documentation |
| Series | A label configured as an ordered run of pages, so templates can render “part 2 of 6” and link the neighbors. | Labels and Series |
| Short link | A branded short URL that redirects to a longer one and records the click — plan-gated, see Feature Availability by Plan. | Short Links and Attribution |
| Shortcode (template) | In a Leed template, another name for a Handlebars helper — nothing to do with the Engage section of the same name. | How Helpers Work |
| Shortcodes (Engage) | The Engage section holding your tracked short links, which is what “Shortcodes” means everywhere outside a template. | Short Links and Attribution |
| Site repository | The Git repository behind your workspace, holding your site’s layouts, partials, styles and static files. | Your Site Repository |
| Slug | The last segment of a page’s URL, derived from its title when the page is created. | URL Paths and Slugs |
| Stage (UI) | The rounded white card the CMS renders the current screen inside, beside the rail. | Touring the Workspace |
| Suggesting mode | An editor mode where your edits become tracked suggestions for someone else to accept or reject rather than changing the page outright. | Suggesting Mode and Tracked Changes |
| Summary | A page’s one-sentence description, used in listings and social cards and required before publishing on page types that demand it. | Page Settings |
| Tab group | A named set of tab titles and icons that keeps a reader’s choice — their operating system, their MCP client, their language — in step across every page that uses it. | Tab Groups for Consistent Examples |
| Target date | The date you intend a page to go out, drawn on the Plan calendar; unlike a schedule it publishes nothing. | Core Concepts |
| Theme | The color scheme applied to your documentation; choosing among the built-in themes is free, naming your own is plan-gated, see Feature Availability by Plan. | Themes, Fonts and Code Themes |
| Tier | One rung of the plan ladder: Free, Starter, Growth or Enterprise. | Plans and Tiers |
| Tracked change | One suggested insertion or deletion, shown on a card with accept and reject controls; tracked changes never reach your published content. | Suggesting Mode and Tracked Changes |
| Turnstile | Cloudflare’s challenge widget; when a key is configured, Leed records whether each form fill passed it. | Spam Protection and Turnstile |
| Two-phase confirmation | The pattern risky MCP tools use: the first call returns a preview of what would change, and only a second call carrying confirm: true executes it. | What the Operator MCP Can and Cannot Do |
| Upgrade prompt | The panel or banner the CMS shows in place of a screen your plan does not include. | When a Feature Is Gated |
| Version | The v2, v3 chip beside a page’s title, counting its revisions — not the same as the site version a deployment activates. | Revisions, Versions and Reverting |
| WebMCP | The in-page tool interface your published site registers so an AI agent running in a visitor’s browser can query it without an API key. | Site AI Agent |
| Workspace | One site, one team, one domain, one plan — the container everything else in Leed sits inside. | Joining and Switching Workspaces |