Skip to content
Cyberbaser
🧠 Research & Foundations phase — building the KB from the ground up. See the roadmap →
CONSUMED BY🧑‍💻practitioner🎓student🔍searcher🤝colleaguereadsWEB WIKIcyberbase.wiki · search · backlinks · graph view · mobilerendered byTRANSLATION LAYERwikilinks · callouts · embeds · math · mermaid · backlinksremark + rehype plugins — guarantees round-trip fidelityreads / writes backcybersader/cyberbaseGitHub · markdown files · git history · single source of truthyour vault — you own it, you can leave with itAUTHORED FROMObsidian (local)power usersfull Obsidian fidelitygit push / PRWeb CMScasual contributorsDecap · form editorOpen Authoring PRsInline editreaders → authorsclick ‘edit’ in-pageWYSIWYGGitHub directdevelopersraw markdownPR workflowAPI / scriptautomation · teamsbots · pipelinescollaborative sync

The stack: readers consume the web wiki, which is rendered by the translation layer from the GitHub vault. Contribution flows upward from five surfaces — each serving a different perspective, from solo power users to in-page readers to team-wide automation. Inline editing closes the loop: any reader becomes an author without leaving the page.

Jump in

Section titled “Jump in”
01 · ProblemWhy existing Obsidian→web tools fall shortPublishing works. Contribution doesn’t. The gap cyberbaser fills.02 · EcosystemThe landscape around the problemObsidian Publish, Quartz, Digital Garden, Decap, and the gap none of them fill.22 · Hard problemThe translation layerObsidian syntax → web HTML without losing round-trip fidelity. This is where the project lives or dies.12 · PrinciplesThe rules that constrain every decisionGitHub is truth. Obsidian semantics round-trip. Contributors don’t need git. Research before code.20 · RoadmapPhased plan — Research firstPhase R is the only active phase until the first-principles work is real.04 · Prior artWhat others tried and learnedObsidian Publish, Quartz, Digital Garden, Notion-as-wiki, awesome lists — the data points.