Upgrading my portfolio
· 3 min read
For a long time my website was a single page. It had my name, one sentence about me, and four cards that linked to LinkedIn, my resume, GitHub and my email. It loaded fast and it told you almost nothing. It is still up at v1.ehtishamsajjad.com if you want to compare.
That was fine when I only needed a place to point people. It stopped being fine when the things I wanted to show no longer fit behind four links: products I lead, a course I wrote, talks, and posts like this one.
What I wanted from version two
Three kinds of people land on this site: someone with a project, someone hiring, and someone who wants to learn. I wanted each of them to find their part within one scroll. I also wanted the site to look like it belongs to an engineer, without dressing up as a terminal.
The design
The layout is borrowed from a notebook. A rule runs down the page, labels sit in the margin, and the content sits to the right. As you scroll, the rule inks in and a small square rides its tip.
What is on it now
- Work covers the products I have built and led, each with its own page and photos.
- Writing is where posts like this one live, with an RSS feed if you prefer a reader.
- Community collects the teaching, talks and workshops, from training trainers in the TVET programme to an episode of the Scrimba Podcast.
- About has the longer story, a timeline of where I have worked, and a coffee cup that tells you a few things about me that are not work.
- Resume is a proper page now, with the PDF still a click away.
- Away is for the days I was not at a desk, with a chart of how far each trip was from Islamabad.
- Gaming is what happens when the laptop closes.
- Contact has a form that lands in my inbox, and you can book a 30 minute call without leaving the page.
Small things to play with
The home page has two small games and a race that replays a dev server going from two minutes to three seconds. Under every post there is a coffee cup you can fill, and the count beside it is every reader’s pours added together. The gaming page has a controller that follows your pointer.
The build
- Astro renders every page to static HTML. Work, writing and community entries are Markdown files in content collections.
- Tailwind handles layout, with a small set of colour tokens that both themes share.
- Cloudflare Workers serves the site. Only two routes run code on a request: the contact form, which sends email through Resend, and the coffee cup, which keeps its count in a D1 database. Both are rate limited.
- Page transitions use the browser’s native View Transitions, so there is no client-side router.
- Images are resized and converted to WebP at build time.
- Deploys happen on every push to GitHub, and the footer shows which commit is live.
Almost everything works without JavaScript. The scripts that do ship are small and each has one job: the theme toggle, the chart race, the games, the coffee cup and the booking popup.
What I kept from version one
The old redirects still work, so links on my resume and LinkedIn did not break. The speed stayed too. A portfolio that makes you wait is a bad argument for hiring the person who built it.
What is next
More writing. If there is something you would like me to cover, tell me.