What is the issue you are encountering with the docs?
The base/web repository contains many pages, components, and shared utilities, but there isn’t a simple overview explaining how everything fits together. A quick high-level explanation would make it easier for new contributors to understand the project.
New contributors may need to explore many files before understanding where key logic lives or how different parts of the app connect. This can slow down onboarding and make small changes feel more complicated than they should be.
Describe the solution you'd like to see.
Add a short documentation section that explains the main folders, how pages and components are organized, and where common changes are typically made, using clear and simple language.
Additional context
The documentation should help readers quickly understand the overall structure of base/web and where to look when making changes.