DaoBox is a local Markdown file knowledge base.
Your notes and materials live in a folder on your own computer.
Here you can write, organize, search, link, and read your knowledge. Markdown is the main format, but you can keep images, PDFs, HTML, audio, video, and other files alongside it.
The most important part:
Your knowledge is your files.
Nothing is locked inside an app database. You can back up, copy, and move your content anytime—and open it with other tools.
DaoBox exists so those files—already yours—are easier to grow, organize, and use over the long term.
1. One folder is a knowledge base
You don’t need to create a special database first.
Open a folder, and it can become your knowledge base.
Organize directories however you like:
My Knowledge Base/
├── Reading/
├── Work/
├── Coding/
├── Ideas/
├── Projects/
└── ...
Inside, they’re just ordinary files.
Markdown notes, images, PDFs, HTML pages, and other materials can sit in whatever structure makes sense to you.
From day one, your knowledge base is open:
- You can see it in Finder / File Explorer;
- You can copy the whole folder to back it up;
- You can keep using it after switching machines;
- You can open it in other Markdown editors;
- You can put it under Git;
- You don’t need DaoBox to read your own content.
So DaoBox sits on top of your files and gives you a full way to work with knowledge.
The files are yours. The knowledge is yours.
2. Why local files
Many note apps store everything in their own database.
That’s convenient—but it also means:
Your knowledge starts depending on that software.
If the app is abandoned, the format changes, or you want to switch tools, you may face a migration problem.
DaoBox takes another path:
Keep the important things simple.
Markdown is open, lightweight, and readable for the long haul.
Your knowledge doesn’t need to live inside DaoBox.
DaoBox can go away. Your files will still be there.
That’s one of its core design principles:
Apps can change. Your files shouldn’t be held hostage.
3. More than a Markdown editor
If all you need is editing Markdown, a regular editor is enough.
DaoBox focuses on something else:
Once you have lots of Markdown files, how do you actually use them?
So it offers a full set of knowledge-base capabilities:
- Folder organization;
- Markdown reading and editing;
- Full-text search;
- Outline;
- Tags;
- Bidirectional links;
- Backlinks;
- Local assets;
- File preview;
- Git version control.
You can treat a note as a standalone document—or connect many notes into a network of your own.
As files pile up, a knowledge base can grow with them.
4. Reading and editing don’t have to be the same mode
DaoBox doesn’t expect you to stay in “editor mode” all the time.
Most of the time, you’re actually:
- Reading;
- Searching;
- Browsing;
- Organizing;
- Thinking.
You only edit when something needs changing.
So Markdown in DaoBox leans toward:
Read well by default; edit when you need to.
When you do edit, the goal is to avoid constant layout jumps as Markdown syntax appears, hides, or shifts.
What you see and what you get should stay clear and stable.
5. One piece of writing, for yourself and for others
This is one of DaoBox’s most important workflows.
When you write an article, you often produce two kinds of content at once:
Ready to share:
Polished ideas, body text, sources, and conclusions.
Still just for you:
Unsettled judgments, honest thoughts, notes, fragmented thinking.
The usual options:
- Maintain two files;
- Delete private bits before publishing;
- Or lean on plugins.
DaoBox aims to make this simpler.
In the same Markdown file, you can mark some content as private.
That content:
- Still lives in your knowledge base;
- Remains visible to you;
- Can serve as your own context;
- Is automatically hidden from readers when you publish.
You don’t have to scrub a draft clean just to make it public.
One document can serve both you and your readers.
6. Knowledge doesn’t need a purpose on day one
Often you don’t know whether today’s note will become an article six months from now.
So DaoBox doesn’t ask you to decide up front.
You can simply:
Write it down.
Then:
Organize over time.
Then:
Build connections.
And one day, when it feels mature enough, decide:
Whether to share it.
That’s a big difference from traditional “blogging tools.”
Publishing isn’t the starting point of writing.
Publishing is just one way to output knowledge after you’ve built it up.
7. The same files can become a website
When you do want to share, you don’t need a second content system.
DaoBox can preview and publish from the knowledge base you already have.
In other words:
Local files
↓
Knowledge base
↓
Organize / link / refine
↓
Site preview
↓
Publish
There’s no need to duplicate a second copy of the content.
The same Markdown files can be rendered with different templates into different forms—for example:
- A blog;
- A book-style knowledge base;
- A documentation site;
- Other site shapes that fit your content.
You don’t have to learn a template system, the command line, or a complex deploy pipeline first.
Focus on content while writing; decide how it looks when you publish.
8. Files can be read as they are
A DaoBox knowledge base doesn’t require everything to become Markdown.
A real library often includes many kinds of materials.
For example:
Knowledge Base/
├── Markdown notes
├── Images
├── PDFs
├── HTML
├── Audio
└── Video
DaoBox opens each type in a suitable way:
- Markdown → read and edit;
- HTML → view as a page;
- Images → image preview;
- Audio → audio playback;
- Video → video playback;
- PDF → PDF viewer;
- Other files → the appropriate viewer or editor.
You don’t need to convert everything into one format just to use a knowledge base.
Whatever the file is, open it in a way that fits.
9. Git, so knowledge can go back in time
A knowledge base isn’t static.
What you change today might feel wrong tomorrow; a version from months ago might be worth recovering.
DaoBox brings Git’s versioning into the knowledge base so common operations stay inside the app:
- Review changes;
- Commit versions;
- Browse history;
- Restore earlier content;
- Sync with a remote repository;
- Clone a knowledge base from a remote.
You don’t need a heavy command-line workflow just to manage your knowledge.
Underneath, it’s still mature Git.
So:
Knowledge can keep changing—without easily losing where it came from.
10. Who DaoBox is for
DaoBox fits especially well when:
You’re building knowledge over time
You have many Markdown notes and want them to stay as your own files, slowly becoming a coherent knowledge base.
You don’t want to be locked into a note app
You want free backup and migration—and the option to switch tools later—without years of work trapped in one product.
You often need to keep things for yourself first
When writing, researching, or organizing sources, you produce content that isn’t ready to share, and you want it to live naturally alongside the public draft.
You occasionally want to share
Most days you’re accumulating knowledge, not blogging daily—but when something matures, you want it to become a website without friction.
You want one tool from accumulation to output
You don’t want one tool for notes and another toolchain just to publish.
11. What DaoBox is not
DaoBox isn’t an all-in-one knowledge OS trying to replace every tool.
It also isn’t a closed ecosystem that forces you to change how you work.
It aims to keep one thing simple:
Your files remain your files.
On top of them, DaoBox adds better reading, editing, organizing, linking, versioning, and publishing.
You can use it only as a local knowledge base.
Or go further with publishing.
You shouldn’t have to reorganize your whole library just to use one feature.
12. Closing
Knowledge isn’t something you organize once and finish.
It usually starts with a file, a paragraph, an idea.
What you jot down today may become an article months later; an article may become part of a book; scattered notes may slowly connect into a system that’s truly yours.
DaoBox wants that path to feel natural:
Capture first. Organize over time. Share when you’re ready.
And from start to finish:
Your knowledge is your files.
For more concrete scenarios, see Use Cases; for the full capability list, see Features; for common questions, see FAQ.