Touring the Workspace

The Leed CMS is three things on one screen: a narrow dark rail down the left edge, a single white stage card holding whatever you are working on, and a small utility cluster at the bottom of the rail. The rail carries six destinations — Know, Design, Engage, Plan, Deploy and Chat, in that order — and the Leed arrow mark at the top of the rail takes you home. Everything else you will ever open in the CMS is reached from one of those six.

The rail

Each tab is one destination. The glyph is drawn in outline while the tab is inactive and swaps to a solid version, on a lighter tile, when it is the tab you are in.

The rail is organized around objects — pages, revisions, deployments, labels — whose meanings are fixed across every screen, and core concepts defines them once.

The tabs go different places than their labels suggest in two cases worth knowing up front. Design does not open a content list — it opens a two-part library workspace, and the Design workspace explains what each of its seven sections holds. Engage is the CRM side of the product rather than an inbox; the Engage workspace covers its three-zone shell. For the other four: Know is your performance home, starting at the Know dashboard; Plan is the Plan calendar; Deploy is where everything you have changed becomes public, traced end to end in how publishing works.

Each tab remembers where you were

The rail records the last path you visited under each tab and returns you there rather than to the tab’s default. Open Design and work on a form, switch to Engage, then click Design again: you land back on that form, not on the page tree.

The tab that is not highlighted

While you are editing a documentation page at /documentation/<id>, no rail tab lights up. Documentation pages sit under Design but do not highlight it. Nothing is broken — the left panel still shows the Documentation section and every control works — but two small consequences follow: the rail looks as though you are nowhere, and because the same lookup is what records your last-visited route, that visit is not remembered either. Clicking Design afterwards returns you to whatever you were on before, not to the docs menu. It is one of several small defects collected at known limitations.

The stage

Whatever you navigate to renders inside one white card with rounded corners, floating on the dark background with a narrow gutter around it. One card, one screen. There is no split view and nothing else renders beside the stage — the CMS never shows you two screens at once, so the rail plus the URL always tell you exactly where you are.

Where you land when you sign in

Visiting the root of the CMS redirects you to your home preference, which defaults to Know (/know). The preference is stored in your browser under leed.shell.homePage.

If your workspace is still being set up, the root redirect sends you to the Initializing screen instead of your home tab. That is expected on a brand-new workspace and is covered in workspace provisioning.

The utility cluster

Three controls sit at the bottom of the rail, below the five tabs.

Send feedback

The first opens a dialog titled Send feedback, described as “Spotted a bug or have an idea? Your current page is included automatically.” Choose a type — Suggestion or Bug — and write your message; the prompt above the box changes to What’s your idea? or What went wrong? to match. The path of the page you were on and your viewport size are attached automatically, and your identity and workspace are attached on the server, so you never have to describe where you were. On success the dialog closes and a toast reads “Thanks — your feedback was sent.”

Settings

The second opens /settings, a searchable grid of cards rather than a row of tabs. Press Cmd + K (or Ctrl + K on Windows and Linux) anywhere on that screen to jump into its search box. Settings home and the settings map lists every card and the page that documents it.

Your avatar

The third is your avatar, which opens the profile menu.

The profile menu

Belonging to more than one workspace is what makes Switch Organization appear at all — see joining and switching workspaces for how a second membership comes about and what changes when you switch.

Developer Setup hands you the one-line installer for the Leed CLI:

curl -fsSL https://app.leed.ai/install | bash

The dialog also lists its two prerequisites — Git and Bun — and points at the README.md in your raw-content repository for what to do next. Follow the whole path through at installing the Leed CLI.

Notifications are messages, not an inbox

Leed tells you about a completed action with a transient toast in the corner of the screen — File Saved, Page Type Created Successfully, Thanks — your feedback was sent. — and asks about a destructive one with a modal you confirm or cancel.

Old links still work

The rail replaced an older set of screens, and their URLs were kept alive rather than left to 404. /analytics redirects to /know, /schedule to /plan, and /library to /pages. A bookmark or a link in an old email lands in the right place; the complete list is at legacy URLs that still work.