Case studies

NSW Digital Design System

The NSW Digital Design System documentation site, rebuilt on Inka. Every component page is authored in the editor and rendered by a Next.js frontend built on the design system's own markup, and checked against the design system's own examples.

It is being rolled out to several NSW Government sites.

Why it is a good fit

The biggest wins are security and ease of maintenance, without giving up a good editing experience.

• Smaller attack surface. The public site is a separate frontend. The CMS and its editing interface do not serve the pages visitors see, so what faces the public is a small, focused application rather than the whole content management system.
• Easier to maintain. The frontend is independent code: the CMS can be upgraded without rewriting the site, and the site can change without touching the CMS.
• A good editing experience. Editors work visually on the real pages, with the design system's components, and the design system's rules decide what can go where — so there is no off-system output to find and fix after publishing.

Coming soon

Demos for two more design systems, in the coming weeks:

• UK GOV.UK Design System — the GDS components and patterns as an Inka frontend.
• NHS Design System — the NHS digital service manual's components as an Inka frontend.