Publish a folder, or a whole root, as a read-oriented site on the content host or your own domain, with the folder tree as navigation, index pages, search, table of contents, backlinks and opt-in search-engine indexing.

The navigator is organized by where things live, and it already reads like a wiki: folders with index pages, a manual order, shortcuts. The wiki is that same tree, published. Choose Publish on a folder or on a root and it becomes a site for people who only read: a new hire, a client, the rest of the company.

Publishing a folder

Open the folder in the app and choose Publish. The dialog has the on/off switch, Who can read it (public, signed-in readers, or one group) and the site's address with a copy button. In a shared root, workspace owners and admins publish; in My documents you publish your own folders. Agents do the same with set_folder_meta, and only when you ask.

What you get:

The folder tree is the navigation. Subfolders and documents appear in the left sidebar in the folder's manual order; shortcuts appear where they were placed.
Index pages are landing pages. A folder with an index page opens on it, with the folder's children listed beneath. A folder without one shows its name and the list.
The site's home is the root: its title is the root's name.

Host	A published folder
Shared content host	`https://fermiumusercontent.app/w/@<workspace>/r/<root-slug>/<folder path>/`
Your custom domain	`https://docs.acme.com/w/r/<root-slug>/<folder path>/`

A document's page is the folder address followed by its alias, or its id when it has none. The audience settings, how subfolders inherit them, the scope rule (only documents inside published folders are served) and the rule that document visibility still applies are on Roots and folders.

If your workspace has a agent-tree wiki, its appearance (accent colour, logo, footer) is used by published folders too.

What a page shows

The header carries the site title or logo, the tagline, a search box and either Sign in or the reader's email. The left column is the navigation. The main column shows breadcrumbs (the folder path), the document, and a footer with:

Last edited: how long ago, which channel wrote the version, and the version number;
Linked from: documents in the wiki that link here through [[wiki links]];
Edit this page for signed-in members who may edit the document, which opens the browser editor;
History for signed-in members who may view it, which opens the document's Versions tab in the app;
Copy link.

On wide screens a right column, On this page, lists the headings of a markdown document.

How the document itself renders depends on its kind. Markdown and snippets are rendered from their source; raw HTML inside markdown is escaped on wiki pages. [[wiki links]] that point at documents inside the wiki lead to their wiki pages; other references keep working through the resolver. An HTML document is never rewritten or inlined: it renders inside a sandboxed frame that loads the document's own /d/ address on the same host, with an Open full page link beneath it. A file share shows its image, video or audio inline, a download card and its description.

Search

The search box searches the text of every document in the wiki, ranked, with a highlighted excerpt and the document's place in the navigation under each result. Results respect the reader: someone who is not signed in searches unlisted documents in the wiki; a signed-in reader also searches the Restricted documents they may open; password documents never appear in results. Browsers that support OpenSearch can add the wiki as a search engine from the page. Search pages are never indexable.

Search engines

Everything on the shared content host is served with noindex, nofollow and stays that way. A workspace on the Team plan or above with an active custom domain can turn on Allow search engines: open Settings → Wiki, choose an agent, and use the switch in its wiki settings. The switch refuses to turn on without both, and turns itself off if the domain stops being active. The one switch covers published folders and any agent-tree wiki alike.

With indexing on, for that domain:

wiki pages of unlisted documents, and the home, folder and tag pages, drop the robots restriction and carry a canonical link plus Open Graph title, description and image (the logo), so links unfurl in chat tools;
/robots.txt allows /w/, disallows /d/ and /x/, and names the sitemap;
/w/sitemap.xml lists the home page, the folder and tag pages, and every unlisted document in the wiki with its last-modified date, exactly as an anonymous visitor would see the sidebar.
a published folder has its own sitemap at /w/r/<root-slug>/sitemap.xml, built the same way.

Password and Restricted documents never carry indexing metadata, and search results pages are always noindex. Documents outside the wiki stay noindex on /d/. The effect is one indexable copy of each page, on your domain, only for pages a person placed in the wiki, only when the workspace asked.

Agent-tree wiki

Some workspaces publish a wiki from an agent's navigation tree instead of a folder. It is served at /w/@<workspace>/ on the content host and at /w/ on a custom domain, next to published folders under /r/, and is managed under Settings → Wiki by workspace owners and admins. Only documents the tree reaches are in it, and each document's visibility applies as it would for a direct link. Agents manage it with get_navigation, set_navigation, publish_home and get_wiki_site; see the MCP reference.