01 / FILES
Markdown files are the library
Organize with folders, store content in Markdown, connect pages with links—open, transparent, and easy to use with other tools.
LOCAL · MARKDOWN · WIKILINK
01 / THE FOUNDATION
Not moving files into a vault.
DaoBox works directly with Markdown in your filesystem. Your knowledge doesn’t need to be imported into a closed database, or depend on one platform to exist.
A folder is the library. Markdown is the content. Links connect files, Git keeps full history, and AI can work with those files directly.
From day one to years later—when you migrate or switch tools—your knowledge is still ordinary files.
02 / WHAT MAKES IT DIFFERENT
Six pieces.
One complete workflow.
02 / BLOCK TAGS
One file, many perspectives
Tag paragraphs, heading regions, tables, and other blocks. Templates and publishing can select, hide, or transform content accordingly.
BLOCK · TAG · CONTEXT
03 / DAILY USE
Day to day: a private knowledge space
Browse, search, update, and organize. Edit when you need to—don’t reshape daily work just to publish.
READ · SEARCH · EDIT · ORGANIZE
04 / GIT
Fully compatible with system Git
Not a reinvented VCS. DaoBox uses standard Git—you can still manage the same files with system Git, the CLI, or other Git tools.
STANDARD GIT · FULL COMPATIBILITY
05 / TEMPLATES
Templates that automate the repetitive
Templates are Markdown too. System variables plus editor snippets help you spin up articles, logs, and project docs from fixed structures.
DATE · TIME · UUID · CLIPBOARD · SNIPPET
06 / PUBLISH
When you publish, generate a site
Generate a Blog, Book, Wiki, or custom static site from the same Markdown—no fixed site structure required, and no second copy of content.
STATIC SITE · BLOG · BOOK · CUSTOM
03 / ONE FILE, A LONG WAY
From one Markdown file
to a full website.
01Write it down
02Link it together
03Tag content
04Keep history with Git
05Produce with templates
06Generate the site
04 / PUBLISH WITHOUT REBUILDING
When you’re done writing, don’t move it again.
Library and site aren’t two content sets. DaoBox pulls what it needs from your Markdown and builds the site from templates.
You’re not forced into a fixed Blog, Docs, or Book layout. You define structure—so the same knowledge can become very different sites.
The real point isn’t “export HTML”—it’s that the same knowledge stays a library and can also become a real website.
Blog
Keep writing, publish posts, and build a personal content site.
Book
Organize long-form content by chapter until it becomes a book.
Knowledge Base
Turn private knowledge into a browsable site when you need to share it.
Your own structure
No fixed site shape—define pages and navigation with your own templates.
05 / USE CASES
Start today.
Grow it over time.
You already have lots of Markdown
No migration, conversion, or reshaping into a database. Open the folder you already have.
Building a long-term knowledge base
Keep reading notes, work docs, research, and long-term archives in a file space that can keep growing.
You work with AI often
Let AI work on your Markdown files directly—without moving knowledge into an AI-only database first.
One draft for you and for readers
Use block tags to control what gets processed or published in each context.
Want history without learning Git
Keep standard Git compatibility while tucking away day-to-day complexity.
Writing that eventually becomes a site
No copying into another CMS or blog. Your accumulated knowledge is already the site’s source.
06 / TEMPLATES
Hand the repetitive work
to templates.
Templates are still Markdown. On insert, system variables and editor placeholders start new docs from a fixed structure.
---
created_at: $(DATE)T$(TIME)$(TZ_OFFSET)
id: $(UUID)
---
# ${1:标题}
${2:正文}07 / FAQ
Before you start,
you might ask.
Is DaoBox a notes app or a static site generator?
Neither alone. Day to day it’s a local Markdown knowledge workspace; when you need to, the same content can become a static site.
Is my content stored in a DaoBox database?
Core knowledge stays as ordinary Markdown files on your filesystem. DaoBox adds reading, editing, linking, templates, and publishing around those files.
Do I need Git installed for versioning?
No. Versioning doesn’t require an external Git install—DaoBox handles day-to-day versioning itself. When you need to, system Git tools can still take over those files.
Can publishing only make a Blog?
No. Generation doesn’t require a fixed site structure—you can build Blog, Book, knowledge base, and other custom sites via templates and selective generation.
Why not just use Hugo, Jekyll, or Zola?
If you only need a CLI static site generator, those tools are already great. DaoBox focuses on the full path from daily knowledge work to publishing—files, reading, organizing, templates, Git, and site generation in one environment.
DAOBOX
Your knowledge should always belong to you.
Start with a folder. Write slowly, accumulate patiently—then let it travel farther when the content is ready.