IronLife

IronLife is a fitness blog CMS on Webflow (live staging: ironlife-org.webflow.io). This page is here for honesty, not for padding the engineering portfolio.

Who did what: collaborator Milan (Webflow developer) built and developed the site. I did not ship the Webflow build. My role was content — drafting fitness/SEO articles with AI assistance, then editing and publishing them through the CMS.

Not a SaaS client case study. Not related to a separate physical product chapter with the same brand name. Included so visitors see the full timeline without pretending this was a solo full-stack ship.

The brief for the site was a fitness content property: CMS-driven articles, structure for ongoing publishing, and a clean Webflow front end someone else owned in Designer/Editor.

I already knew enough Webflow to navigate the CMS and publish — I don't sell Webflow builds as a service. Pairing with Milan meant the build stayed with a Webflow specialist while I focused on the part I actually owned: words, structure, and editorial consistency.

Role clarity. Marketing-friendly portfolios love to flatten “worked on a Webflow site” into “I built it.” That fails the second someone asks who owns the Webflow project.

AI-assisted draft quality. Raw AI drafts are generic. Fitness and SEO content still needed human cuts: claims, structure, readability, and CMS formatting.

CMS discipline. Publishing through someone else’s build means respecting their collection schema, SEO fields, and layout constraints instead of redesigning mid-stream.

Pipeline: AI-assisted first drafts → heavy human edit → CMS publish (titles, slugs, meta, body formatting, internal linking where the schema allowed).

Stack on my side: Webflow CMS editor + editorial workflow — not Designer-owned builds, custom code embeds as “my deliverable,” or client Webflow retainers.

Stack I did not own: Webflow site architecture, Designer work, and ongoing site development — Milan’s lane.

A live (staging) fitness blog CMS with a published content stream I wrote and edited. No invented traffic, conversion, or Lighthouse claims here — those aren’t the point of this page.

The useful outcome for me: sharper CMS editorial habits, clearer boundaries on collaborator work, and practice shipping content without claiming a build I didn’t do.

If you need a Webflow site build, that’s not the service I sell. If you need full-stack SaaS / Flutter / React shipping, look at Callidus, BookBed, Pizzeria Bestek, Relocate, and the FlutterFlow Marketplace line.

IronLife stays on this site as a content collaboration footnote with a live URL — useful context, correctly labeled.