Document Tools¶
For that profile — non-profit, mixed technical + management audience, open source, Markdown source, needs graphics and polish — here's how I'd narrow it down.
Top recommendation: MkDocs with Material theme¶
This is the strongest fit and it's not particularly close. Reasons:
It's fully open source (MIT license for MkDocs core, MIT for Material theme — though Material has a "Insiders" sponsored tier with extra features that you don't need). You write pure Markdown, it produces a polished, fast, searchable static site. Hosting is free on GitHub Pages, GitLab Pages, Netlify, or Cloudflare Pages, which matters for a non-profit budget.
What you get out of the box: full-text client-side search, dark/light mode, responsive navigation with sections and tabs, code syntax highlighting, admonitions (callout boxes for "Note", "Warning", "Tip"), tabbed content blocks, footnotes, math via MathJax/KaTeX, and native Mermaid diagram rendering. So your management-facing org charts, process flows, funding pipelines, and theory-of-change diagrams all render from text in your Markdown files.
For an incubator specifically, the structure tends to map cleanly onto Material's navigation: a top-level tab for "Program" (cohort guidelines, application process), one for "Operations" (governance, finance, policies), one for "Resources" (templates, playbooks for founders), one for "Reports" (annual reports, impact metrics). Each tab is just a folder of .md files.
A realistic stack¶
Source: a Git repository (GitHub or GitLab — both have free non-profit tiers) with your .md files and a mkdocs.yml config.
Diagrams: Mermaid for flowcharts, sequence diagrams, Gantt charts, org charts — all written as text inside fenced code blocks, version-controlled with the prose. For richer diagrams, draw.io / diagrams.net (open source, free) exports SVG that drops into Markdown.
Images and graphics: store in the repo under docs/assets/, reference with standard Markdown.
Build and deploy: GitHub Actions runs mkdocs build on every push and deploys to GitHub Pages. Free, automatic, version-controlled.
PDF export when a board member or funder wants a printable document: the mkdocs-with-pdf or mkdocs-print-site-plugin plugins generate clean PDFs from the same source. So one Markdown corpus produces both the website and any PDF deliverables.
Why not the alternatives, briefly¶
Docusaurus is excellent but heavier — React-based, more developer-oriented, more overhead for non-technical contributors who just want to edit a Markdown file in the GitHub web UI. Worth it if you need versioned docs (v1.0, v2.0 of a program) or a tightly integrated blog. Probably overkill for an incubator.
GitBook has a free open-source tier but the polished collaborative features are paid, and the open-source self-hosted version (the original gitbook-cli) is deprecated. Not a great long-term bet.
Wiki.js and BookStack are open source and good, but they're database-backed CMS systems, not Markdown-source-of-truth systems. You lose the "edit a file in Git, push, site updates" flow, which is the cleanest workflow for a small team.
Quarto is genuinely impressive (one source → website, PDF, slides, Word doc) and fully open source, but it's optimized for data and scientific publishing. For a business/program documentation use case, Material gives you a more polished result with less configuration.
What management-facing content looks like in this setup¶
A few patterns that work well for an incubator:
- Program handbook as a multi-page section with admonitions for key policies and Mermaid flowcharts for the application-to-graduation pipeline.
- Founder resource library as a tabbed section — "Legal templates," "Fundraising," "Hiring" — each linking to PDFs or external resources.
- Impact dashboard as a page that embeds charts (either static SVGs exported from your data tools, or live charts via the
mkdocs-charts-pluginwhich renders Vega-Lite from data files). - Governance docs (bylaws, board minutes, conflict-of-interest policies) as plain Markdown with PDF export available for formal distribution.
- Public site vs. internal site: you can run two MkDocs instances from one repo — a public one stripped of internal pages, and a private one (gated by GitHub auth or basic auth on Cloudflare) with the full set.
Reasonable next step¶
If you want, I can put together a starter mkdocs.yml config with the navigation structure I described, the right Material theme settings, and the plugin list for diagrams + PDF export — basically a working skeleton you'd clone and start filling in.
Open-source alternatives to Obsidian¶
Obsidian itself is free but not open source (proprietary, with an open plugin ecosystem). The truly open-source alternatives that match its core feature set:
Closest analogs to Obsidian¶
Logseq is the most popular open-source alternative. AGPL-licensed, local-first, stores everything as Markdown (or Org-mode) files in a folder you control. The interaction model is outliner-based — every line is a bullet/block you can reference individually — which is a stylistic difference from Obsidian's page-based model. It has bidirectional links, backlinks panel, graph view, daily notes, queries, and a plugin marketplace. Strong if you like the Roam/outliner style of thinking.
SilverBullet is newer, MIT-licensed, and self-hostable as a web app (runs in a browser, syncs files to a server you control). Markdown-native, supports [[wiki links]], has a query language for live-rendering content from across your notes, and a plugin system in Lua. The web-app deployment model is interesting if you want a vault accessible from any device without installing a desktop app on each.
AppFlowy is GPL/AGPL-licensed and pitched as a Notion alternative more than an Obsidian one — page-based, database views, kanban — but it does support Markdown and linked pages. Worth knowing about if your team wants Notion-style structure with open-source guarantees.
Lighter-weight Markdown editors with some linking¶
Joplin (MIT/AGPL) is mature, has Markdown editing, attachments, end-to-end encrypted sync, and tags. It supports note links but doesn't have the full Obsidian-style backlinks/graph. Best if you primarily want a notes app, not a knowledge graph.
Zettlr (GPL) is a Markdown editor aimed at academics — strong on citations, footnotes, Pandoc export. Supports [[wiki links]] and a basic backlinks pane. Less of a "vault" feel, more of a writing-focused editor.
MarkText and Ghostwriter are pure Markdown editors — clean writing experience, but no linking/vault features.
VS Code as a vault¶
Worth flagging: if your incubator team is already using VS Code, the Foam extension (MIT) turns a folder of Markdown files into an Obsidian-like vault — [[wiki links]], backlinks, graph view, daily notes. The advantage is that the same folder also works as your MkDocs source, so writing notes and writing documentation become the same activity on the same files. Markdown Memo and Dendron are similar VS Code-based options (Dendron is more structured, hierarchical).
This is genuinely worth considering for BNI: one folder of .md files that is simultaneously (a) the team's linked notes vault when opened in VS Code with Foam, and (b) the published documentation site when built with MkDocs. No content duplication, no sync, no separate tools to learn for technical contributors.
Practical recommendation for BNI¶
| Scenario | Recommendation |
|---|---|
| Mixed technical/non-technical team, one consistent tool | Logseq for everyone + MkDocs reading from the same folder |
| Contributors mostly comfortable in VS Code | Foam in VS Code — same files, same folder, same Git repo as the MkDocs site |
| Web-based vault accessible from any browser without installs | SilverBullet, self-hosted on a small VPS or container |