A portfolio site is not a craft project. It is a sales asset that should take one day, ship to a real URL, and be honest about your work. The longer you spend tweaking the navigation, the less likely you are to ever launch.
This guide walks through a one-day path that actually finishes, with the stack and content order that work for most engineers and designers in 2026.
What changed in 2026
Three things matter for the build.
- Static-first frameworks are dominant. Astro and Next.js cover most cases; SvelteKit is a strong third.
- Free hosting is excellent. Vercel, Netlify, and Cloudflare Pages all deploy from a Git push in under a minute.
- AI design tools are good enough for the layout. v0, Lovable, or a Tailwind UI starter saves you the design loop.
How to plan the day
Five short bullets.
- Morning: outline content. Three case studies, one bio, one contact section.
- Midday: pick the stack. Astro or Next, Tailwind, deploy target.
- Early afternoon: build the layout. Use a starter, do not start blank.
- Late afternoon: write the case studies. This is the hard part.
- Evening: deploy and share. Custom domain optional.
1. The stack — best for shipping today
Astro for static-first sites with light interactivity. Next.js if you need React components throughout or plan to add a blog with dynamic content. Either one with Tailwind for styling. Deploy to Vercel or Netlify from a GitHub repo.
The trade-off is convention over invention. You will not have the most original site on the internet. You will have one that loads in 200ms and works on every device.
2. The content order — best for getting hired
Top of the page: name, one sentence on what you do, one button to your best case study. Then three case studies, each with the problem, your role, what you built, and the result with a number. Then a one-paragraph bio. Then a single contact link.
The catch: most developers reverse this order, leading with bio and burying the work. Recruiters skim top-to-bottom in fifteen seconds. Lead with the work.
3. The case study — best for proving you can ship
Each case study is one page, four sections, 300 words. Problem in two sentences. Role in one sentence. Approach in a paragraph. Result with at least one number. Add three screenshots. That is the whole thing.
The catch: you have to write them. AI can edit, but the specifics have to come from you, because that is what makes the work yours.
Comparison: portfolio stacks in April 2026
| Stack |
Best for |
Build time |
Catch |
| Astro + Tailwind + Vercel |
Most engineers, fastest path |
4–6 hours |
Limited dynamic content |
| Next.js + Tailwind + Vercel |
React-heavy work, blogs |
6–8 hours |
More config than you need |
| SvelteKit + Tailwind |
Animation-heavy portfolios |
6–8 hours |
Smaller ecosystem |
| Plain HTML + CSS |
Designers who want full control |
4 hours |
No component reuse |
| Squarespace or Framer |
Non-developers, designers |
2 hours |
Less customization |
Common mistakes to avoid
Building a CMS for one author. You do not need WordPress or Sanity for three case studies. Markdown files in a repo are fine.
Skipping the case studies. A site full of project screenshots and no narrative tells a recruiter nothing.
Custom domain before launch. Buy the domain after you have a live URL. Otherwise you spend two hours on DNS and never finish the content.
FAQ
Do I need a blog?
No. Add one later if you actually want to write. An empty blog hurts more than no blog.
Should I use a template?
Yes. Tailwind UI, Astro themes, or a Vercel template will save you the design loop. Customize the content, not the layout.
How often should I update it?
Every six months, when you have a new case study worth adding. Not before.
Where to go next
For related guides see Best CLI tools for developers in 2026, How to ship a SaaS in 30 days in 2026, and Best web hosting for developers in 2026.