A portfolio site does not need six months and a developer. It needs a clear decision about what the site is for, a shortlist of work you still believe in, and two days without too many interruptions. The plan below is deliberately tight: Friday evening for thinking, Saturday for building, Sunday for editing, testing and going live. It assumes you have a laptop, a domain name, and enough finished work to fill eight to twelve project pages — not a complete archive of everything you have ever made.
Nothing here requires you to learn to code, and nothing here requires you to spend a fortune. What it does require is that you stop browsing templates at midnight and start making decisions.
Start on Friday Night With One Sentence
Write a single sentence describing the site. I make hand-thrown tableware for restaurants and home cooks. I photograph editorial portraits for small magazines and arts organisations. I design identity systems for independent food brands. Keep that sentence visible while you work. It decides your navigation, your image sizes, the tone of your captions and which pieces you leave out. If you cannot write it yet, that is useful information — it means the site is not ready to be designed.
Then decide who it is for. An art director scanning for a specific skill, a gallery, a commissioning editor, a client sent your way by a recommendation, or an admissions tutor. Write down the one thing you want that person to do: email you, book a call, download a PDF, follow a link to a shop. One action, not four.
Spend the rest of the evening collecting three sites you admire — not to copy, but to study. A grid that lets images breathe. A caption style you can read on a phone. A sense of pace. Write down the specific thing that works, because "it looks nice" will not help you build anything.
Pick a Platform in Twenty Minutes
Most hosted builders will handle a creative portfolio perfectly well. Squarespace, Format, Cargo, Adobe Portfolio and Webflow are all used by working makers. WordPress is flexible if you are happy to maintain it, and if you already write code, a simple static site is a fine choice. The differences between them matter far less than the work you put inside them. Judge each one against a short list of practical questions:
- How are images displayed, and can you control cropping, sizing and the gaps between them?
- How long does it take to add a new project? If updating the site costs you an evening, you will stop doing it.
- Does the template let your work lead, rather than the design?
- Is a custom domain included, or cheap to connect?
- What happens if you leave — can you export your content?
- Are the ongoing costs something you can sustain for a few years?
Choose one and move on. Pay for the plan that removes the platform branding and allows your own domain. Building on a free subdomain reads as unfinished, because it is.
Choose the Work Before You Design Anything
Eight to twelve pieces is plenty. Group them into two or three series or themes, and lead with the work you want more of. If you are applying for a particular kind of job, put the closest match first. Be ruthless with the rest. Remove anything you cannot talk about for two minutes, anything that needs a paragraph of context before it makes sense, and anything technically weak — soft focus, bad light, a scan that has lost its detail.
Then prepare the files once, properly:
- Export final images at a consistent long edge. Around 1600 to 2000 pixels is more than enough for screens.
- Convert to sRGB so colours behave predictably across devices.
- Name files sensibly: project-title-01.jpg, not IMG_4471-final-final.jpg.
- Keep web exports in their own folder, separate from your master files.
- Look at each image at full size on a phone. That is where most people will see it.
Saturday: Build the Skeleton
Keep the structure plain: Home, Work, About, Contact, plus one page per project. That is all. Four navigation items is the maximum most visitors will read. Your home page should show three to six strong images and offer a clear route into the work; it does not need a manifesto.
Build one project page completely — title, images, captions, credits, a link to the next project — then duplicate it for everything else. Consistency is what makes a portfolio look professional, and it is also what saves you time. Same type sizes, same margins, same caption position on every page. Resist customising each project differently; the work should vary, not the furniture around it.
Let images sit on a quiet background — white, off-white or near-black — and give them room. Avoid autoplay video with sound, carousels that move before anyone can read them, and any animation that delays the work by half a second.
Captions Do More Work Than Layout
A good caption answers three questions: what is it, what did you do, and what is one specific detail worth knowing? Materials, dimensions, client, year, process. For example: Harbour Wall, 2024. Stoneware with oxide wash, 32cm. One of a series testing how salt glazes behave on thrown forms with a coarse clay body.
That is more persuasive than "personal project" or "just experimenting". Cut those phrases wherever they appear. Keep titles formatted the same way throughout the site, and write alt text for every image — a short description of what is in it. It helps anyone using a screen reader, and it keeps the page readable if an image fails to load.
Your About page should run to 150 or 250 words in plain speech. What you make, how you make it, where you are, what you are available for. Put your email address there as text, not only inside a form. If you collect visitor data through the site, keep it minimal and make sure you understand your obligations; if you are unsure, seek proper advice rather than guessing.
Sunday Morning: Polish, Test, Fix
Before you launch, work through this list properly rather than skimming it:
- Read every page on a phone, then again on a laptop.
- Click every link, including the email address and any social profiles.
- Send a message through your contact form, then reply to it.
- Compress any image that is slowing a page down.
- Check spelling on titles and captions as carefully as on body text.
- Add a favicon, and check the browser tab title on each page.
- Look at your 404 page and make sure it points somewhere useful.
- Ask one person to spend ten minutes on the site. They will spot the typo you have read past six times.
Launch It Before You Lose Your Nerve
Point the domain, remove the holding page, and send one message to the people who might actually use the site. Then leave it alone. Give yourself a two-week rule: no design changes unless something is broken. After that, add work as projects finish, update the About page when something changes, and keep a folder of new images ready so the next update takes an hour instead of a weekend.
A live site with eight good pieces will do more for you than a perfect one still sitting in a folder. Finish it, publish it, and let it work.
Photo: freephotocc / Pixabay