HARTMANN
Healthcare experience platform
Senior Frontend Developer · Design System
CMS-driven Next.js component set for PAUL HARTMANN, bound to Sitecore XM Cloud so editors can compose healthcare pages without a new engineering pass for every layout.
01What I built
Built and maintained reusable Next.js components for HARTMANN’s XM Cloud frontend: TypeScript UI, LESS/BEM, and CMS bindings so editors could configure layouts from existing building blocks. Helped sequence the backlog by effort versus impact, and worked with product and design so new composition stayed inside the design system.
- Reusable Next.js components compatible with Sitecore XM Cloud
- LESS / BEM implementation inside the design system
- Editor-facing configuration so new layouts did not require a dedicated build
- Backlog sequencing with product and design
02Engineering proof
- Editor-configurable components on Sitecore XM Cloud
- LESS and BEM inside an existing design system
- Layouts composed in the CMS instead of per-page builds
04Problem
Editors needed to assemble healthcare pages without opening an engineering ticket for every layout. Components had to stay inside the design system and remain compatible with Sitecore XM Cloud.
05Scale & constraints
- Sitecore XM Cloud as the CMS
- Next.js frontend with LESS and BEM
- Components had to be configurable by editors, not only by engineers
- Azure DevOps as the delivery path
06Outcome
Editors can compose new layouts from a CMS-driven component set without a dedicated engineering ticket for each page. No public engagement or page-count metrics are published.
- Reusable frontend components for CMS-driven page composition
- Design-system consistency across Sitecore-driven layouts
07Stack
- Next.js
- TypeScript
- LESS
- BEM
- Sitecore XM Cloud
- Azure DevOps
No verified public metrics are published for this engagement.
Categories: Design System, Frontend
Year: 2026