A personal page for developers
A developer page should answer what you build, how well, and where the proof lives: shipped products, open source, writing. It's the page your GitHub, résumé and LinkedIn all point to.
What your page should include
- What you build and the stack you're strongest in, in one sentence
- Two to four projects with links to code or live product
- Impact numbers: latency cut, users served, revenue shipped
- Open-source contributions and writing
- Availability: open to roles, contracts or neither
Sections that work
Projects → Experience → Open source → Writing → Contact
Looks to start from
Ink or a mono-type look: dense, readable, fast. Ivo can restyle any of them to your colours.
Questions
Is GitHub enough as a developer portfolio?
GitHub shows code; it rarely shows impact. A short page that explains what each project did and links to the repo gets read by recruiters who don't read code.
Should I list every technology I know?
No. List what you'd want to be hired for. Long skill lists read as filler.