Final project and portfolio
Lesson 26 of 26 in the course “Vibe coding”. Free, with animations and a quiz.
The whole route on one map
This is the course finale, and the figure shows the whole route of ten stops. First half. Idea: what you're making and for whom. Spec: a one-page plan. AI tool: a builder, an editor or an agent. GitHub: your code in the cloud with its full history. Hosting: the site goes online, and each branch gets its own preview link. Domain: your own name instead of a technical address. The other stops are on the next slide.
The second half of the route
Database and login: only if the site must remember user data. A one-page portfolio doesn't need them. Security: keys on the server, access rules for the database, request limits. Launch: checklist, analytics, a link where your people are. Feedback: listen to people and improve. The flag at the end means a live project, not a perfect one. Main rule: don't launch before you've passed the security check.
What your first project could be
Pick a small project that you or your friends actually need. Landing page: one page about you, your band or your stream. Telegram bot: reminds you about school deadlines. Calculator: splits a café bill across the whole group. Mini game: a quiz about your favorite show. Habit tracker: a streak of days without misses. Portfolio: a showcase of your work. Bottom line: one finished project beats three abandoned ones.
README: your project's shop window
A portfolio is a collection of your work that others can see. On GitHub its heart is the README, the front page of a repository. In it, say what problem the project solves, give a live link to the site, add a couple of screenshots, list what it's built with and how to run it. Pin your best repositories on your profile so they're seen first. And check that there are no keys in the public code.
How to talk about your project
In an application for an internship, a school program or a part-time job, show not just the link but the story. What problem you spotted. What you decided as the producer and what the AI did. Where the AI got it wrong and how you caught it. What you learned. Be honest that you worked with AI: setting clear tasks and checking results is a valuable skill on its own. Useful repositories to get started are below the lesson.
Check yourself
- What should a portfolio project's README include?
Correct answer: What problem it solves, a live link and screenshots. The README is read by people who won't dig into the code. They need the point, a link and pictures. Keys in a public repo will leak. - When does the route need a database and login?
Correct answer: When the site must remember user data. A static site, like a portfolio, is published without a database. A database and login are needed when you store people's data. - How should you talk about working with AI in a portfolio?
Correct answer: Honestly: what you decided, what AI did, where you caught bugs. An honest story shows your real work: producer decisions and checking. That's valued more than pretending you wrote everything.