How to build a portfolio as a student with no clients

A portfolio piece is any project where you built something that works and can explain what you did. The client does not matter. The work does.

Personal projects. A tool you built for yourself: a budget tracker, a GPA calculator, a study timer. Real projects solve real problems, even if the user is just you.

Class projects. If your course included a group project or a final-year assignment that produced working software, it belongs in your portfolio. Add it to GitHub, write a description, and present it well.

Club or community work. Did you build a poster for a club? Design a landing page for an event? Create a registration form for a hackathon? These are portfolio pieces with real context.

Open-source contributions. Even a small contribution (fixing a bug, improving documentation) to an existing open-source project counts. It shows you can work on code you did not write.

Redesigns and clones (with a twist). Redesigning an existing website or building a clone of a familiar product is fine if you add something original. A todo app is a tutorial clone. A todo app customised for campus study groups, with shared lists and deadline reminders, is a project.

The presentation matters as much as the code. A strong portfolio piece has:

A title and one-line description. "StudyBuddy: a study plan generator for Kenyan university students." Clear, specific, tells the visitor what it does in one breath.

A screenshot or demo. Show what the project looks like. A screenshot of the interface, or better, a link to the live version. Visitors decide in seconds whether to look closer. A visual hook keeps them reading.

The problem it solves. One paragraph: "University students juggle multiple units with overlapping study needs. StudyBuddy takes your unit list and exam dates, then generates a weekly plan that prioritises based on difficulty and deadline." This context makes the technical work meaningful.

The tech stack. "Built with React, Node.js, and deployed on Vercel." Short. Employers scan for technologies they use.

Links. GitHub repo and live URL. If the project is not deployed, deploy it. A live link is worth ten times more than a repo nobody will clone and run.

Your portfolio needs a home. Options, from simplest to most impressive:

GitHub profile README. Free, takes thirty minutes. Create a repo named after your username, add a README.md with your bio, skills, and project links. This appears on your GitHub profile page. Good enough for first year.

A simple portfolio page. One HTML page with your name, bio, skills, and project cards. Deploy on Vercel or GitHub Pages. This is itself a portfolio piece: "I built my own portfolio site." Takes a weekend.

A multi-page portfolio site. Home, about, projects, contact. Use a framework you are learning (React, Next.js). This is the gold standard, but do not spend three months on it. A clean simple site with three projects is better than a beautiful empty site you keep redesigning.

The portfolio site is not the priority. The projects on it are. Build things first, then build the showcase. Do not build the frame before you have paintings to hang.

First year: Two or three small projects. A personal tool, a class project, and maybe a club contribution. Presented on a GitHub README or simple HTML page.

Second year: Add a more complex project using a framework. Replace your weakest first-year project. Your portfolio should always show your best work, not all your work.

Third year: Add freelance or internship work (with permission). Link to live sites you built for real clients or companies. Local business websites are excellent portfolio pieces.

Fourth year: Your portfolio should have four to six strong pieces, a mix of personal projects, client work, and your final-year project. By now, employers should be able to visit your portfolio and see a clear progression in skill and complexity.

Remove old projects that no longer represent your skill level. A portfolio is not a museum. It is a highlight reel.