At project start, no consistent convention existed for where code, configuration, documentation, and examples should live. Without an early decision, structure tends to organically grow inconsistent as the project scales across multiple packages (library, docs, examples).
What was done
Defined a pnpm-based monorepo layout separating the library package (packages/luna-charts), documentation (docs/), and usage examples (examples/)
Decided that Storybook lives inside the library package itself rather than as a separate app, keeping component source and its interactive documentation co-located
Documented the structure, including the reasoning behind each top-level directory, as an Architecture Decision Record
Outcome
Repository structure and rationale documented in ADR-0001 (Repository Structure)
Matches the structure described in the Getting Started guide (project-structure.mdx)
## Context
At project start, no consistent convention existed for where code, configuration, documentation, and examples should live. Without an early decision, structure tends to organically grow inconsistent as the project scales across multiple packages (library, docs, examples).
## What was done
- Defined a pnpm-based monorepo layout separating the library package (`packages/luna-charts`), documentation (`docs/`), and usage examples (`examples/`)
- Decided that Storybook lives inside the library package itself rather than as a separate app, keeping component source and its interactive documentation co-located
- Documented the structure, including the reasoning behind each top-level directory, as an Architecture Decision Record
## Outcome
- Repository structure and rationale documented in **ADR-0001 (Repository Structure)**
- Matches the structure described in the Getting Started guide (`project-structure.mdx`)
## Related
- `docs/.../architecture/adr/000100-repository-structure.mdx`
Ninosaurier
added this to the v0.1.0 - Phase 1: Groundwork milestone 2026-07-22 14:02:48 +00:00
Ninosaurier
self-assigned this 2026-07-22 14:02:48 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
At project start, no consistent convention existed for where code, configuration, documentation, and examples should live. Without an early decision, structure tends to organically grow inconsistent as the project scales across multiple packages (library, docs, examples).
What was done
packages/luna-charts), documentation (docs/), and usage examples (examples/)Outcome
project-structure.mdx)Related
docs/.../architecture/adr/000100-repository-structure.mdx