Skip to content
Docs Flowy
Public sites

Publish named releases of your Handbook

Each project's Handbook can have a public site. You choose which approved changes go out, you name the release, and you decide who can open it.
The address

One address per team, one path per project

A site lives under your team's own subdomain of docsflowy.site. The path starts as the project's slug. Change it and the old one redirects for 90 days.

{team}.docsflowy.site/{project}
Sample addresslarkspur.docsflowy.site/payments
Team is the source

Public arranges. It never writes.

Every word on the site was approved in the Team Handbook first. The public side is a structure of entries, each pointing at one Team page.

  • An entry carries its place, its folder and its public title. Its text mirrors the Team page and cannot be edited on its own.
  • A link to a Team page with no public entry renders as plain text, so an internal page never leaks as a URL.
  • Shared folders publish validated repository documents too: the reviewed bytes, with the next release.
Releases

A release is chosen and named

Unreleased changes wait in a list, all ticked by default. Untick what is not ready; anything a ticked change depends on comes with it.

  • A name is required, up to 60 characters, and prefilled from the last one: v1.4 becomes v1.5.
  • Preview the site as the release will compose it before you publish.
  • The name is the changelog heading, the RSS item title and the subject of the email subscribers receive.
Readers follow along

Changelog, RSS, email and llms.txt

Changelog
Every release is listed on the site with the pages it changed.
RSS
The same releases as a feed, for readers who keep a feed reader.
Email
Readers subscribe with an address and confirm it before anything is sent. Each release can notify them.
llms.txt
Lists the site's pages for agents, each one available as Markdown. On by default; a setting turns it off.
Who can read it

Three ways to open a site

Pick one per site. A site behind a password or team sign-in is never indexed: its pages send noindex and its robots.txt disallows them.

Anyone

Open to everyone and indexable, with a sitemap for search engines.

Password

Eight characters or more. A correct password keeps the reader in for seven days.

What the reader sees

Enter the password to read this site.

Team sign-in

For people in your organization who can read the project. The pass lasts 12 hours and never outlasts their console session, so signing out of Docs Flowy signs them out of the site.

What the reader sees

This site is for the Larkspur team.

Sign in with Docs Flowy
Not on the site

No public board and no comment screen

The site is for reading. The Board and notes stay inside Docs Flowy, where agents reply and people close them. A visitor cannot see your workflow or post to it.

Plans

Starter and up

The public site is part of Starter, Team, Business and Enterprise; the site on your own domain and email subscriptions start at Team. On Free the Team Handbook works and the site is not served. A downgrade deletes nothing: upgrade again and the site returns as it was.

Compare plans

Publish your first release

Start a Handbook, add pages to Public and name the release.

Start free