brand
mdbase.dev serves implementors, plugin authors, tool builders, and agent developers who need a shared behavior contract for Markdown files with YAML frontmatter. They arrive with technical intent: deciding whether the spec fits their project, finding the exact semantics for an implementation, or locating the conformance resources needed to build and test a library.
The site presents mdbase as a serious, portable specification for treating a folder of Markdown files as a typed, queryable data collection. Success means visitors quickly understand the core model, trust the spec's precision, and can move from concept to implementation resources without hunting.
Precise, literal, and implementation-facing. The tone should feel like specification documentation: clear about behavior, quiet enough for long reading sessions, and concrete enough that implementors can picture the files on disk.
Avoid generic SaaS launch-page gloss, rhetorical product slogans, terminal cosplay that hides information behind darkness, oversized decorative metrics, mascot-led developer marketing, and card grids that imply more product surface than exists. Do not make the spec feel like a blog theme or a venture-backed product landing page.
- Show the filesystem model before abstract claims.
- Treat the spec reader as the product's deepest proof point.
- Make conformance resources feel first-class, not buried in repository links.
- Favor durable reference-page craft over flashy developer branding.
- Keep every visual flourish tied to real mdbase artifacts: type files, records, queries, links, and tests.
- Prefer literal section headings over slogan-shaped framing.
Target WCAG AA for text contrast, focus visibility, semantic navigation, and keyboard access. Reduced motion must be respected. The site is long-form technical reading, so contrast and responsive navigation are product requirements, not polish.