Shipping Faster, Loading Faster: How I Expanded the Portfolio and Improved Mobile Performance

Six New Stories: Why I Expanded the Portfolio Beyond Just Screenshots
Yesterday I launched six detailed portfolio case studies that tell the full story behind each project. Here's why I moved beyond simple screenshots and what this means for anyone looking to work together.
The problem with "just screenshots"
For months, my portfolio was essentially a gallery. Nice images, short descriptions, but not much depth. If you were considering hiring me, you'd see what I built but not how I thought about it or why certain decisions mattered.
The feedback was consistent: "Great work, but I want to understand your process."
What I built instead
Portfolio pages that tell stories
Each project now has its own dedicated page with:
- The challenge: What problem needed solving?
- The approach: How I tackled it and why
- The results: What actually happened after launch
- Technical highlights: Key decisions that made the difference
Six case studies are now live: Blightfell (a game dev platform), Jorild.se (personal portfolio), Skyscraper (performance-focused site), Chronomation (automation platform), The Builder Coil (this very site), and Shipping API Dojo (API documentation platform).
A better reading experience
I created a consistent layout that makes it easy to scan:
- Hero section that immediately tells you what the project is about
- Sidebar navigation so you can jump to what matters most
- Image galleries that show the work in action, not just final screenshots
- Related projects so you can see how different work connects
Making it mobile-friendly
More people browse on phones than desktops, so I made sure:
- Text is readable without pinching and zooming
- Images load quickly and look sharp on all screens
- Navigation works smoothly with touch gestures
- Pages feel fast and responsive
Why this matters for potential clients
When you're evaluating someone for your project, you want to understand their thinking. These new portfolio pages show:
- Problem-solving approach: How do I break down complex challenges?
- Technical judgment: What trade-offs do I consider and why?
- Real-world impact: What happened after the work was delivered?
The results so far
- Richer storytelling: Each project now has context, not just pretty pictures
- Better mobile experience: Pages load quickly and are easy to navigate on any device
- Clearer value proposition: You can see exactly how I approach different types of challenges
What's coming next
- Replace some placeholder images with final project screenshots
- Add more case studies as new projects launch
- Continue refining the storytelling based on what visitors find most helpful
See for yourself
- Portfolio overview:
/portfolio - Individual case studies: Click "View Case Study" on any project
Built with care for anyone who wants to understand not just what I build, but how I think about building it.
Related Posts

Connecting the Dots: How I Built the Technologies Page and Tightened Performance
How I shipped the new Technologies page, wired services → technologies → portfolio links, and folded in the latest performance audit fixes for Ball Lightning.

Debugging TanStack Store: When Your React App Crashes Before It Renders
A TanStack Store implementation that looked correct, compiled without errors, and crashed spectacularly in the browser. The story of fixing `atom?.get is not a function` and learning to read documentation carefully.

The Client Quest: Facebook Posts, Cloudflare Redirects, and a Bash Script That Learned From Its Mistakes
A freelance client engagement told as an RPG quest — from planning in the tavern, to grabbing tools from the merchant, to a multi-day adventure of content, automation, and debugging. Plus: how this becomes a Chronomation workflow.