PhD student website examples that do what a CV can't

Your CV already lists what you have done. A website is for everything a CV has no room for: what the work actually looks like, why it matters, and what you are doing next. This page shows six real PhD-stage academic websites — all live, all linked, none of them ours — each reviewed critically: what it does well, what it's missing, and what's worth stealing. At the end there's one you can click through, and honest advice on where to build yours when your budget is a stipend.

All six sites were visited and reviewed on September 2, 2026; roles and affiliations are as stated on each site at that time. None of these researchers is affiliated with Scilio, and several are hosted on platforms that compete with us — that's the point. Sites change; if an annotation no longer matches, tell us: support@scilio.app.

What a PhD student's website has to do (that a professor's doesn't)

A professor's site has to serve prospective advisees, current students and colleagues at once. Yours has a narrower job and a harder one: convince people who have never heard of you that your work is worth their time, using less material than you wish you had.

Which brings up the thing most people are actually worried about. Your publication list is short. That is not the problem you think it is. A survey of 317 early-career researchers who applied for faculty positions in the 2018–2019 cycle found that the total number of publications, the number of first-author publications, the number of corresponding-author publications and h-index all failed to significantly correlate with the share of applications that produced an offer. Total citations did. The same survey found that 40% of those applicants had an active preprint that had not yet been published in a journal.

Read the caveats before you read too much into it: 317 self-selected respondents recruited through Twitter, a Slack group and postdoc mailing lists, one hiring cycle, 13 countries with 72% in the United States, and it measures faculty applications specifically. It is not evidence about what any particular committee does, and nobody has measured whether hiring committees look at personal websites at all.

But it is enough to retire one bad instinct. If a longer list is not what moves the outcome, then padding one is not what your site is for. Showing the work — the paper people can actually read, the code they can run, the preprint you would otherwise hide behind “under review” — is.

That leaves three decisions a professor never has to make:

  • Which audience wins. Most PhDs do not end up in academia, and a site built for a hiring committee looks nothing like one built for industry. Committees want publications, venues and a CV; industry wants projects, outcomes and a plain-English description of what you can do. Two of the sites below chose opposite answers, and both are better for having chosen.

  • What to show before you have results. A preprint, a conference talk, a well-written project page, a repository — these are exhibits. “Manuscript in preparation” is not.

  • Whether it survives you. You will build this on a student budget, on a domain you renew yourself, with a university email that expires when you graduate. The last section of this page is about what happens when that goes wrong, because it does.

If you want the full planning walkthrough before looking at examples, we keep one at how to make a personal academic website, step by step. For the other end of the career, see professor website examples, annotated through a professor's lens.

Six real PhD-stage websites, annotated

Each of these was visited and reviewed on September 2, 2026. For a broader set across every career stage, see our twelve academic website examples, annotated.

Mayank Mittal — Robotics, ETH Zurich and NVIDIA

al-folio (Jekyll) on GitHub Pages · mayankm96.github.io

This is what a publication list looks like when every entry is treated as an exhibit. Each paper leads with an animated GIF of the robot doing the thing, then the author list, the venue, and links marked Abs, arXiv, Website, Code and Video. The news feed is dated and current — the top item on the day we checked read “Apr 26, 2026 — Our paper on Visual Sim-to-Real for Robust Dexterous In-hand Reorientation is accepted at RSS 2026” — and there's a downloadable CV under a vitae tab.

What's missing: Almost no narrative. You learn what he built; you learn very little about how he thinks or where the research is heading. The header reads “Graduate Student | ETH Zurich | NVIDIA”, which is an unusual double life worth a paragraph, and it doesn't get one.

What to steal: One visual per paper. A GIF or a figure turns a citation line into something a reader stops on, and it costs you nothing you don't already have in the paper.

Lauren Nicole DeLong — Artificial intelligence, University of Edinburgh

GitHub Pages · laurendelong21.github.io

An icon-based overview of her research areas that a non-specialist can parse in seconds — rare, and genuinely useful when your subfield's name explains nothing. Real achievements are surfaced: an Alan Turing Institute Enrichment Scheme place, a survey paper in IEEE TNNLS, a talk at NeSy 2024 in Barcelona.

What's missing: There is no publication list. Visitors are sent to Google Scholar instead: “To see my latest publications and preprints, check out my Google Scholar page.” That trade costs a PhD student more than it costs a professor. Scholar shows a short list stripped of context, ordered by citations you have not accumulated yet, next to strangers with the same name — where your own page could show three papers with abstracts, code and a sentence each on why they matter. The blog's most recent post is “Neurosymbolic AI for graphs: a crime scene analogy” from March 23, 2023.

What to steal: The research-areas overview. The lesson to avoid: own your publication list, especially while it is short enough to present well.

Belén Otero — Computational biology, Universidad Politécnica de Madrid

faculty.bio · belenoteroc.faculty.bio

A tidy, fast-to-produce CV structure — Education, Work Experiences, Skills — that makes real breadth legible in one screen, including a PhD internship at Harvard running since 2023 alongside her position at UPM's Center for Biomedical Technology.

What's missing: For a portfolio branded computational biology, there is not one publication, project or repository to open. A single outbound link to her lab profile is the only place the work exists. It is a well-organised claim of expertise with no exhibits.

What to steal: The cautionary lesson. Every listed skill and position needs an artifact a reader can click, and this matters most at PhD stage, precisely when the CV is thinnest — experience without evidence is a CV, and you already have one of those.

Related: how Scilio compares to faculty.bio

Hira Javed — Service design, doctoral candidate

Zyro · hirajaved.com

This is the clearest “industry wins” answer on the page, and it is coherent. The nav runs Work, Teaching, Research, Publications, Presentations — practice first, research second — and she describes herself as “a service design professional with a strong practical and academic background in facilitating interdisciplinary collaborations”. Someone hiring for a design role learns what she does in ten seconds.

What's missing: Every academic handle. No ORCID, no Google Scholar, no repository links, no CV to download, and no institution named anywhere — so an academic reader cannot verify the doctorate or find the work. The site also carries no dates at all, which makes it impossible to tell how current it is.

What to steal: The decisiveness, not the omissions. If your future is industry, lead with practice. Just keep one page that an academic can use, because you may want that door open later.

Cecilia Baldoni — Behavioural biology and science communication

Quarto on GitHub Pages · cecibaldoni.github.io

The best argument on this page for building a site during your PhD rather than after it. Baldoni trained as a behavioural biologist through a PhD and a postdoc and now works in scientific marketing — and the site carried her across, because it was hers. It still runs About, Projects, Publications, Talks and Workshops, and a blog; she still teaches, mentors, illustrates and writes. The copyright reads 2026, Google Scholar sits next to Substack, Bluesky and GitHub, and it won Best Interactive Website in the 2025 Best Personal Academic Websites contest.

What's missing: No ORCID and no visible email address — for a site this well kept, the two cheapest fixes available.

What to steal: The premise. A site tied to your university profile disappears when you do; one you own becomes the thing that explains a career change instead of a gap.

Meg Mindlin — Molecular and marine biology, science communication

Squarespace · megmindlin.com

Reach. “Scientist. ARTIST. Photographer.” is a positioning statement, and the site delivers on it: science-communication writing, campaigns, art and photography, a downloadable CV dated 2025, and outputs with genuine external reach — a New York Times quote, a piece for Octo Nation, podcast episodes, a thesis presentation on YouTube, an SICB 2025 talk.

What's missing: Everything lives somewhere else. There is no on-site research record — no ORCID, no Google Scholar, no DOI — so the work can only be reached through platforms that may not outlast it. Her stage is also left unstated: the site lists a B.S. from UC Santa Cruz and an M.S. from Walla Walla University and past work with UC Merced's Nishiguchi Laboratory, but names no current position, so a reader cannot tell where she is now.

What to steal: The breadth, and the warning underneath it. Outbound links are how people find you; an on-site record is how they verify you. You need both, and one line stating your current position costs nothing.

What the good ones have in common

  1. 1.

    The strong ones show work; the weak ones describe it. The single clearest divide on this page is not design or platform — it is whether there is anything to open. Mittal's GIF-per-paper and Baldoni's project pages are exhibits; Otero's skills list and Javed's unlinked Publications tab are claims.

  2. 2.

    Publications hide, and it costs PhD students most. Two of six have no on-site publication list. At a career stage where the list is short enough to present beautifully — with abstracts, code, and a sentence of context each — outsourcing it to Google Scholar throws away the one presentation advantage you have.

  3. 3.

    Dates are the honesty signal. Mittal's April 2026 news item and Baldoni's 2026 copyright tell you the site is alive in a second. Javed's site has no dates anywhere and DeLong's most recent post is from March 2023 — and you notice, immediately.

  4. 4.

    Nobody hedges well. The sites that read as confident picked an audience. The ones that feel unfinished tried to serve academic and industry readers with the same page and committed to neither.

The site has to survive the degree

Two ways a PhD-stage site dies, and both are worth planning around before you build.

It stops being updated. Adam McCarron's astronomy site — one of the twelve we annotate on our broader examples page — is a perfectly reasonable Jekyll build whose copyright still read 2022 when we checked it again on September 2, 2026. Nothing on the page tells a visitor whether the research, or the researcher, has moved since. A visibly stale portfolio undercuts the work it presents.

It stops existing. In November 2025, a contest picked twelve of the best personal academic websites. One of the winners was a PhD student on their own custom domain. When we followed that link on September 2, 2026 — roughly ten months later — the domain no longer served a website: it answered with a redirect to an ad-survey page. We are not naming them, because this is not a failure of care. It is what a lapsed renewal looks like, and renewal notices go to the email address you had when you registered, which for most PhD students is the one the university closes behind them.

The practical version: put the domain renewal on a personal card and a personal email address, set a calendar reminder for the year you defend, and pick a setup whose upkeep you will still tolerate in year five. If that sounds like more maintenance than you want, academic website templates — code you fork versus demos you click lays out what each route actually costs to keep alive.

One you can click through

Screenshots — ours included — can't show the thing that matters: what a site feels like to navigate. So here's a live one: Tomás Aldana, a computational-linguistics PhD candidate with a code-heavy project list, in the Editor theme. Tomás is a fictional persona and his photo is AI-generated — he exists so you can click around a finished PhD-stage site without us parading a real customer. He's built on Scilio (that's us); his page wears the Editor theme, one of twenty a portfolio can be dressed in.

Building one on a stipend

Three honest routes, and the right one depends on what you want to spend.

You write code and want to own every pixel. Fork a template. Mittal and DeLong are on GitHub Pages, Baldoni is on Quarto — free hosting, total control, and a real maintenance bill in your own hours. Our templates comparison covers what each one costs to keep running.

You want it done this week with no code. Builders handle the structure for you — Otero's site is on faculty.bio, and there are several others worth comparing. We put the academic website builders side by side with date-stamped prices.

You want a publications-first site done in an evening. That's the case we built Scilio for: import your publication list by BibTeX or DOI, pick a theme, publish. Held to the same standard as everyone else on this page — Scilio is portfolio-only by design, with no lab or group sites and no ORCID import. Building and publishing at your own scilio.app address are free; a custom domain, the other themes and visitor analytics come with the paid plan.

Build your own

Every researcher above started with the same blank page, and most of them started with a shorter publication list than they wanted. Build and publish yours for free — publications, projects and all — at your own scilio.app address.