Design Workspace

The Design tab is not a content list. It opens a two-part workspace: a persistent library panel down the left, and whatever you have selected in that library filling the rest of the stage. Six sections share the one panel — site pages, documentation menus, site menus, forms, email templates and assets — and a picker at the top of the panel switches between them without ever leaving the workspace.

The six sections

The picker lists all six in a fixed order, each with a one-line description of what it holds.

The chrome every section shares

The panel header is built once and never rebuilt when you switch sections, which is why switching is instant and why the panel keeps its scroll position and width. From top to bottom it is a search box, then a row holding the section picker, the filter button and the ＋ button.

Search

Each section supplies its own placeholder, so the box tells you what it will search. Search clears when you switch sections — the box belongs to the panel, not to the section, so a query you typed in Forms is gone when you come back from Assets.

Filter and sort

The filter button sits to the right of the picker and turns dark when a non-default filter is active. What it offers depends on the section.

Site gets the fullest popover. It carries a sort key — Name, Created or Published, with an arrow showing the direction, defaulting to Published descending — plus a My pages checkbox, a row of status pills (Published, Scheduled, Approved, In Revision, Draft and Site Builder, which is the facet for pages your site builder owns rather than the CMS), and a row of page-type pills built from your own page types. Toggling a pill does not close the menu, so you can build up a filter in one pass. Every part of it is remembered for the rest of your browser session, as is the set of folders you have expanded in the tree. Pages that belong to a documentation or API page type are left out of the Site section altogether — out of the tree and out of the page-type pills — because those sets are edited from the Documentation section.

Menus and Forms offer Name (A–Z) and Name (Z–A). Documentation offers the same two sorts plus a row of status pills — Published, Scheduled, Approved, In Revision and Draft, the Site pills without Site Builder — remembered for the rest of your browser session. With a status selected, a menu item whose page is in another status drops out, a folder stays only while something inside it matches, and external links drop out entirely; a menu left with nothing is hidden, and when every menu empties the panel says No matches. Drag-to-reorder is switched off while a status filter is on, because a reorder computed from a filtered tree would drop the hidden items; renaming, adding and deleting still work. Email templates offers Recently created and Name (A–Z), defaulting to Recently created. Assets offers a type filter — All, Images, Videos, Audio, Docs — under a Show heading.

The ＋ button

The ＋ appears only where something can be created from the panel. Five sections have it: Site creates a page, Menus a menu, Forms a form, Email templates a template, and Assets an asset. Hover it and the tooltip names what it will make.

Documentation has no ＋. It lists the navigation menus behind your documentation sets, and one is created for you automatically when you create a documentation or API page type — there is nothing to make by hand. Email templates loses its ＋ below Growth, because creating a template is a Growth feature; the templates you already have stay listed.

Resizing

Drag the right edge of the panel — the handle is labeled Resize left panel — to widen or narrow it.

The panel remembers where you were

Picking a section does not open the first item in it, and it does not always open the section’s default. It opens the last item you opened in that section, this browser session — and only that.

flowchart TD
    A[You pick a section] --> B{Have you opened an item<br/>in this section this session?}
    B -->|Yes| C["That item reopens — e.g. /forms/abc123"]
    B -->|No| D["The section's bare landing — e.g. /forms"]
    C --> E[The panel stays visible either way]
    D --> E

Each section keeps its own memory, so a site page, a documentation menu and a site menu never collide — switching Site → Menus → Site lands you back on the page you were writing. The memory is session-scoped: a fresh tab, a new window or a reload starts empty, and you get the bare landing instead. That is deliberate. Reopening an item you never chose, on a machine you may share, is worse than an empty editor.

What the bare landings say

Every section has an empty state, and it is worth recognizing it as “nothing selected” rather than “nothing here” — the panel beside it is fully populated and usable.

The URL always tells you where you are

Every section owns a real route, and the panel keeps the URL in step even when nothing is selected. So /forms/<id> opens the Forms section with that form loaded, /documentation/<id> opens the Documentation section with that menu loaded, and /menus opens the Menus section with nothing selected — the URL is never ambiguous about which library you are in. That makes any view in this workspace a link you can send to a colleague, who will land exactly where you did as long as their permissions allow it.

Where each section is documented

The Site section’s tree, its status glyphs and its filters are the subject of managing pages, and opening any item from it puts you in the editor described by the page editor. Documentation lists the left-nav menus behind your documentation sets, where the left navigation menu covers folders, ordering and the rule that a page may appear in exactly one menu. Menus is where the rest of your site navigation is built — see building and editing a menu. Forms opens the builder documented at building a form. Email templates lists your own templates and the built-in starters under separate headings, below the shared Brand settings row; email layouts covers what a template holds. Assets is the media library, and the asset library is where to start; it is the only asset screen in the CMS, so anything describing a separate media manager is out of date.