brand
mdbase.dev serves two connected audiences. People evaluating mdbase need to understand why ordinary Markdown files can support several independent applications without surrendering control of their data. Application and tool developers need exact, runnable guidance for building on mdbase Connect, implementing the specification, and verifying conformance.
The site introduces mdbase, mdbase Connect, the specification, runtimes, SDKs, and conforming implementations. It should explain the ownership model through one small collection, then help a developer reach a working Connect integration without reconstructing the architecture from source repositories.
The normative specification remains independently versioned and is imported from a pinned mdbase-spec build. Conformance and implementation claims remain machine-readable and must not be inflated into marketing language.
Precise, grounded, and quietly optimistic. The site should feel like a durable technical standard with a useful product built around it. It is direct about trust boundaries, release status, and what remains on the user's computer.
Avoid generic SaaS launch-page gloss, security theatre, terminal cosplay, oversized decorative metrics, mascot-led developer marketing, vague claims about data ownership, and repetitive card grids. Do not imply that Connect is the mdbase specification, that TaskNotes owns the ecosystem, or that hosted collections are zero-knowledge.
- Show a real collection and its routes before making abstract claims.
- Explain Connect in terms of user choices and exact application permissions.
- Make the SDK quickstart runnable and keep advanced topics one link away.
- Separate passive collection semantics, runtime contracts, workflow execution, and Connect hosting.
- Publish exact profile claims with artifact versions and evidence dates.
- Keep normative content sourced from mdbase-spec.
Target WCAG 2.2 AA for contrast, keyboard navigation, focus visibility, semantic structure, and reduced motion. Long-form SDK and specification reading must remain comfortable on narrow screens and under light or dark system themes.