Public HARTMANN website, shown for company context. The internal product described in this case is not shown.

Public HARTMANN website, shown for company context. The internal product described in this case is not shown.

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.

01Problem

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.

02Selected contributions

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

03System context

Next.js components, authored in TypeScript with LESS and BEM, are bound to Sitecore XM Cloud so editors compose pages from configured blocks. Azure DevOps is the delivery path.

  • Next.js componentsMy scopeBound to CMS blocks editors composeSitecore XM Cloud

My scope in the system: Next.js components

Delivery

  • Azure DevOpsDelivery pipeline

Separate from the runtime flow. These are not connected to each other.

Implementation tools

TypeScript · LESS · BEM. Not runtime services.

04Scale & 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

05Outcome

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

06Stack

  • 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

Related services