Changelog

You published something. Is anyone reading it? Now you can see at a glance, without setting up Google Analytics or adding a script.

• A number on every site card. Your dashboard shows "412 people in the last 30 days" under each site. Click it to see more.
• An Analytics tab for each site. People and views over 7 or 30 days, a daily chart, your top pages by title, and the sites your readers came from.
• Nothing to set up. It's on for every site, on every plan, from today. Counting started on 12 November, so there's no earlier history.
• No cookies on your readers. Visits are counted without cookies, and numbers update every 10 minutes.

The screenshot above uses sample numbers.

Good to know

• The numbers are estimates. People who use ad blockers aren't counted, and your own visits are included.
• Raw .html pages and password-protected sites aren't counted yet.
• If you already use Google Analytics or Umami, it keeps working alongside.

Fixes

• The daily chart now always covers the full 7 or 30 days, with dates and a scale, so a few days of data no longer stretch across the whole width. Pages and sources sit side by side.

More in Analytics.

Your site can now have a reading layout. Add "layout": "reading" to config.json and pages get a centred reading column, their page contents as a rail of ticks at the far left, and the site contents behind a menu button at the top left. Ordinary pages get previous and next links in the order of the site contents, so readers can move through a course or a set of essays without opening the menu.

The default layout, now called docs, is unchanged: site contents on the left, page contents on the right. Set layout: docs or layout: reading in a page's frontmatter to change one page. For a home page that keeps the site contents while the pages behind it use the reading layout, set the site to reading and the home page to docs.

See Site layouts for the recipes and the rules.

You can now show no logo at all in your navbar, not even the Flowershow logo that appears when you haven't set one. Turn off Show Logo under Settings → Navigation, or set "showLogo": false in config.json. See Navbar configuration.

Fixes

• Logos uploaded in the dashboard keep their shape. They used to be cropped to a thin strip and stretched into a square, so they looked zoomed in. If you uploaded your logo before today, upload it again.
• Replacing a logo, favicon or social image in the dashboard shows the new image right away, instead of the old one for a while.
• Adding a custom domain no longer sends visitors of a public site to it before the domain works. Your pages stay reachable on the Flowershow address until your DNS is set up, then redirect to your domain.

The Flowershow connector can now sign in to your account. Add https://flowershow.app/api/mcp as a connector in Claude or ChatGPT. You can publish straight away without an account; when your AI needs your account, sign in and choose Allow. From then on your AI publishes to your account, and the connector is no longer a beta. See Publish from Claude and ChatGPT.

• Your sites, in any conversation: ask for "my team site" in a new chat and your AI finds it, checks which pages it has and updates it. New sites go straight into your account, with no claim link and no 7-day expiry.
• Edit without losing anything: before changing a page, your AI reads its current text, so the rest of the page and the site stay as they are.
• Sites shared with you: if you're an editor on someone's site, your AI can publish to it too.
• Keep a site you made without an account: if you published without signing in earlier in the conversation, ask your AI to keep the site and it moves into your account.
• You stay in control: see the apps you've connected under Connected apps on the Access tokens page, and revoke any of them there.

If you added Flowershow with https://flowershow.app/api/mcp/account before, remove it and add https://flowershow.app/api/mcp instead. Connectors added with https://flowershow.app/api/mcp keep working.

Running a site with other people no longer means sharing a login. Open your site's Members tab and enter an email address, and that person gets an invite. Once they accept, they can publish to the site and manage it with you. See Invite editors to a site for the details.

• You stay the owner. Editors can publish, change settings and site config, turn password protection on or off, and moderate annotations. The custom domain, root directory, renaming, the GitHub connection, inviting and removing people, billing and deleting the site stay with you.
• Invites go to one address. A link lasts 14 days and only works for an account with that verified email. Signing in with an email link is enough, so editors don't need a GitHub account.
• Included with Premium. No charge per editor, up to 20 editors per site. If Premium lapses, editors lose access until you renew, and nobody needs inviting again.
• Publish from the terminal. Update fl, then fl list shows shared sites as owner/name and fl --name owner/name --overwrite <folder> publishes to one. AI tools that connect with a personal access token can publish to them too, but Claude and ChatGPT connectors can't yet, and neither can the Obsidian plugin.

Publishing a folder with fl replaces the whole site, so two editors publishing from different folders overwrite each other. Agree on one source for the site; the History tab shows who published each run.

When annotations are on, a comment no longer has to be the last word. Answer a reviewer's question, explain why you kept a sentence, or let your agent say what it changed, all next to the words in question.

• Reply on the page. Click Reply under any comment. No account needed, and your name is remembered. Replies from the site owner show an Author badge.
• Anyone can resolve. When a point has been dealt with, click Resolve. The comment moves to the Resolved group with who resolved it, and its highlight goes. Reopen brings it back. Deleting is still for the site owner only.
• Your agent closes the loop. fl annotations reply <id> -m "…" answers a comment, and fl annotations resolve <id> -m "Added an example" replies and resolves in one step. fl annotations pull now includes each comment's replies. Needs fl 2.10.0 or later.

Fixes

• The comments panel now runs the full height of the window on wide screens, above the site's navigation, and uses your site's interface font. Writing a comment and the list of comments are quieter and easier to read.

You can now show the page contents as a rail: a column of short ticks in the right-hand column, one per heading. The current section's tick is longer and in the accent colour. Hover or focus the rail to open the outline, then click a title to jump.

The rail is opt-in. Set "toc": { "style": "rail" } in config.json, or toc: { style: rail } in a page's frontmatter. See Table of contents.

Fixes

• Narrow screens (phones, tablets and, for the classic panel, small laptops) now get a Contents block on long pages

When your AI publishes to one of your sites through the Flowershow connector, it sends only the pages it adds or changes, and everything else on the site stays as it is. Removing a page happens only when you ask for it.

In a new chat, though, your AI doesn't remember what the site already has. Two new connector tools fix that:

• list-files shows the files on a site, so your AI can see which pages exist before it adds one or removes one.
• read-file gets the current text of a page, so when your AI changes a page, for example to link a new page from your home page, it keeps what was already there.

Both work only on sites in the account you signed in with. Reconnect the connector, or start a new chat, if your AI doesn't see the new tools yet.

Anything you publish can be read by anyone with the link. So when your AI assistant publishes with the Flowershow skill, it now tells you which files are going out, to which site, and anything it will remove. This applies to a first publish, an update, an anonymous site and the Claude/ChatGPT connector.

There's no extra confirmation step when nothing needs one. Your assistant stops and asks first only when:

• a file looks private, such as drafts, personal notes, or data with names or emails;
• the publish would delete files from your site;
• the files aren't what you asked for, such as extra files in the folder, or a new site you didn't ask to publish.

Update the skill to get this: re-run the install command on the Skills page.

From October 18, pages you published or updated didn't reach your site's search index, though the publish itself succeeded and the pages were live. Sites created in that week had no search results at all.

Publishing adds pages to search again, and we've re-indexed every page published during the outage, so you don't need to republish anything. Search is turned on with enableSearch in config.json.

Fixes

• After you overwrite a site, navigation, wiki-links and the index page now refresh the moment your last file is processed, instead of staying stale for a few seconds.
• fl no longer says "Already in sync" right after another folder overwrote the same site. Files that are still being processed or were just deleted count as changed.
• A page that search can't index because of its frontmatter (for example a description that isn't plain text) now shows an error in your publish output and publish history, such as Not added to search: Field `description` must be a string. Before, it was silently left out of search. A single author written as authors: Ada instead of a list is indexed as usual.
• Unpublished pages (publish: false), drafts and deleted pages are now removed from your site's search. Before, they could still show up in search results after they were taken down. We've cleared these stale entries from every site.
• A draft (draft: true) that links to a published page no longer shows up in that page's "Links to this page" list or in the graph view, so its title isn't shown on your published pages.
• Opening a page you just unpublished or deleted now shows "Page not found" instead of an "Internal Server Error" page.