$mdflow
$mdflow publish ./docs

A knowledgebase out of documents you already have

Group, publish, search. No build step, no static site generator.

start free →how sharing works
A published MDflow knowledge base: a document sidebar on the left, a rendered homepage document in the middle, and a visitor search box above the file list.
What the reader gets: a homepage, a sidebar, and search. No account needed.
$cat the-problem.txt
“Publishing internal docs means standing up a whole site.”

The documents exist. They are written, they are correct, and they are sitting in a folder. What stands between them and a link you can send is a static site generator, a theme, a config file, a build, a repository and somewhere to deploy it — and then the same again every time someone edits a paragraph.

A collection skips all of it. You choose which documents belong together and turn sharing on. The published knowledge base reads from the same documents you edit, so there is never a build to remember or a deploy that is out of date.

$mdflow kb --steps

Three steps, no toolchain

  1. 01

    Group

    Make a collection and add documents, or whole folders in one go. Pull from any workspace — collections are deliberately cross-workspace.

  2. 02

    Pick a homepage

    In Knowledgebase mode, one document renders at the share root, and the sidebar gains a Home entry pointing back at it.

  3. 03

    Publish

    A public link anyone can open, or a private invite by email. Either way there is nothing to build and nothing to deploy.

$mdflow collections

Collections: a reading set, not a move

A collection groups documents for readers without disturbing how you file them for yourself.

  • Documents or whole folders. Add a single document, or add a folder and every document inside it comes along. Nothing is moved and nothing is copied — the collection is a view over documents that stay where they are.
  • Across every workspace. When you build a collection you pick from all of your workspaces at once, grouped by workspace. Search and the sidebar are scoped to one workspace; collections are not.
  • One document, several collections. The same onboarding note can sit in the customer knowledge base and the internal handbook without being duplicated. Edit it once and both update.
  • Filed how you like, published how they need. Your folder tree is organised for writing. A collection is organised for reading. They do not have to agree.
Building an MDflow collection: the sidebar tree lists documents and folders grouped by workspace with tick boxes marking the ones in the collection, while the panel beside it shows the file count and the Knowledgebase share presentation with its homepage document.
Pick documents and whole folders, from any workspace.
$mdflow kb --mode knowledgebase

Knowledgebase mode

A collection share renders one of two ways: the folder structure, or Knowledgebase. Knowledgebase is the one that reads like a documentation site.

  • A homepage at the root. Pick any document in the collection and it renders directly at the share link's root URL — so the link you send lands on an introduction, not a file list.
  • A Home entry in the sidebar. Readers can always get back to the homepage from anywhere in the knowledge base.
  • Search for visitors. Full-text search across the collection's documents, run by the reader without an account.
  • Both share modes. Knowledgebase presentation applies to the public link and the private email-ACL view alike — the same reading experience either way.
$mdflow search --as-visitor

Search that behaves for readers

Visitor search is deliberately forgiving, because the person searching does not know your vocabulary yet.

  • Language-neutral. No stemming dictionary to pick and no language to configure. It behaves the same whether the knowledge base is in English, Czech or German.
  • Diacritics-insensitive. Typing ucetnictvi finds účetnictví. Readers should not have to reproduce your accents to find a page.
  • Prefix-matching. Typing private finds privately, so partial words still land. You do not need to guess the exact form of the word.
  • Encrypted documents are never searchable. The server holds only ciphertext for those, so there is nothing to index. That is a property of client-side encryption, not a setting.
$mdflow share --public | --email

Publishing: to everyone, or to eight people

The same knowledge base, two audiences. Both modes render identically; only who can open the link changes.

  • A public link. Read-only, openable without an account, on a long random URL designed to be hard to guess. Turning sharing off invalidates it permanently; turning it back on mints a fresh one.
  • Private by email. Invite specific addresses instead. Recipients sign in with the invited email, see it under “Shared with me”, and you can revoke one person or everyone at once, immediately. Pro.
  • Your own domain. Connect one custom domain in Settings and share links are offered on it, with the permanent mdflow.cz URL still available so nothing you already sent breaks. Pro.
  • Comments, if you want them. Optional per share. Readers comment on a selected passage and you moderate from your normal editor.
$mdflow reader

What the reader actually gets

A clean reader with your documents in it and none of your workspace around it.

  • A file list they can navigate. The collection's documents in a sidebar, opened in a clean reader with none of your workspace around it.
  • Three ways to read. Rendered preview by default, read-only markdown source, or a side-by-side split on larger screens.
  • Take a copy. Download any document as its original .md, or run it through a print-ready PDF flow.
  • No account, no install. Public knowledge bases open for anyone with the link. Signing in is only needed to comment or to clone a private copy.
$cat limitations.txt

What it doesn't do

A collection is a flat reading set. That keeps it quick to assemble and quick to reason about, and it does mean these are missing:

  • No nested collections. A collection cannot contain another collection. Adding a folder brings its documents in, but the published structure stays one level deep.
  • No custom theming. You get the MDflow reader — your own domain, but not your own CSS.
  • No per-page access control. Sharing is set at the collection level; you cannot open one document to the public and keep its neighbour private inside the same share.
  • Knowledgebase mode needs Pro. Without it, a shared collection still works — it just presents as the folder tree, with your settings kept for later.
$man mdflow-kb --faq

Questions

Is this a static site generator?
No, and that is the point. There is no build, no generator config, no repository and no deploy step. You group documents into a collection and turn sharing on; the knowledge base is served live from the documents themselves, so editing a document updates the published page immediately.
What is the difference between a folder and a collection?
A folder is where a document lives — one folder per document, inside one workspace. A collection is a reading set assembled across folders and across workspaces; a document can be in several collections at once without being moved or duplicated. Folders are how you file, collections are how you publish.
Do I need Pro for a knowledge base?
Collections and public collection sharing work on every plan, presented as the folder structure. Knowledgebase mode — the homepage document at the share root, the Home entry, and visitor search — is a Pro feature, as are private sharing by email and connecting your own domain.
What happens to my knowledge base if Pro lapses?
The share stays up and keeps working. It falls back to the folder-structure presentation, and your Knowledgebase settings — including which document is the homepage — are kept, so it returns exactly as it was if you subscribe again. Nothing is deleted and no link breaks.
Can I publish it on my own domain?
Yes, on Pro. Connect one custom domain in Settings; MDflow shows the DNS records to add and reports the connection status while DNS propagates. Sharing panels then offer both the custom-domain URL and the permanent mdflow.cz URL, so the original link never stops working.
Can an AI agent keep the knowledge base up to date?
Yes. Anything that can write a document body over the HTTP API or MCP can add to and revise the documents a collection points at, and the published knowledge base reflects it right away. That workflow — and the audit trail that makes it safe to allow — is covered on Let agents maintain a knowledgebase.
$ls ../related

Related

$mdflow share --collection

The docs are written. Send the link.

Group what belongs together, choose a homepage, turn sharing on. Editing a document updates the published knowledge base straight away — there is no build to run.

start for free →see pricing

Collections and public sharing are on every plan. Knowledgebase mode, private email sharing and custom domains are Pro, from €4.99/mo.