What Building My Own Portfolio Site Taught Me About Shipping

Starting with the admin panel, not the homepage

The first real decision was building the Filament admin panel before polishing a single public page. Every piece of content — profile, skills, projects, blog — needed to be editable without touching code, so getting that right early saved a lot of rework later.

Content before layout

It's tempting to design a homepage around placeholder text and swap in the real content later. I did the opposite: real skills, real career history, and a real bio went in first, and the layout was built around what that content actually needed to say.

Adding the AI assistant

The chatbot in the corner of this site is trained on the site's own content — profile, skills, projects, blog — so a visitor can ask a direct question instead of reading through every section themselves. It's a small feature, but it changed how I thought about the rest of the content: writing for both a human reader and something that summarizes it.

Why 50 free tools

The free tools started as a handful of SEO utilities I already used constantly, then grew into 50 once I built a shared engine for the simpler text-transform tools instead of hand-building each one from scratch. A visitor gets something useful even if they never read the rest of the site.

The actual lesson

Shipping a real site, even a portfolio, surfaces problems that a mockup never does — data loss, deployment quirks, content that doesn't hold up once it's live. Building this one end to end was as much a lesson in maintaining a real application as it was in presenting my work.