How I Structure a New Front-End Codebase

When I open a new codebase, I want to find the page, its data and its styles without following an elaborate filing system. That's what I aim for when I start one too.

I keep related files close together and wait before creating shared abstractions. A small amount of duplication is easier to untangle than a generic module with ten callers and slightly different expectations. The structure should become more specific as we learn what the application actually needs.