flows.md · documentation
Site#
Every space that is somebody's answers at an address of its own: the space's name, without separators, under flows.md. The space @ana answers at ana.flows.md, and @jonas.porto at jonasporto.flows.md. Nothing to set up: the address exists from the moment the space is yours.
That address is a site, not the app. It shows only what anybody may read, and nothing else: nobody signs in, nobody edits, no cookie is written there. Editing stays at flows.md/@ana, as ever.
One address per page#
A public page has one address, on the site, in the short form: flows.md/@ana/post is read at ana.flows.md/post. That is the address search engines index, a link's card shows and the MCP's link answers. The address at the app still opens the same page, and tells Google which one is official.
A page whose short name means something else on the site (/core, /assets) keeps its long address, ana.flows.md/@ana/core.
The front page#
A space is born private, and every new page is born private. So the site needs a home: the front page, the page it opens on. One per space, chosen among the pages anybody may read, never the root. The front page answers at ana.flows.md/ and only there: its own address leads to /. The other public pages keep their addresses.
Where to choose, in any of three places:
- Site (Pro), in the sidebar, right below the Inbox: the site's address, today's front page and the pages that could be it.
- The … menu of a page in the sidebar: "Set as front page", or "Remove as front page" on the front page itself.
- The page's settings, beside the QR code.
Marking the first front page is one click. Marking another, while one exists, asks first, saying which page is the front page today. Changing the front page is how the site gets a new face without rewriting anything: write the new page, publish it, mark it.
With no front page#
If the space's root is public, it is the front page, as a whole site. If the root is private and no page is marked, the site shows a clean page: the space's name and the line "is still setting things up". Nothing inside is said.
A front page that stops being public keeps its mark, inactive, and the site goes back to the clean page until it is published again.
Arriving through the app#
A visitor who opens flows.md/@ana without being able to read the root is taken to ana.flows.md: the front page, or the clean page. A page shared with somebody still asks them to sign in, because that is how they reach it.
A blog#
A blog is a folder: each post is a page inside it. On the folder's page, one block lists the posts, newest first, with a date and a line each:
```@posts
```The date is the one the post gives in its meta (date: 2026-09-12), or the day the page was made. When the folder is public it also has a feed, for anybody following in a reader: ana.flows.md/blog.rss (RSS) and ana.flows.md/blog.atom (Atom). The feed holds only what anybody may read, and the list ends with both links.
Agents (MCP)#
front_page shows each space's front page, marks one (front_page ~/about) and unmarks it (front_page ~/about clear:true). details says whether a page is the front page and its address on the site; manual site explains all of this.
What comes next#
Your own domain, for the Pro plan: the space's site at the address that is yours, with the domain's root as the address.