What makes a good projects page?

A gallery is not a projects page

The most common mistake I see is a wall of pretty screenshots with no words. Images prove you can make something look nice. They do not tell a visitor whether you solved a problem like theirs, which is the actual question in their head. A strong projects page is closer to a short story than a photo album.

Tell each project as a small story

For every piece of work worth showing, cover three things in a few sentences each:

• The problem. Who was the client, and what were they stuck with? "A Centurion salon taking every booking by WhatsApp and losing track of them" is instantly relatable to the next salon owner reading it.
• What you did. The solution in plain terms, and why you made the choices you did. Not a feature dump, just enough to show there was thinking behind it.
• The result. What changed afterwards. If you have honest numbers, use them. If you do not, describe the outcome plainly rather than inventing statistics, because made-up figures read as made up.

That structure works whether you have three examples or thirty. It is the explanation, not the volume, that builds confidence.

Show the work properly

Once the words are right, the visuals support them. A clean screenshot in a phone and desktop frame, one or two detail shots, and where it makes sense, a before and after. If the project is live and you are allowed to link it, link it, because a working site someone can click is the strongest proof there is.

Keep the images fast. A portfolio stuffed with huge uncompressed screenshots is slow, and a slow page about your web work sends exactly the wrong message.

Let visitors find work like theirs

If you serve different types of client, help people spot the relevant example quickly. A salon owner wants to see a salon, not scroll past ten unrelated jobs first. Simple category tags or grouping by industry does this without much effort. The goal is that within a few seconds a visitor lands on something that looks like their own situation.

Get permission and be honest

Always ask a client before you feature their business, and respect it if they say no. Never dress up a small job as something bigger than it was, and never borrow work you did not do. It is a small industry and it catches up with you. Honest, modest examples beat impressive ones you cannot stand behind.

If you genuinely have little to show yet, that is fine. A couple of real jobs explained well, or even a personal build you are proud of, does more than padding with weak filler. One good case study you can talk about beats five you cannot.

Point every project at a next step

A visitor who reaches the bottom of a case study and nods is no use to you if there is nowhere to go. End each project, and the page itself, with a clear route forward: a line like "want something similar for your business?" and a button through to the contact page. You have just done the hard work of building confidence, so do not make them hunt for how to act on it.

If you want to see the idea in practice, my own work is laid out this way, with the problem and the build spelled out for each one rather than left as a screenshot.

The quick test

Read your projects page as if you were a nervous customer comparing three developers. Can you tell what each person actually did? Can you find an example that matches your problem? Do you know how to take the next step? If the answer to any of those is no, the page has more work to do, and it is worth doing, because for a lot of visitors this is the page that decides whether they enquire at all.