Your first space

A space is one surface of your site: your documentation, your community forum, your blog, your changelog, and so on. Your organization can hold as many spaces as you like, each with its own type, its own address, and its own visibility. Together they make up your site.

Every space's type decides what it is — what a reader arrives at, what a "piece" of content is called, what fields it carries, and what layouts it can wear. You picked your first spaces in the setup wizard; this guide covers adding more and choosing the right type.

Creating a space

From your organization, go to Spaces and choose to create a new one (/o/<org-id>/spaces/new). Creating a space is a single decision made in one screen.

1. Pick the kind

Choose one of the thirteen types (below). This is the most important choice — it shapes everything else — so you pick it first. Once you choose, the card collapses to show your pick, and the rest of the form appears. Use Change to go back to the grid.

2. Choose how it reads (where offered)

Some types honestly offer more than one layout. Where they do, you will see a How it reads row of named arrangements, each with a small sketch — for example a blog's Feed, Grid, or Magazine. One is recommended and preselected. Types with a single honest layout skip this step.

3. Start from a template (optional)

If a template exists for this type, you can start from it. A template is applied after the space is created, so if it fails to apply you still keep the space — you can pick another and apply it from the studio later.

4. Name it and set its address

Give the space a name and an address (its slug in the URL). The name suggests the address as you type. The live address line shows exactly where readers will find it — on your custom domain if you have one verified, otherwise as a path. Some slugs are reserved (like api); if you pick one, you are told before you create the space, not months later from a 404.

5. Choose who can read it

Set the space's visibility:

• Private — only your team.

• Public — anyone with the link.

You can change this later.

Press Create space. You go straight to the new space's studio, because the next thing anyone does with a space is look at it.

Custom spaces

If you pick the Custom type, you are also asked three questions up front — what readers arrive at (a landing page, a list, a board, or one page), how they move around (a page tree, categories, tags, sections, or nothing), and who may add to it (your team, signed-in members, or anyone who can read it). These are the questions that make a blog a blog and a forum a forum. You can change all of it later, and give a custom page its own named sections, in the space's settings.

The thirteen space types

Each type is a purpose, not just a template. In one line each:

A few things that follow from the type:

• What a piece is called follows the type. A documentation space holds pages, a forum holds topics, a blog holds articles, a roadmap holds items, a changelog holds releases, careers holds roles, legal holds documents, an FAQ holds questions, contact holds messages, status holds monitors.

• What a reader arrives at follows the type too — a documentation space opens on a landing page and a page tree; a forum opens on a list of topics grouped by category; a roadmap opens on a board of columns by status.

• Who may add content is part of the type: a blog's articles are written by staff, while a forum's topics can be started by members, and a roadmap's items suggested by members.

The space root is the studio

Once a space exists, its root in the console is the studio. There is no separate "edit" screen to open — you open the space and you are already looking at its live site with the editing panel beside it. Everything about the space (its content, its look, its settings, its housekeeping) lives in that one panel.

What's next

• Spaces and shapes — customizing a space's fields, sections, and layouts without code.

• Editing in the studio — the day-to-day editing surface.