Examples
Research Portfolio Examples: 12 Real Academic Websites, Annotated
The fastest way to figure out what your research portfolio should look like is to study real ones — so here are twelve research portfolio examples from actual PhD students, postdocs and faculty, across ten disciplines and seven different platforms. Every site below is a real researcher's live, public page, linked so you can explore it yourself. For each, we note what it does well, what's missing, and what's worth stealing for your own portfolio — because even excellent portfolios have gaps, and even flawed ones contain one great idea.
All portfolios verified live on July 24, 2026; roles and affiliations are as stated on each site at that time. None of these researchers are affiliated with Scilio — several are hosted on platforms that compete with us, and they're here because they're good examples.
PhD student portfolio examples
Mayank Mittal — Robotics, ETH Zurich
al-folio (Jekyll) on GitHub Pages · mayankm96.github.io
What it does well: Each publication gets an animated GIF teaser alongside its author list, venue, and links to the abstract, arXiv, project page and code. For robotics — where the work moves — this beats any static list. A dated news feed proves the site is alive.
What's missing: Almost no narrative text — you learn what he built, but little about how he thinks or where the research is going.
What to steal: Treat each paper as a mini project page with its own visual, not a citation line.
Sanghyun Son — Computer science, University of Maryland
Owlstown, on a custom domain · sanghyun.phd.sh
What it does well: The cleanest publication machine in this list: papers grouped by year with thumbnails, full co-author lists, venues and per-paper arXiv/GitHub/project links — plus dated acceptance announcements that double as a freshness signal. Also proof that builder platforms can carry a serious CS publication record.
What's missing: Dense, text-heavy layout with little visual hierarchy; it rewards readers who already care.
What to steal: Year-grouped publications with resources attached to every paper.
Lauren DeLong — Artificial intelligence, University of Edinburgh
GitHub Pages · laurendelong21.github.io
What it does well: An approachable icon-based overview of her research areas that a non-specialist can parse in seconds, plus news items (fellowships, invited talks) that carry real signal.
What's missing: There's no publication list on the site — visitors are routed to Google Scholar. Scholar is a database, not a presentation: no selection, no annotation, no attached code. The blog's last post is from 2022, and there's no downloadable CV.
What to steal: The visual research-areas overview. The lesson to avoid: own your publication list.
Belén Otero — Computational biology, Universidad Politécnica de Madrid
faculty.bio · belenoteroc.faculty.bio
What it does well: A tidy CV-style structure (education, work experience, skills) that shows international and industry breadth — including a Harvard research internship — in one screen. faculty.bio's template makes this genuinely fast to produce.
What's missing: For a portfolio branded “computational biology,” there is not a single publication, project or repository to click. It's a well-organized claim of expertise with no exhibits.
What to steal: The cautionary lesson, mostly: every listed skill or position needs an artifact a reader can open. Experience without evidence is a CV, not a portfolio.
Adam McCarron — Astronomy, UT Austin
Beautiful Jekyll on GitHub Pages · apm5587.github.io
What it does well: A friendly, low-tech site that gets the basics up: research areas, a publications link, even a tutoring page — a reminder that a simple Jekyll theme is enough.
What's missing: Any sign of life. The copyright reads 2022 and nothing on the page indicates whether the research — or the researcher — has moved since. Publications live on a subpage; there's no CV.
What to steal: Nothing structural — its value here is the warning. A visibly stale portfolio undercuts the work it presents. Plan for the upkeep, or choose a setup that minimizes it.
Postdoc & early-career portfolio examples
Nicole Paul — Earthquake engineering, ETH Zürich
Hugo Blox · nicolepaul.io
What it does well: Featured publications carry abstracts plus PDF, code, dataset and DOI links — the fullest open-science presentation in this list. She even wrote a post documenting how she built the site.
What's missing: Publication types blur together visually, and the blog trails off in 2024.
What to steal: The per-paper resource row (PDF · code · data · DOI). It makes every paper a destination instead of a citation.
Alexandra de Gendre — Economics, University of Melbourne / CNRS
Quarto · adegendre.github.io
What it does well: A complete, quietly professional economist's site — research, CV, talks, teaching — with ORCID, Scholar, GitHub and Bluesky all one click away. Mid-transition between fellowships, the site does exactly what a portfolio should: it stays the stable address while affiliations change. She also published her own Quarto website tutorial.
What's missing: The homepage shows no publications at all — you have to go digging in Research; and a single headshot is the page's only visual.
What to steal: Keeping the portfolio as your permanent professional address across moves — the use case university profile pages can't serve.
A. Solomon Kurz — Clinical psychology & statistics, VA research
Hugo Apéro · solomonkurz.netlify.app
What it does well: Goes far beyond a publication list: books, workshops and courses sit beside the papers, turning the portfolio into an open-education hub people return to — the strongest answer in this list to “why would anyone visit twice?”
What's missing: The homepage gives no date cues (the footer says 2022), which undersells how much substance is behind it.
What to steal: Give visitors a resource, not just a record — teaching materials, tutorials or code that makes your site worth bookmarking.
Julie Lai — Data science
datascienceportfol.io · datascienceportfol.io/juliejlai
What it does well: Four genuinely diverse projects — a Spotify recommender, neural machine translation, an audio-responsive music visualization — tied together with a stated narrative connecting data work to journalistic inquiry. The narrative thread is what most project portfolios lack.
What's missing: Project descriptions truncate behind “read more,” outcomes aren't quantified, and the platform's project-card format leaves no room for publications — fine for industry data science, limiting for research.
What to steal: One sentence of narrative that makes a project list read as a direction, not a heap.
Faculty & senior researcher portfolio examples
Martin Bulla — Ornithology, Czech University of Life Sciences Prague
al-folio (Jekyll) on GitHub Pages · martinbulla.github.io
What it does well: Two details worth the visit alone: an explicit “last updated” date on the site — the cheapest possible freshness signal, and almost nobody uses it — and a dedicated Repos section, rare and excellent for a field biologist.
What's missing: The publication presentation leans on external profiles instead of a rich on-site list.
What to steal: The visible last-updated date. It converts maintenance from a chore into a trust signal.
Mark P. M. Dean — Condensed matter physics, Brookhaven National Laboratory
al-folio (Jekyll) · markdean.info
What it does well: A personal site that scales into a group site: People, Openings and Group-notes pages alongside research, with a separate Preprints section — exactly right for a fast-moving physics field — and a dated news feed linking published work in Science and Physical Review B.
What's missing: No CV or teaching page, and the core pages are sparse — the news feed carries the site.
What to steal: Splitting Preprints from Publications, and the Openings page: a portfolio can recruit for you.
Andrew Heiss — Public policy, Georgia State University
Quarto, custom domain · andrewheiss.com
What it does well: Probably the best-known Quarto academic site, and a masterclass in site-as-professional-identity: a full teaching portfolio linking standalone course websites, plus Now, Uses and AI pages that answer questions visitors actually have. The copyright spans nearly two decades of continuous presence.
What's missing: The homepage surfaces almost none of it — recent work and highlights take digging.
What to steal: The “Now” page — one honest paragraph on what you're currently working on beats an outdated news feed.
What the good ones have in common
Patterns across these twelve — observed, not theorized:
- 1.
Papers ship with their artifacts. The strongest sites (Mittal, Son, Paul) attach code, data or a project page to every publication. A citation is a claim; a linked artifact is proof.
- 2.
Freshness is visible. Dated news feeds (Dean, Mittal, Son), an explicit last-updated line (Bulla) — while the weakest sites' only date is a stale copyright. Visitors check for signs of life before they read a word.
- 3.
The site says who you are, not just what you published. A narrative thread (Lai), an education hub (Kurz), a Now page (Heiss). The list-only sites are forgettable even when the lists are good.
- 4.
Curation beats completeness. “Featured publications” (Paul), selected projects (Lai) — the good sites choose. The complete record belongs in the CV link.
- 5.
Profile plumbing is universal. ORCID, Google Scholar and GitHub links appear on nearly every strong site here — they're infrastructure, not decoration.
- 6.
The platform matters less than the maintenance. This list has excellent and abandoned sites on the same platforms. What separates them isn't the tool — it's whether updating is easy enough that it actually happens.
That last point is the honest pitch for purpose-built portfolio tools, ours included: reduce the site to the parts you'll maintain. If you want the full tool-by-tool comparison, it's in Academic Website Builders Compared.
Academic website templates by field (Scilio demos)
These are demo profiles, not real researchers — the personas are fictional and their profile photos are AI-generated. We built them ourselves to show what a Scilio portfolio looks like filled in — treat them as live templates you can click through in every theme. Unlike the screenshots on most examples listicles, these are real pages: same themes, same layout engine as a published portfolio.
Physics — undergraduate →
Liam Bennett (fictional): publications and projects from a physics student's first research steps, in the Default theme.
Marine ecology — postdoc →
Dr. Ilaria Bentes (fictional): heatwave-recovery research with field projects and citizen science, in the Marine theme.
Computational linguistics — PhD candidate →
Tomás Aldana (fictional): low-resource language technology with a code-heavy project list, in the Editor theme.
Neuroscience — professor →
Prof. Ingrid Vasseur (fictional): a full faculty publication record, including a labeled preprint, in the Serif theme.
Glaciology — mid-career researcher →
Dr. Aksel Rande (fictional): ice-core and monitoring research with outreach projects, in the Glacier theme.
Build your own
If the patterns above — structured publications with links, curated projects, a bio, zero site maintenance — are what you want without running a website, that's what Scilio is for. Build and preview your whole portfolio free; publish at scilio.app/yourname for €5/month or €48/year. Not sure what goes on the page? Start with the step-by-step guide.