Appearance

Language

Build a personal website from 0

Personal Website Examples: 10 Real Sites and What Makes Each One Work

Ten live personal websites, from Paul Graham's bare essay list to Brittany Chiang's portfolio and Maggie Appleton's digital garden, with the one idea worth copying from each. The good ones all say who the person is in a sentence and point to one thing to read or do next.

Kelvin Wang · · 11 min read

Key points

  1. The good personal sites say who the person is in one sentence near the top.
  2. Each one has a single main job, and the navigation follows from that job.
  3. Proof beats adjectives: dated job history, a list of essays and projects with the tools named.
  4. Plain or old-fashioned design is fine; several of these sites look minimal and are still widely read.

The best personal websites are small and specific. Each of the ten I picked tells you who the person is within a sentence or two, shows proof of their work, and gives you one obvious next click. For each site you get what’s on it (all checked live on 7 November 2026), why it works, and the single idea you can borrow for your own site. One of them is mine, kelvinwang.info, because I can show you how it is built from the inside.

SiteOwnerTypeIdea to borrow
paulgraham.comPaul GrahamEssaysLet the writing be the whole site
sive.rsDerek SiversWriter, authorA dated /now page
brittanychiang.comBrittany ChiangDeveloper portfolioOne page that reads like a résumé
joshwcomeau.comJosh W. ComeauTeaching blogA summary under every post title
maggieappleton.comMaggie AppletonDigital gardenLabel how finished each piece is
jvns.caJulia EvansBlogEvery post on the home page
simonwillison.netSimon WillisonLink blogSeveral post sizes, short ones included
rauno.meRauno FreibergDesign portfolioOne sentence and almost nothing else
patrickcollison.comPatrick CollisonTopic pagesPages about interests, not a timeline
kelvinwang.infoKelvin WangEngineer, bilingualGroup your work into a few areas

1. Paul Graham: the essays are the site

The home page of paulgraham.com is a narrow column of plain text links down the left (essays, books, his Lisp projects, RSS, bio, email and a few more), a large picture, links to his two newest essays and one line telling founders they can apply to Y Combinator. Click through to the essay index and you get a single long list of titles, newest first, with no dates, thumbnails or categories. At the top of that index he names a few essays to start with if you don’t know where to begin.

Why it works: everyone who visits came to read, and nothing gets between them and the text. The design looks like it was made in the late 1990s, and it doesn’t matter, because the essays carry the site.

Borrow this: if your writing is the reason people come, put a plain list of it front and center, and add a short “start here” line that points newcomers to two or three pieces you’re proudest of. That one line saves a first-time visitor from guessing.

2. Derek Sivers: a /now page with a date on it

sive.rs opens with a “me in 10 seconds” block that splits his life into eras: musician, entrepreneur, author. Below that sit links to a longer about page, a now page, a contact note saying he answers email, his newest articles and his books. A line at the top says nothing on the site is written by AI.

The idea people copy most is the /now page: a short page about what he’s focused on at the moment, with the date it was last updated and where he was when he wrote it. He started a directory of other people’s now pages, nownownow.com, and the format spread from there. He also keeps a /uses page listing his tools.

Borrow this: add a /now page and put the update date at the top. It gives returning visitors a reason to come back, and the date is honest about how fresh it is. Three or four short paragraphs is enough.

3. Brittany Chiang: a portfolio that reads like a résumé

Brittany Chiang’s site is the developer portfolio many people try to copy. It’s one page. On a wide screen, a column on the left stays fixed and holds her name, her role in a few words, section links and social icons. The right side scrolls through About, Experience, Projects and Writing. Each job has dates, a short description and the technologies she used as small tags. Links to a full résumé and a project archive sit at the end of their sections. The footer says which tools she designed and built it with (Figma, Next.js, Tailwind CSS, Vercel) and which typeface it uses.

Why it works: a recruiter or hiring manager gets the answers they need in one scroll, in the order they’d ask them. Her old Gatsby version of the site is listed as a project too, and she notes it picked up thousands of GitHub stars and forks, so the portfolio itself became proof of her skill.

Borrow this: if the site exists to get you hired, lay it out as About, Experience, Projects, Writing on one page, and tag every role and project with the tools you used. Skip the separate pages until you have a reason for them.

4. Josh W. Comeau: a summary under every title

joshwcomeau.com is a teaching blog for front-end developers. The home page lists articles, and each one has a title (some with a short subtitle) and a summary of a few sentences that tells you what you’ll learn before you click. The navigation is just categories, courses, goodies and about. According to his courses page, building self-paced interactive courses has been his main job since 2020, so the free articles also act as the front door to what he sells.

Why it works: the summaries let readers pick the right article without opening five tabs, and the posts themselves are full of interactive demos, which is the reason people share them.

Borrow this: write a one- or two-sentence summary for every post and show it on your list page. If you sell anything, a course, a book or consulting, let your free writing lead to it with one link in the navigation instead of pop-ups.

5. Maggie Appleton: say how finished each piece is

maggieappleton.com calls itself a digital garden: a collection of notes and essays that grow over time. Her writing is sorted by kind. Essays are her long pieces with a clear argument, notes are thinking she hasn’t settled yet, patterns collect interface ideas she has spotted, and there are separate sections for small links and thoughts, talks, podcasts, books she recommends and an “antilibrary” of books she hasn’t read but wants around. On the home page, essays and patterns show their type and roughly how long ago they were written. The full garden index goes further and marks each piece as a seedling, budding or evergreen, a growth stage that tells you how settled the thinking is.

Why it works: she can publish half-formed notes without them being mistaken for finished essays, so she publishes far more. The labels set the reader’s expectations before they start.

Borrow this: if you hold back from posting because a piece isn’t polished, add a label like “note” or “draft” and publish it anyway. A visible type or stage on every item is the cheapest way to do that.

6. Julia Evans: every post on the home page

jvns.ca greets you with a one-line hello, then lists her ten newest posts, then every post she has ever written grouped by category. The top links go to about, talks, projects, her social accounts, favorites, a TIL (“today I learned”) section, zines and RSS. The intro points to Wizard Zines, where she publishes her computer zines, and offers a weekly email digest of new posts.

Why it works: the home page is also the archive. A visitor who likes one post can see the entire body of work immediately and scan by topic. Nothing is hidden behind pagination.

Borrow this: once you have more than a handful of posts, group them by topic on one page instead of paginating. Add a “favorites” page for the posts you’d hand to a stranger.

7. Simon Willison: posts in several sizes

simonwillison.net is a long-running weblog with several post types: full entries, links with commentary, quotes, short notes and longer guides. Tags show a running count, so you can see at a glance which topics he writes about most. He keeps a separate TIL site and a tools page, and offers a newsletter.

Why it works: most days he doesn’t have a full essay in him, but he does have a link worth sharing with a paragraph of context. Allowing small posts is what lets him keep posting several times a week.

Borrow this: decide that a link plus two sentences of your own thinking counts as a post. It keeps your site alive between big pieces.

8. Rauno Freiberg: one sentence, then get out of the way

rauno.me is close to empty on purpose. A single sentence names him, where he’s from, what he does and who he works with. Below that sit a handful of links (Devouring Details, his project about interaction design, a craft section, a history of software design, projects, field notes by year, social accounts and email) and a few short lines on how he wants his work made.

Why it works: he’s an interaction designer, and the restraint is the portfolio. The detail lives in the projects and craft pages for anyone who wants it.

Borrow this: write your one-sentence intro before you design anything: your name, what you do, and for whom or where. If that sentence is strong, a very small home page works.

9. Patrick Collison: pages about interests, not a timeline

patrickcollison.com is a plain list of topic pages: advice, a bookshelf, culture, a page called Fast listing big projects that teams pulled off in very little time, questions he’s curious about, travel and more. There’s no feed. Each page is a reference he can add to whenever he likes. The bookshelf page now opens with a warning that he hasn’t touched it in roughly a decade and may take it down.

Why it works: topic pages age better than dated posts, and people link to them as resources. The note on the bookshelf is a good habit too: it tells readers how old the page is instead of letting them assume it’s current.

Borrow this: pick one subject you keep coming back to and make it a page you update over time instead of a one-off post. When a page goes stale, say so at the top.

10. kelvinwang.info: a few work areas, two languages

This site is mine, so here’s what’s on it and why. The home page opens with a one-line headline and a sentence underneath saying I’m an electrical engineer who designs hardware, ships full-stack products and builds his own quant tooling. Below that are the three newest posts, then a Work section split into three areas (Hardware, Full-stack, Quant). Each area has one headline, a short description and tags for the tools involved. Each area also has its own animated simulation on the home page. Then comes a short About block, and the footer links to Threads, Instagram, LinkedIn, X and GitHub.

Some choices that are less visible:

  • Two languages. The site has Traditional Chinese (/zh-hant/) and English (/en/) versions with a language switch in the header, aimed at readers in Taiwan and English-language readers everywhere else. Most posts exist in both languages; a few, like this one, are written for one audience only.
  • The About page lists things I’ve made. It links to interactive 3D models of reported hardware-wallet implants, which is the most unusual work on the site, and ends with a note that anything I write about investing isn’t investment advice.
  • Machine-readable extras. There’s an RSS feed per language, a sitemap and an llms.txt file that summarizes the site and links to the main pages for AI tools.
  • Under the hood. It’s an Astro site running on Cloudflare Workers, with Supabase behind the private dashboard. The repo’s first commit is dated 10 June 2026, and it was built with an AI coding agent working from written specs and a design document.

One gap I’d point out to anyone copying it: there’s no contact page or email address, only social links. If you want inquiries, give people one obvious way to reach you.

Borrow this: if you do several unrelated things, don’t force them into one label. Name two to four areas, give each one a headline and a line of proof, and let visitors pick the one they came for.

What the good ones have in common

Look across all ten and the same few decisions keep showing up:

  • A one-sentence intro near the top. Rauno, Brittany, Maggie, Derek and my site all say who the person is and what they do before anything else.
  • One main job. Paul Graham’s site is for reading essays, Brittany’s is for hiring, Josh’s is for learning CSS. The navigation follows from that job.
  • Proof over adjectives. Job history with dates, a list of essays, a count of posts per tag, projects with the tools named.
  • Honest dates. Derek’s now page and Patrick’s bookshelf both tell you how old they are.
  • A way to keep up. RSS, a newsletter or a weekly digest appears on most of them.
  • Plain design is fine. Several of these sites are visually minimal or old-fashioned and still widely read.

How to use these examples for your own site

You don’t need ten ideas. Pick the example closest to your goal and copy its structure:

  1. Write your one-sentence intro first. Name, what you do, for whom. This becomes the top of your home page and your page description.
  2. Decide the site’s one main job. Getting hired points to Brittany’s layout. Building an audience for your writing points to Paul Graham, Julia Evans or Simon Willison. Showing several areas of work points to my three-areas layout.
  3. Choose your pages. Most personal sites need a home page, an about section, a work or projects section, writing if you write, and a way to contact you. Add a /now page if you want people to come back.
  4. Ship a small version, then add. Every site above grew over years. Start with the home page and one other page, put it online, and add the rest as you have something to show.
Go deeper What to Put on a Personal Website (Free Template) A page-by-page checklist and a structure you can copy.

When you’re ready to build it, you can make a site like any of these yourself with free hosting and an AI coding tool, starting from an empty folder.

Go deeper How to Build a Personal Website with AI in 2026 The full walkthrough, from setting up your computer to a live site on your own domain.

Sources

  1. 1. Paul Graham, home page · paulgraham.com · checked 2026-11-07
  2. 2. Paul Graham, essay index · paulgraham.com · checked 2026-11-07
  3. 3. Derek Sivers, home page · sive.rs · checked 2026-11-07
  4. 4. Derek Sivers, /now page · sive.rs · checked 2026-11-07
  5. 5. nownownow.com, directory of /now pages · nownownow.com · checked 2026-11-07
  6. 6. Brittany Chiang, portfolio · brittanychiang.com · checked 2026-11-07
  7. 7. Josh W. Comeau, home page · joshwcomeau.com · checked 2026-11-07
  8. 8. Josh W. Comeau, online courses · joshwcomeau.com · checked 2026-11-07
  9. 9. Maggie Appleton, digital garden · maggieappleton.com · checked 2026-11-07
  10. 10. Maggie Appleton, the garden index · maggieappleton.com · checked 2026-11-07
  11. 11. Julia Evans, blog · jvns.ca · checked 2026-11-07
  12. 12. Simon Willison's Weblog · simonwillison.net · checked 2026-11-07
  13. 13. Rauno Freiberg, home page · rauno.me · checked 2026-11-07
  14. 14. Patrick Collison, home page · patrickcollison.com · checked 2026-11-07
  15. 15. Patrick Collison, Fast · patrickcollison.com · checked 2026-11-07
  16. 16. Patrick Collison, Bookshelf · patrickcollison.com · checked 2026-11-07

About the author

Kelvin Wang

Electrical engineer building tools with AI agents, sharing hands-on notes on engineering and investing.

More about me