A tour of your Next.js project
Know what every folder and file in your Next.js project is for, which ones you'll work in, which ones to leave alone, and how folders inside app/ become the pages of your site.
Why this matters
Open your file tree in Cursor and count the items at the top level. There are about fifteen, and some of them, like next-env.d.ts or eslint.config.mjs, have names that tell a beginner nothing at all.
In Lesson 3.2 you had a first quick look. Now you'll walk through all of it properly, because in Stage 2 your projects grow. Module 6 adds an environment file for settings. Module 7 adds code that talks to a database. Module 9 adds a protected admin area. Each time, Cursor will create new files and folders, and you need to know whether it put them in the right place.
There's also a simpler reason: confidence. When you know what every file does, the project stops feeling like a machine you might break by touching it. It becomes a workshop where you know where every tool hangs.
In the full lesson
- The idea in plain English
- Do it
- Check it worked
- Quick check
- What you can do now
The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.