Publishing and Sharing Your Site

Intermediate

Pin a version, share the link, and control what readers see while you keep editing.

Editing your model does not change what readers see. A publication serves a snapshot that you pin deliberately.

Publish

In the publication's properties, click Publish (pin current version). Metapad snapshots the model exactly as it is and serves that to readers; the panel changes from Not published to Published.

Then keep editing freely. Readers stay on the pinned snapshot until you click Republish (pin current version).

Live versus Published

The viewer has two modes:

  • Live — the model as it is right now. Use it to check your work.
  • Published v3 — the pinned snapshot readers actually get.

Open live view and Open published view open each of them. The published view only becomes available once you have published.

The address

A published site lives at an address of this shape:

/publication/{model-id}/{slug}

Share that link. Readers need to know nothing about Metapad to use it. A page has its own address (…/{slug}/{element-id}), and a language prefix such as /de/publication/… opens the site in German.

Who can open it

Access follows the model's visibility in the Share dialog. If it is Public (Anyone with the link can view), anyone with the link can read the published version, with no account and no login. Otherwise only the people the model is shared with can. A signed-in reader without access sees You don't have access to this publication.

Publishing itself needs the Team plan and edit access to the model.

What readers get

  • The site map in the sidebar, from your navigation tree. Readers fold and unfold it as they like. The Show current page button at the top of the site map unfolds it to the page they are on and scrolls there. Drag the divider between site map and page to widen it for a deep tree.
  • Clickable diagrams: a node in a diagram links to its own page with one click, if that element is part of the publication. Diagram-link cards are shown but don't navigate on the published site.
  • Search pages… across the whole publication (type at least three characters).
  • The AI assistant, to ask questions about the content, if AI is enabled for the model and the publisher's plan includes it. The reader's own plan doesn't matter; usage counts against the publishing team's AI allowance. Suggested questions from your greeting appear as buttons (see Branding Your Publication).
  • Their own language: when the model has more than one, language buttons in the site header switch between them. Charts, value tiles and tables follow the site's language too, including the number format.

The graph explorer

The graph explorer gives readers an interactive graph next to the pages, so they can follow how things connect.

  1. In the publication's properties, tick Graph explorer.
  2. Publish again (Republish (pin current version)). Readers only get the explorer after you republish.

Readers then see a Graph explorer button. When they open it:

  • The graph follows the page. It centres on the element of the page they are reading and shows its neighbours. Opening another page moves the graph with it, and Back to the open page brings it back after they have wandered.
  • Clicking a node opens its page. A node without a page of its own adds its neighbours to the graph instead.
  • Hovering shows a card with the node's type, the start of its description and its key properties. The card has Open page and Show connections, which adds the node's neighbours without leaving the page. On a touchscreen, the first tap shows the card and a second tap goes on.
  • On a phone, the explorer opens as a panel at the bottom of the screen.

Graph explorer on a C4 publication page, with a hover card

The explorer on the App Server page of the C4 template's site, with the card of the Database node.

What the explorer shows. By default it shows the elements that have a page and the elements on the publication's diagrams. To choose exactly what readers see, pick a stored filter under Explorer shows. Anything the filter leaves out is hidden, even if it has a page. If the filter is later deleted, readers see the default selection again until you choose another one.

The explorer only ever shows the published snapshot, so it never reveals anything readers couldn't already see.

Keeping a site out of search engines

Tick Hide from search engines in the publication's properties, below Show IDs to readers. Search engines are then asked not to list the site or follow its links. The setting takes effect right away, without republishing; pages a search engine has already listed drop out the next time it visits them. Use it for a site that copies content published elsewhere, or one that isn't meant to be found.

Unpublishing

Unpublish takes the published version down. The publication and all its content stay exactly as they are; only the reader-facing snapshot goes away.

Publishing on your own domain (Enterprise)

On the Enterprise plan, a publication can be served at your own address, such as handbook.example.com. Readers who open the address land on the publication's homepage; the pages themselves keep their usual paths. If your organisation signs in with its own identity provider, readers can be sent straight to your company login. transentis sets this up for you: contact us with the domain you'd like to use.

You are reading an example: this help is published from a Metapad model and served at docs.metapad.ai.

If publishing does not work

  • Publishing requires the Team plan — the model's owner needs Team.
  • Someone else was saving this model at the same moment — nothing was changed; publish again.
  • All pinned version slots are in use — unpin a version in the model's version history, then publish again.

This content was written collaboratively with AI.