Folder Structure
Five top-level concepts inside src/: app, components, lib, providers, helpers.
Folder Structure
An org problem with a designed answer, an honest timeline, and PRs compounding in the meantime.
- 01
Org problem, not code
- Folders nobody knows exist (hi, animations/)
- No shared rule for where things go
- No shared definition of what owns what
- 02
Designed, not improvised
- Full analysis in Prague, refined on SFW
- Every folder has a one-line job
- Docs live alongside the code
- 03
Incremental, not flashy
- Grouping (Apple Pay), pages/ as orchestrators
- Aliases: @/, @config/, @test/
- Naming conventions, dead-code cleanup
- 04
Every small PR compounds
- Design system stays the priority
- No big-bang migration required
- The codebase gets clearer week by week
Same content, organized luggage — a finite, named structure instead of a pile to dig through.