How We Structure Our Next.js Projects (Simple and Boring)

Every time I see a "project structure" article it is always some over-engineered setup with 15 folders and custom abstractions. That works for big teams but for a small studio like ours, we keep it simple. Here is how we organize our Next.js projects at Impeccify . Nothing fancy, just practical. The folder structure src/ app/ - Pages and routes components/ - Reusable UI components constants/ - Static data and configuration lib/ - Utility functions hooks/ - Custom React hooks styles/ - Global CSS (minimal with Tailwind) public/ - Static files That is it. No domain folders, no feature folders, no barrel files. Just the basics. Why this works for us The app folder is flat Every page gets its own folder inside app. We do not nest routes unless the URL structure actually requires it. src/app/ page.jsx - Homepage tools/page.jsx - Tools hub blog/page.jsx - Blog hub px-to-rem-converter/ page.jsx layout.js chipotle-nutrition-calculator/ page.jsx layout.js Each tool or page has its own folder wi