Editing in the studio

The studio is where you build and edit a space. It is not a form that describes your site from a distance — the page in the middle of the screen is your site, the real reader view on the app's own address, and the panel beside it is everything that changes it. Hover a region and it outlines; double-click it and the panel becomes its inspector; every save refreshes the page in place.

This guide covers day-to-day editing.

The layout

When you open a space you get three things:

• The canvas — your live site, filling the middle. For a private space this is a preview through a rotating share link, so nothing becomes public just to be looked at.

• The panel — on the right, organized into four folds: Pages, Look, Settings, and Housekeeping. What you learn on one space's panel is true on every other — the folds are always the same four, in the same order.

• The top bar — the space name and type, a Desktop / Phone width toggle to preview at either size, a ✓ Saved indicator that appears briefly after each save, and Open site ↗ to open the real page in a new tab.

The studio is a desktop surface. On a narrow screen it tells you so; the panel and its sheets need the room.

Editing text in place

Single-clicking behaves like the real site — links navigate. To edit, double-click. Hovering first shows you exactly what a double-click would select.

• Double-click a heading, a paragraph, a title, or a nav link and the panel becomes its inspector.

• Where the thing is your own writing, you edit the words directly. Body prose is edited in a markdown editor that lives in the panel, never on the page — the block being edited is highlighted on the canvas, and you type over on the right, always in the same place.

• Text that is really a setting — a page title, a nav link, the space name, a banner — is edited through the real setting behind it, so the change sticks everywhere that text appears.

Content that belongs to other people — a member's forum post, say — is reader content. You can moderate it, but it is not yours to rewrite.

The inspector: styling one element, or all of them

When you select an element, the inspector also lets you style it — its font, its look — and paints the change onto the live element immediately so you see it at once. Saving stores it as a style rule in the space's theme.

A switch lets you choose the scope: style this one element, or every element like it in the space. The raw CSS selector never shows — you read "every paragraph", and the switch is the choice. Press ✕ or Escape to hand the panel back to the space.

Structure: pages, groups, and reordering

For page-based spaces (documentation, FAQ, careers, legal, custom), the Pages fold holds the space's structure — the same tree the reader's navigation is built from.

• Add a page — type a title in the field at the foot of the tree and press Add. The new page is a draft; the canvas walks to it and its title opens for typing. You never leave the studio.

• Reorder — drag a page within the tree to reorder it, or drag it onto a group's header to move it there. The site reorders to match.

• Groups (collections) — add a group with the + button below the tree. Rename or delete a group from its own row, or edit its introduction with Hub intro. Deleting a group deletes its pages with it.

Other space types bring their own manager into the Pages fold — a forum's Topics, a blog's Posts, a roadmap's Board, a changelog's Releases, a status page's Checks. The dense ones open as a sheet over the canvas so they have room to work; while a sheet is open the panel steps back.

Structural entities: categories, lanes, statuses

The things that organize a space — a forum's categories and tags, a roadmap's lanes and statuses — are edited in two ways:

• In place. Double-click one on the live page and its card opens in the panel to rename or edit it.

• From the panel. A forum's Categories and tags and a roadmap's Lanes and voting live under the Settings fold as their own managers.

Adding content by type

How you add a piece follows the type. For page-based spaces, the tree's own input creates a page. For the others, the primary action opens that type's maker — a new topic, a new article, a new release. (A contact space is the exception: readers write the messages through the form, and your team answers them from the inbox.)

Undo and redo

Structural changes — a delete, a move, a rename, a field edit — are undoable. After a change, a small toast appears at the bottom of the canvas naming what just happened, with a one-click Undo. After an undo, the same toast offers Redo.

Keyboard shortcuts work too: Cmd+Z (Ctrl+Z) to undo and Cmd+Shift+Z (Ctrl+Shift+Z) to redo, and they walk the whole history, not just the last step.

Saving

There is no separate save button for content — the studio saves as you work, and shows ✓ Saved briefly after each write. While you are still typing in a text field, the canvas holds its refresh so it does not flicker mid-sentence; the moment you look up, it refreshes once. Switches and pickers apply promptly.

The other folds at a glance

• Look — the front door (the words at the top, the arrangement/layout, what the listing shows), the theme/design, and the content library.

• Settings — the space's shape (see Spaces and shapes), who can read it, its address and domains, reader settings, developer/integration settings, and saving the space as a template.

• Housekeeping — the things done rarely: imports, comment moderation, trash, and (for docs) the glossary.

What's next

• Publishing and domains — making the space public and putting it on your own domain.

• Spaces and shapes — reshaping what a piece contains.

For AI agents

• This page for a human reader: https://forumulate.com/guides/editing-in-the-studio

• The whole space as one Markdown file: https://forumulate.com/api/public/orgs/046a9bc0-d530-43ae-9bae-af7945008cda/spaces/36aa4df0-1e95-4cef-8ae9-795169441345/llms-full.txt

• Live search + fetch over MCP: https://forumulate.com/api/public/orgs/046a9bc0-d530-43ae-9bae-af7945008cda/spaces/36aa4df0-1e95-4cef-8ae9-795169441345/mcp

  • Install (Claude CLI): claude mcp add forumulate-docs --transport http https://forumulate.com/api/public/orgs/046a9bc0-d530-43ae-9bae-af7945008cda/spaces/36aa4df0-1e95-4cef-8ae9-795169441345/mcp

This Markdown is the same content the page renders — safe to quote and to ground answers in.