Next.js
Judges and recruiters will not inspect every file deeply. Your repo should make the App Router evidence easy to find in under two minutes.
Your submission must show file-based routes, layouts, Server and Client Components, one server-side data fetch, one route handler, and a deployed URL that works on a phone.
0 of 7 lessons done · proved by a submitted project with a public repository
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 6 done
Put a short proof section near the top of README.md. Do not make judges hunt through your project.
Keep it factual. Link to the live app and list the exact files that prove each requirement.
Project: Campus Mess Feedback
Live URL: https://your-deployed-app.example
Built with: Next.js App Router
App Router proof:
- File-based routes: app/page.tsx, app/feedback/page.tsx, app/admin/page.tsx
- Shared layout: app/layout.tsx
- Server Component: app/feedback/page.tsx
- Client Component: app/components/RatingForm.tsx
- Server-side data fetch: app/admin/page.tsx fetches feedback before render
- Route handler: app/api/feedback/route.ts handles POST requests
How to run locally:
- Install dependencies
- Run the dev script
- Open the local URL printed in the terminal
Phone test:
- Tested the deployed URL on Android Chrome using mobile data
- Main pages load
- Feedback form submits
- Admin page renders dataA weak repo only has a live link and a one-line README. That makes your work look unfinished even if the app runs.
Another common mistake is submitting a localhost screenshot. Judges need a public deployed URL. Test it on a real phone because that is how many hackathon judges will open it.
You can ask ChatGPT, Gemini, or Claude to review your README before submission. Paste your file tree and ask it to check whether each App Router requirement is visible.
Do not blindly accept its answer. Verify the file names yourself. AI may claim a route handler exists when your file is actually named handler.ts instead of route.ts.
Use a prompt like this after you finish the repo. It helps you catch missing proof before submission.
You are reviewing my Next.js App Router hackathon repo README.
Check if it clearly proves these requirements:
1. File-based routes
2. Layouts
3. Server Components
4. Client Components
5. At least one server-side data fetch
6. At least one route handler
7. Public deployed URL tested on a phone
Here is my README:
[paste README]
Here is my app folder tree:
[paste app folder tree]
Return only:
- Missing proof
- Confusing file names
- README edits I should makeDo each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
Answer the quick check to finish this lesson.