Case study / Flowable
Rebuilding
the foundation.
I independently own Flowable’s marketing website from architecture and implementation through testing, releases, and maintenance—while partnering with design and marketing to keep the platform moving.
- Role
- Sole engineer and technical owner
- Stack
- Next.js, TypeScript, Contentful, Radix UI, Storybook
- Scope
- Architecture, delivery, quality, and technical health
The work
A live site,
not a blank slate.
Flowable’s website supports an active marketing team and a steady publishing workflow. Improvements need to strengthen the technical foundation without getting in the way of campaigns, content updates, or visitors.
I led the migration from Next.js Pages Router to App Router, redefining routing, rendering, and data-fetching patterns beneath the existing experience. Contentful-managed pages and publishing workflows remained intact, so the team could keep shipping content throughout the transition.
Design system
One system,
100+ pages.
I own and evolve a library of 35 CMS-driven React components. Built on Radix UI and compound component composition, the system gives editors flexible page-building options without trading away consistency or accessibility.
Working from Figma, I extended that system to implement Flowable’s rebrand across more than 100 published pages. Variants and states are documented in Storybook, giving design and development a shared place to review components before they reach the live website.
Motion and CSS add transitions, scroll-driven effects, and focused micro-interactions where they clarify hierarchy or provide feedback, not simply as decoration.
Performance and quality
Easier to find.
Faster to use.
I raised mobile Lighthouse performance on key production pages from 45-50 to 85-90 by improving Next.js rendering, image delivery, font loading, and the amount of client-side JavaScript shipped to visitors.
The work continues beyond headline scores. I maintain the website’s accessibility, technical SEO, dependencies, and Cypress coverage for critical user journeys so routine changes remain safe to release.
Component system
35 CMS-driven components
Rebrand reach
100+ published pages
Mobile performance
Near-90 Lighthouse score
Ownership
Architecture to release
Technical scope