Case study / Flowable

Rebuilding
the foundation.

As the sole frontend developer responsible for Flowable’s company website, I drive its development, maintenance, and technical evolution as part of the marketing team.

Role
Sole website frontend developer
Stack
Next.js, TypeScript, Tailwind CSS, Storybook, CMS
Scope
Architecture, design system, discoverability, performance

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 migrated the website from Next.js Pages Router to App Router, modernizing the routing architecture beneath the existing marketing experience. The work created a stronger base for ongoing improvements while keeping the CMS central to how the team publishes.

Design collaboration

A rebrand,
built together.

The website is also undergoing a rebrand. I work closely with the designer to translate the evolving visual direction into reusable, production-ready components.

Storybook gives us a shared place to build, document, and review interface components in isolation before they become part of the live website.

Beyond migration

Easier to find.
Faster to use.

My ongoing work covers technical SEO and generative engine optimization, making content easier for search engines and AI-assisted discovery tools to understand and surface.

Performance is part of the same job: reducing friction for visitors while keeping the implementation practical for the people who maintain and publish the site.

Internal implementation details and company metrics are intentionally kept private.

Focus areas

Pages Router to App Router migration

Rebrand implementation

Component development in Storybook

Technical SEO and GEO

Web performance

CMS-driven publishing