Personal website examples, and what makes them work

Eight kinds of personal site, what belongs on each one, and the four mistakes that make the rest forgettable. Structure first, because that is the part a screenshot cannot teach you.

Start for free -> See the Figma plugin

What the good ones have in common.

Personal sites that work are not the ones with the best animation. They are the ones where a stranger can answer four questions in under a minute.

  • One sentence, above everything

    A visitor decides in about four seconds whether to keep reading. A sentence that says what you do and who for beats a clever headline that says neither.

  • One job per site

    Getting hired, getting read, getting commissioned. A site trying to do all three does none of them, and the navigation is where you can see it happening.

  • Proof over adjectives

    Three pieces of work with a line each about the problem beats a paragraph of adjectives. Nobody has ever been hired for the word "passionate".

  • A way to reach you that works

    An address people can copy, on the page rather than behind a form, and a link that is still alive. Half of abandoned personal sites fail this one.

Eight kinds of personal site.

Most personal sites are a version of one of these. Find yours, build that one properly, and ignore the other seven.

1. The one-page introduction

Your name, one sentence about what you do, a photograph if you want one, three links, and an email address. That is the whole site. It suits anyone whose work lives somewhere else already, on a platform, in a shop, in published writing.

What goes on it: the sentence, three to five links with a few words each explaining where they go, contact, and a date. Failure mode: padding it out. A one-page site with a fake About section reads worse than a one-page site that stops.

2. The portfolio with case studies

The standard for product, UX and brand designers. A home page with three to six pieces of work, and a page for each that explains the problem, what you did and what happened.

What goes on it: selected work rather than all of it, a real About page, and a contact route. Failure mode: case studies that are process shots with no problem statement. Open every one with a sentence describing what was wrong before you started.

3. The writing-led site

Where the essays are the work. The home page is a list of pieces with dates, and everything else is secondary.

What goes on it: a reverse-chronological index, generous body type, and one line saying who you are. Failure mode: building a magazine layout for eleven posts. This kind of site needs a real content system once the archive grows, so plan for a tool with a blog rather than designing forty pages by hand.

4. The CV site

One page, structured like a document, aimed at people who are deciding whether to interview you. It suits developers, researchers and anyone applying to institutions.

What goes on it: roles with dates, education, selected output, and a downloadable version. Failure mode: designing it like a poster. This is the one kind of personal site where being boring and scannable is the correct answer.

5. The links hub

A single page pointing at everything else you do. It suits people whose audience arrives from social platforms and needs somewhere to land.

What goes on it: six to ten links, each with a short line of context, on your own domain rather than a platform that could disappear. Failure mode: no context. A list of bare logos tells a visitor nothing about which one to click.

6. The freelance service page

Not a portfolio. A page that says what you sell, who it is for, what it costs or how pricing works, and how to start. It suits anyone taking on client work.

What goes on it: the service in plain words, two or three proofs, an honest note on availability, and a single clear next step. Failure mode: hiding the offer behind the word "collaborations". If someone has to guess what to ask you for, they will not ask.

7. The visual index

For photographers, illustrators and anyone whose work is the image. A dense grid, minimal text, and the images doing all the talking.

What goes on it: a tight edit, consistent crops, and images exported properly rather than dumped at full resolution. Failure mode: a slow page. A visual index that takes six seconds to load has already failed at the one thing it does.

8. The project archive

For people with a long tail of things they made. Everything listed, dated, and honest about which ones are dead.

What goes on it: a plain list with years, a line each, and a status. Failure mode: presenting abandoned projects as live. Marking something as finished or dormant makes the whole archive more credible, not less.

Four mistakes worth avoiding.

These turn up on sites that are otherwise nicely designed, which is what makes them worth naming explicitly.

  • A homepage that says nothing

    A full-screen photograph, your name, and a scroll arrow. It looks considered and it postpones the only question the visitor has, which is what you do.

  • Nine navigation items

    A personal site with nine links is usually four sites arguing. Cut to the pages that serve the one job, and let the rest be sections.

  • Case studies with no problem in them

    Process shots, mood boards and final screens, with no sentence about what was wrong before you started. The problem is the interesting part.

  • Nothing dated

    No dates anywhere means a visitor cannot tell whether the site is current. One line saying when it was last updated is worth more than another project.

  • How to actually get it built.

    The reason most personal sites never ship is that they are redesigned three times before anything goes live.

    1. Pick the site's one job.

    2. Write the first sentence.

    3. Design one page, one width.

    4. Send it over, set breakpoints.

    5. Connect your domain and publish.

  • The rules that make it finish

    Write before you design. The first sentence is the hardest part of a personal site and no layout decision can rescue a page that has not decided what it says.

    One width first. Design the desktop page, get it published, then handle the narrow layouts. Designing three breakpoints in Figma before anything exists is how a weekend becomes a quarter.

    Publish at 80%. A live site with three case studies beats a perfect one with six that nobody has seen. You can add the fourth next month.

    Put a date on it. One line at the bottom saying when it was last updated does more for credibility than another animation.

Frequently asked.

How do I make a personal website?

Decide the three things above before you open a design tool, gather the proof you already have, then lay out one page and only split it once a section outgrows it. The order matters: people who start by picking a template spend the time on decoration and still have nothing to say. Design it wherever you already work — if that is Figma, it can go straight to a live URL without a rebuild.

What should a personal website include?

One sentence saying what you do, proof of it, and a way to reach you. Everything beyond those three is optional and should earn its place. A site with those three and nothing else is finished; a site missing any of them is not, however good it looks.

How many pages should a personal website have?

Between one and six for almost everyone. One if your work lives elsewhere, three to six if you have case studies. If you are past ten, you are building a content site and should choose a tool with a real content system rather than designing every page by hand.

Do I need a blog on my personal site?

Only if you will write. A blog with two posts from 2023 actively damages the site, because it tells a visitor you started something and stopped. If in doubt, leave it out and add it when you have four pieces ready.

Should I use a template or design my own?

If you are a designer, designing your own is the point. If you are not, a template will be better than what you would build and much faster. The honest test is whether the site is the work or the container for the work.

How much does a personal website cost?

The domain is roughly $10 to $20 a year. Publishing costs money on every serious platform: from $7/mo billed yearly here, and $10 to $19 a month elsewhere. Some builders do publish free to their own subdomain with a badge on it, which for a personal site tends to defeat the purpose. Siter.io is not one of them, because no - the free plan builds and previews privately; publishing needs a paid plan.

Can I build a personal website from a Figma design?

Yes, and it is the fastest route if the design already exists. Yes, on every plan including free - one-way import, no re-sync, though prototype animations and interactions do not import. Our Figma plugin page walks the whole path, and the Webflow route is written up separately.

  • Figma plus Siter.io

    Design it in Figma. Publish it here.

    If the layout above already exists as a Figma frame, the plugin sends it over and you finish it on the canvas. Publishing to your own domain starts at $7/mo billed yearly.

    Get the plugin ->
  • Start for free with Siter.io

    Start for free ->
Hey there 👋  Friends from designmodo are here to help!