The one-page résumé website — one link for recruiters, built in an evening
Recruiters look at a résumé for a few seconds. They look at a LinkedIn profile for a few more. What they rarely get is the thing that would actually make them remember you: a single page, designed by you, that shows the work, tells the story in your voice, and gives them an obvious way to get in touch.
You don't need a developer or a personal-website template that takes a weekend. You need one page with the right sections behind one link. This guide builds it, section by section, and covers the details that make a hiring manager stop skimming.
Why a page beats a PDF
A PDF is a document. It's static, it's the same for everyone, it doesn't link to anything, and on a phone it's a pinch-and-zoom chore. A page is a product. It has a hierarchy you control, it links to your work, it can embed a talk you gave or a project demo, it has a contact form, and it works on a phone. It also tells you who looked at it, which a PDF never will.
You still need the PDF for application portals. The page is what you put in your LinkedIn header, your email signature, your Instagram bio, and the "website" field of every form that asks.
The sections, in order
1. Hero. Your name, what you do in one line, where you're based and whether you're open to remote. A photo, if you're comfortable; it makes you a person rather than a document. One button: "Get in touch" or "Download CV".
The one-liner is the hardest part and the most important. It's not your current title. It's what you do and for whom: "Product designer, six years in fintech, currently looking." Or "Backend engineer who likes boring, reliable systems. Go and Postgres."
2. Résumé. Experience and education as a timeline: role, company, dates, and two or three lines per role about what you actually did and what changed because of it. Numbers where you have them. "Cut checkout errors 40%" beats "responsible for checkout."
Keep it to the last three or four roles. The page isn't your entire history; it's the argument for the next role.
3. Skills. A tidy row or grid of tags: the tools, languages, methods. Group them if there are many. Don't rate yourself out of five; nobody trusts those bars.
4. Projects. Three to six, each with an image, a title, a one-line description, tags, and a link. For engineers, the repo and the live thing. For designers, the case study. For marketers, the campaign and the result. For anyone, the thing you're proudest of first.
If a project can be shown, show it: embed the demo video, the talk, the Figma prototype link.
5. Proof. A stats row ("6 years · 40+ projects · 20 open-source repos") or two short testimonials from managers or colleagues. Optional, but it works.
6. Contact. A form: name, email, company, message. Every submission emails you. This is better than exposing your email address to scrapers, and it looks more considered.
7. Links. LinkedIn, GitHub, Dribbble, Behance, X, the PDF résumé. Icons for the socials, a button for the PDF.
BonPages has a Developer starter that comes arranged like this on the Midnight theme, and the Mono theme (black on white, square corners) which reads as serious and gets out of the way.
Writing it
Cut adjectives, keep verbs and numbers. "Passionate, detail-oriented team player" says nothing. "Led a team of four through a payments migration with zero downtime" says everything.
Write in first person, lightly. "I build…" not "Built…". It's your page; it should sound like you talking.
Say what you want. A line in the hero or at the top of the contact section: "Looking for a senior product design role, remote or London, from October." Recruiters can't act on ambiguity.
Keep it to one scroll. If it's longer than a résumé, you've written an autobiography. The page should be readable in ninety seconds.
The details that get noticed
A real URL. bonpages.com/u/janecooper is fine. janecooper.com is better, and it's a PRO feature if you want it, but start with the free one; the content matters more than the domain.
Speed. The person reading it might be on a train. The page loads fast because it's server-rendered and images lazy-load. Don't upload 8MB screenshots.
Search engines. Set the page's meta title and description in settings: "Jane Cooper — Product Designer, London". Your name should find your page.
The social preview. When you paste the link into LinkedIn or a message, it shows a card. BonPages generates one automatically from your page's name and theme, or you upload your own image in the page's SEO settings.
Analytics. You'll be able to see when the page gets visits and where from. A spike the day after an interview tells you the panel looked you up. A visit from a company's IP range isn't shown (analytics are cookieless and don't identify people), but a jump in views from LinkedIn the week you applied somewhere is signal.
Projects, for different kinds of work
Engineers. Repo, live URL, what it does in one line, the stack as tags. Embed a short screen recording for anything visual. Link the pull request you're proud of, not just the repo.
Designers. One image per project, the problem, what you did, the result. Link to the full case study. A prototype embed if it's interactive.
Marketers and writers. The piece or campaign, the number it moved, the link. An embedded X post if a thread performed.
Researchers and academics. The paper, the venue, a one-line finding, a PDF embed of the paper itself.
Everyone else. Whatever the work produced. A photo of the thing, a description, a link.
A second page, if you need one
A single page is right for most people. If you have a lot of writing, a lot of projects, or want a proper "About", add pages with a menu: Home, Work, Writing, Contact. It's still one link in your bio, and each page has its own URL you can send directly.
Keeping it current
A résumé site that says "currently at X" six months after you left X is worse than no site. Update the page the day something changes: a new role, a project shipped, a talk given. Because it's a page you edit in a browser, this takes two minutes.
When you get the job, don't take the page down. Change the hero line to what you do now, remove "looking", and leave it. The next time you're looking, it's ready.
Tailoring the page for an application
You can't tailor a PDF for every application without a folder of versions. You can tailor a page in two minutes. Before applying somewhere specific, reorder the projects so the most relevant one is first, adjust the one-liner to speak to the role, and move the matching skills to the front. Then send the link. If you want to go further, make a second page for that company ("Why me for Acme") with a short note and the three most relevant projects, and link to it from the application. Nobody else is doing this, which is exactly why it works.
For people changing careers
The résumé timeline is the weakest part of a career-change story, because it points backwards. The page lets you lead with where you're going. Put the new-field projects first, even if they were side projects or coursework. Write the one-liner about the new direction. Put a short "Why I'm moving into this" paragraph in a Markdown block. Move the old experience down and keep the lines that transfer: the management, the numbers, the communication. A hiring manager reading the page sees the case for you before they see the gap.
Students and first jobs
With little experience, the page carries more weight, not less, because it's the only thing that shows what you can do. Projects become the centre: coursework you're proud of, a hackathon entry, a club you ran, a small business you started. Skills stay honest. The résumé block lists the internship, the part-time work and the degree. The contact form and a clear "graduating June 2027, looking for a junior role in…" line do the rest.
What to measure
Page views and traffic sources. Views tell you whether anyone's finding the page; sources tell you whether it's LinkedIn, a search, or a direct link from an email. Form submissions are the point: each one is a conversation.
Building it tonight
Sign up to BonPages, pick Midnight or Mono, choose the Developer starter (it works for any profession; swap the sample content), fill in the résumé block with your last three roles, add three projects with images, write the one-liner, add the form, publish, and put the link in your LinkedIn header and your email signature.
It's free, and it stays free: the résumé, skills, projects, form and analytics blocks are all on the free plan. A recruiter who opens it will see a page, not a document, and that's the whole difference.
