A beginner’s portfolio: what to show before your first commercial project

You do not need a paid commission to show how you think and work. A weak portfolio usually lacks explanations rather than client logos: the reader cannot tell which problem the author addressed or what they contributed.

Choose a finished piece of work

A small service, a clearly labelled fictional learning project or a contribution to an open project can become a first case study. Do not present a concept as a real company commission. A completed modest project provides more to discuss than an ambitious promise.

Describe the intended user and their task. Include a working link, key screens or a short recording. Make the outcome easy to find.

Explain your decisions

Describe why you chose the structure, what happens with missing data and errors, and which features you deliberately excluded. For a team project, identify your own contribution.

Explore one decision properly: the initial problem, possible approaches and the compromise you selected. This says more than a list of technologies disconnected from the task.

Make the project reviewable

For developers, a clear README, setup instructions and limitations help. GitHub supports a profile README that can introduce you and direct visitors to your work. GitHub profile documentation.

For designers, a coherent case study and accessible prototype serve a similar purpose. Test links without signing in. Do not publish access keys or someone else’s confidential material.

Report only real outcomes

If a project has never reached an actual audience, do not claim increased sales. Describe what you did verify: a keyboard journey works, a form handles errors or another person followed the setup instructions successfully.

Our form-review guide can serve as a practice task. Document the original problems and your changes to create a concrete account of your work, rather than a gallery of screens.