Baseleg documentation
System docs, domain map, architecture decisions, standards, and UX system. Built from the
repo's /docs directory and published separately from the product app.
Sections
- Product — what Baseleg is, capabilities, v1 scope, and the roadmap
- Domain — bounded contexts, ubiquitous language, DDD model
- Architecture — layering, packages, database, testing, decisions
- UX — design tokens, components, patterns, and diagrams
Recommended reading order
- Product overview — understand what Baseleg is and who it's for.
- Domain overview — understand the DDD approach and bounded contexts.
- Context map + Ubiquitous language — learn the domain model.
- Architecture overview — understand the modular monolith and layering.
- Package boundaries — especially "no direct page → DB shortcuts".
- Definition of done — understand what "complete" means.
- UX system — review design tokens, components, patterns, and diagrams.
- ADRs — understand the rationale behind key decisions.
Notes
- Data owner expands
db/schema/*, migrations, and infrastructure wiring over time. - If you change architecture boundaries or introduce major new tooling, add an ADR.
- Domain terms in code must match the ubiquitous language.