|
| 1 | +# Product |
| 2 | + |
| 3 | +## Register |
| 4 | + |
| 5 | +brand |
| 6 | + |
| 7 | +## Users |
| 8 | + |
| 9 | +mdbase.dev serves two connected audiences. People evaluating mdbase need to |
| 10 | +understand why ordinary Markdown files can support several independent |
| 11 | +applications without surrendering control of their data. Application and tool |
| 12 | +developers need exact, runnable guidance for building on mdbase Connect, |
| 13 | +implementing the specification, and verifying conformance. |
| 14 | + |
| 15 | +## Product Purpose |
| 16 | + |
| 17 | +The site is the ecosystem gateway for mdbase, mdbase Connect, the specification, |
| 18 | +runtimes, SDKs, and conforming implementations. It should make the ownership |
| 19 | +model clear in one screen, then help a developer reach a working Connect |
| 20 | +integration without reconstructing the architecture from source repositories. |
| 21 | + |
| 22 | +The normative specification remains independently versioned and is imported |
| 23 | +from a pinned mdbase-spec build. Conformance and implementation claims remain |
| 24 | +machine-readable and must not be inflated into marketing language. |
| 25 | + |
| 26 | +## Brand Personality |
| 27 | + |
| 28 | +Precise, grounded, and quietly optimistic. The site should feel like a durable |
| 29 | +technical standard with a useful product built around it. It is direct about |
| 30 | +trust boundaries, release status, and what remains on the user's computer. |
| 31 | + |
| 32 | +## Anti-references |
| 33 | + |
| 34 | +Avoid generic SaaS launch-page gloss, security theatre, terminal cosplay, |
| 35 | +oversized decorative metrics, mascot-led developer marketing, vague claims |
| 36 | +about data ownership, and repetitive card grids. Do not imply that Connect is |
| 37 | +the mdbase specification, that TaskNotes owns the ecosystem, or that hosted |
| 38 | +collections are zero-knowledge. |
| 39 | + |
| 40 | +## Design Principles |
| 41 | + |
| 42 | +- Show a real collection and its routes before making abstract claims. |
| 43 | +- Explain Connect in terms of user choices and exact application permissions. |
| 44 | +- Make the SDK quickstart runnable and keep advanced topics one link away. |
| 45 | +- Separate passive collection semantics, runtime contracts, workflow execution, |
| 46 | + and Connect hosting. |
| 47 | +- Publish exact profile claims with artifact versions and evidence dates. |
| 48 | +- Keep normative content sourced from mdbase-spec. |
| 49 | + |
| 50 | +## Accessibility & Inclusion |
| 51 | + |
| 52 | +Target WCAG 2.2 AA for contrast, keyboard navigation, focus visibility, |
| 53 | +semantic structure, and reduced motion. Long-form SDK and specification reading |
| 54 | +must remain comfortable on narrow screens and under light or dark system themes. |
| 55 | + |
0 commit comments