Use this as the fastest route into architecture, development, data rooms, roadmap, and recent changes.
Start with architecture and data-room flows when you need the shape of the app.
Development, testing, and refactor guidance live in one place for fast onboarding.
Use the roadmap and changelog together to understand what changed and what is next.
Docs point back to the code paths that own the behavior, so you can jump from idea to file quickly.
If you are trying to change the app, use this order:
These are the files to reach for first when the docs mention a behavior:
| Area | Primary files |
|---|---|
| Routing and shared links | src/utils/url.ts, src/pages/LegacyRedirect.tsx |
| Deck processing | src/pages/ManageDeck.tsx, src/workflows/deckProcessing.ts, src/services/deckStorageService.ts |
| Analytics and signals | src/services/analyticsService.ts, src/services/interestSignalService.ts |
| Session and auth | src/contexts/AuthContext.tsx, src/services/authSession.ts, src/services/userService.ts |
| Navigation and layout | src/components/layout/Sidebar.tsx, src/components/layout/BottomNav.tsx, src/components/layout/DashboardLayout.tsx |
flowchart TD
A[Docs Home] --> B[Architecture]
A --> C[Development]
A --> D[Data Rooms]
A --> E[Roadmap]
C --> F[Source files]
B --> F
D --> F
E --> G[Changelog]Each page should answer a different question:
index.md: Where do I start?ARCHITECTURE.md: How does the system work?DEVELOPMENT.md: How do I safely change it?DATA_ROOMS.md: How do room flows and data models fit together?ROADMAP.md: What is next and what is blocked?CHANGELOG.md: What changed recently?The docs are strongest when they stay tied to the codebase. When you update a behavior, pair the doc with the owning file path and the related flow so the next engineer can move from context to implementation without hunting.