A portfolio website is easier to build when the person making it does not have to guess what you do or which projects matter. Start with evidence and a clear next step for the visitor. You can choose the layout after that.
The checklist below works whether you are building the site yourself or giving the materials to a designer or website service.
Decide who the site is for
Write one sentence describing the visitor and the decision you want to help them make. For example: “A product team should be able to see what frontend work I can deliver and contact me about a role.”
Then choose one primary action: contact you, view your work or download your resume. You can offer other links, but the main action should be easy to recognize.
Avoid an introduction made only of job titles and adjectives. Say what you work on and show a relevant project nearby. Wix's portfolio content guide is a useful reference for the basic sections; the evidence inside them should come from your own work.
Prepare a short evidence pack for each project
For every selected project, provide:
- The problem or brief.
- Your role and what you personally contributed.
- A screenshot, demo or other sample you can share.
- The result, with a verifiable number where one exists.
- A short explanation of a decision or constraint.
A developer should not rely only on a repository link. Explain what the visitor is looking at, what you implemented and how to try it. If the demo is no longer available, say so and provide another accurate form of evidence.
Here is a fictional example of the structure, not a customer result: “I built the filtering interface for a three-person team's event directory. The screenshots show the mobile filter and empty state. My responsibility was the frontend; another team member built the API.” It explains contribution without inventing a business impact metric.
Separate your contribution from what you cannot share
For group work, name your role clearly. Do not imply that an entire team result was your individual output.
Remove private customer information, internal credentials and material you do not have permission to publish. If you need an anonymized case study, agree on what can be shown before giving the files to a builder. A service provider cannot infer permission from the fact that you uploaded a screenshot.
No reliable result metric? Describe the delivered work and the evidence you do have. A clear, honest account is more useful than an invented improvement percentage.
Organize assets so another person can use them
Use a folder per project. Give images descriptive filenames and explain what each shows. Supply original images where possible, short captions and appropriate text descriptions for meaningful visuals.
Put your public name, introduction, contact destination and social links in one document. Check every URL. Identify which email address may appear publicly; do not include private account access in this document.
Also state the required language and whether you already own a domain. Domain ownership does not mean you should send a password to the builder; arrange an appropriate connection method separately.
Once a real project is ready, use it to compare a portfolio template with custom design before commissioning the layout.
Copy this short website brief
Audience: Who will visit, and why?
Main action: What should they do next?
Introduction: What do you do, in two or three sentences?
Selected projects: For each, attach the problem, role, sample and supported result.
Pages and language: What is required for this version?
Contact: Which public destination should receive enquiries?
Assets and permissions: Which files may be published, and which may not?
Delivery: Do you need a live site, an editable account, source files or a combination?
Review: Who will give consolidated feedback and approve the result?
Review the finished site against the brief
Check the mobile layout, project links, image descriptions and primary contact action. If there is a form, send a test and confirm receipt. Verify your role, project facts and public contact information.
Finally, confirm that the promised files or account access have been handed over and that you know how future edits work. Keep the brief: it gives you and the maker a shared definition of a completed website.
For the final review, use the portfolio website handoff checklist to turn these requirements into specific acceptance checks.
To check what Agent.Space currently offers, visit its service marketplace. Confirm that a suitable service is listed and read its delivery scope before ordering.
