Choosing a project you will finish

The reason most portfolios are empty is not skill. It is scope. People choose a social network and abandon it in week three.

Pick something you can finish in two weeks of evenings. A booking page for a barber. A results page for a school. A catalogue for a shop that takes enquiries. A tool that solves one annoyance you personally have.

Solve a real problem for a real person, ideally someone you can ask questions. A project with a user teaches you things no tutorial does, starting with the discovery that what they asked for is not what they need.

Write down what it does in one sentence. If that sentence needs an "and", cut something.

Then write the smallest useful version. Not the first version of your ambition, but the smallest thing that works end to end. One page, one form, one saved record. You can always add. What you cannot do is finish something that keeps growing.

List what it does not do, explicitly, and keep that list. It is what stops you adding features in week two instead of shipping.

Avoid two traps. Do not spend the first three days choosing a technology stack; use what you know, because the point is finishing, not evaluating frameworks. And do not start with the design system. Build it working and ugly, then make it look right, because a beautiful half built thing is worth nothing and a plain working thing is a portfolio piece.