Tagged: Design
Architecture and system design
Pages with this tag
08 · Linchpin + bottleneck audit
1From first principles: which problems in the architecture are load-bearing, which are incidental, and what are the solution paths for each?
Operational landscape
2Who does what work in the contributable wiki ecosystem — actors × components × resource intensity. The combined view that determines what to build, what to crowdsource, and what needs ongoing funding.
Architecture
3How cyberbaser's components fit together — vault, build pipeline, translation layer, CMS, hosting.
Contribution Workflows
4Three independent contribution paths — Web CMS, Obsidian+Git, Direct GitHub — with end-to-end flows and constraints.
Translation Layer
5The hardest problem in cyberbaser — converting Obsidian-flavored markdown to web HTML without losing round-trip fidelity. Tier 1 / 2 / 3 feature list.
Principles
6The design principles that constrain every decision in cyberbaser. Rules with reasons.
Trade-offs
7Design decisions and their accepted costs. Each entry is dated and references a principle.