How to Build a Project Page for Your Paper

Someone sees your paper title in a talk, a thread or a reading group and searches for it. The first result is a PDF. The second is a code repository whose README opens with installation instructions. Neither tells them, in thirty seconds, what you found and why it matters.

A project page fixes that. It is one URL that says what the paper does, shows it, and links to everything else. It works for a machine learning method, a psychology study or a biology protocol.

What a Good Project Page Looks Like

The Nerfies project page is a useful model because it is short. It opens with the title, the authors and their affiliations, then one line that says what the method does: it "turns selfie videos from your phone into free-viewpoint portraits." Below that come the abstract, video results grouped by what they show, and a BibTeX block at the bottom.

Its source repository is public, and the README says the website is licensed under Creative Commons Attribution-ShareAlike 4.0. If you adapt it, read that license first and keep the attribution it asks for.

The Template, Section by Section

This is the order that works for most papers. Everything above the abstract should make sense to someone who never scrolls further.

Section	What goes in it	Keep in mind
Title and authors	Paper title, every author with a link, affiliations, venue and year	Use the exact published title so search matches it
Teaser	One image, GIF or short clip that shows the main result	Pick the figure you would put on a poster
One-line result	A single plain sentence: what the work shows or makes possible	No acronyms the reader has to look up
Link buttons	Paper (DOI or arXiv), PDF, code, data, video	Link the version of record once it exists
Abstract in plain words	Three to five sentences a smart outsider can follow	The full abstract can sit in the PDF
Video	A short explainer or results video	Caption it so it works with the sound off
Key figures	Two or three figures with one-line captions	Captions say what to notice, not just what is plotted
Citation	A BibTeX block people can copy	Update it when the conference or journal version appears

A worked example

Say you have a machine learning paper on detecting label noise in medical image datasets. The teaser is a grid of four images your method flagged, with the original and corrected labels. The one-line result reads: "A method that finds mislabeled training images without extra annotation." The buttons point to the arXiv abstract, the code, the cleaned label files and a two-minute video. The plain abstract explains why noisy labels matter, what the method does differently, and what the evaluation covered, in four sentences. Everything else lives in the paper.

Hosting It for Free on GitHub Pages

Most project pages are static HTML, and GitHub Pages hosts that without a server. A few details from GitHub's documentation, at the time of writing (October 2026), that save time:

• On GitHub Free, the repository for the site must be public.
• GitHub Pages looks for an index.html, index.md or README.md file as the entry point.
• A project site lives at an address like https://<user>.github.io/<repository>/, so name the repository after the paper.
• Changes can take up to 10 minutes to publish after you push.
• Pages sites are publicly available even if the repository is private (where your plan allows that), so do not leave unpublished data in the repository.

If your lab already has a website, a subpage there works too. What matters is one stable URL you can put on slides, posters and social posts. For how papers fit on a lab site more generally, see building a publications page that gets read.

Make It Easy to Cite

Put a BibTeX block on the page, and keep it current. When the conference or journal version comes out, replace the preprint entry and add the DOI.

If people reach your work through the code, add a CITATION.cff file to the repository root. GitHub's citation file documentation says this adds a "Cite this repository" link to the sidebar, formatted as APA and BibTeX. Its preferred-citation field lets you point that link at the article rather than the software, which is usually what you want for a paper.

Connect It to Where Readers Already Are

For machine learning papers on arXiv, Hugging Face paper pages are a second front door. At the time of writing (October 2026), you can claim authorship of your paper there (Hugging Face's admin team validates the claim). If the paper has been submitted to Daily Papers, its authors can add images or videos, and the first video or GIF becomes its cover in the feed. If a model or dataset card links to the arXiv paper, the Hub tags that repository with the paper so people can find it. Link your project page from the paper page and from the repository README, and it becomes the hub that everything points back to.

For more ways to reach readers after the arXiv listing, see promoting a machine learning paper beyond arXiv.

A Short Launch Checklist

1. Title, authors and links match the published version.
2. The teaser and one-line result make sense without scrolling.
3. Every button works, including the data link.
4. The video has captions and a still that is not a black frame.
5. The BibTeX block and CITATION.cff describe the same paper.
6. The page URL is on your slides, poster and social posts.

Where Amplify Fits

The slowest parts of a project page are usually the video and the plain-language summary. Amplify makes both from the PDF you upload and nothing else: a video abstract (16:9, about 3 minutes), a vertical short (9:16, 45 to 60 seconds) for the teaser slot or social posts, an audio brief in English (with 21 more languages on request), and a one-page infographic. Every artifact carries the title, the authors and a link back to the paper of record.

Each format arrives as three variants you can edit line by line or regenerate. A person reviews every format before it is released, and nothing publishes until you approve it. If you would rather not edit HTML each time, the embeddable widget is one script tag per page and one marker per paper, so readers can read, listen and ask questions about the paper without leaving your project page. Its analytics show reads, listens, questions asked and which format moved people.

A project page is a small piece of work that keeps paying back: every talk, citation and repost now lands somewhere that explains the paper. Build it the week the paper goes public, and update it once when the final version appears.

See what Amplify makes from one paper