← Notes

Why I am Rebuilding akkiipc.com in Public

My portfolio used to live on Framer. The new akkiipc.com is offline-first HTML and CSS, shipped in four phases. Notes on why I switched and what each phase is meant to prove.

Building 4 min read

For almost a decade, I wanted to build akkiipc.com.

The idea was always there. The time, skills, and confidence to build it properly weren't.

Along the way, I experimented with different tools, including Framer. I genuinely enjoyed using it. It helped me understand what I wanted from a personal website, but I kept feeling like something was missing. I wanted more control over the structure, content, and the way the site would evolve over time.

So this version is being built differently.

The foundation is plain HTML and CSS, with a thin Astro layer on top, deployed through Cloudflare Pages and Workers. Nothing particularly fancy. The goal isn't complexity. The goal is ownership.

I'm building it in public and shipping it in phases.

  • Phase 1: The Foundation -
    An admin system and content schema. One place to manage project data. One source of truth.

  • Phase 2: The Portfolio -
    The public-facing site. Home page, project grid, and project pages, all powered by the same content store.

  • Phase 3: Machine Readability -
    Automation and AI feeds. Files like ai.json and llms.txt update automatically on every publish so the site remains readable to both traditional search engines and modern AI crawlers.

  • Phase 4: Polish -
    Dark mode, accessibility, performance improvements, deployment workflows, and all the small details that make a site feel finished. The "ready for the world" pass.

  • Phase 5: The Living Layer -
    Notes, Now, and Library. A place to share what I'm thinking about, working on, and learning in real time. Not polished case studies or portfolio pieces. Just a more honest record of the process behind the work.

Every phase ends with something usable. Something I can send to a recruiter, client, collaborator, or friend. No half-finished experiments hidden away in a folder.

The bigger idea is that a personal website shouldn't be a static résumé that gets updated twice a year. It should be a living professional profile. One that grows alongside the person behind it, remains readable to humans, and is structured well enough for machines to understand too.

After almost ten years of thinking about it, I'm finally building the version I always wanted.