Plan your implementation approach
Start by selecting the template structure that best matches your service journey. The NSW Design System is most effective when teams map component choices to user needs, rather than assembling pages from isolated UI elements.
For content-heavy pages, a left sidebar can improve wayfinding by keeping section navigation visible while users scan long guidance and policy material.
During implementation, keep headings explicit and task-oriented so users can quickly understand page structure and share direct links to relevant sections.
Use existing anchors for stable references
Where headings already include an ID, those anchors should be preserved to avoid breaking shared links in support documentation, onboarding guides and service manuals.
This is especially important for agencies that publish release notes or operational runbooks that are referenced across multiple teams.
Verify that copied links always resolve to the authored anchor and continue working after future content updates.
Generate anchors when none are provided
When an ID is missing, the heading-link script can generate one automatically so teams still get shareable section links without additional authoring overhead.
Generated IDs should remain readable and unique, even when headings have similar names, to support reliable linking and analytics tracking.
This approach reduces manual content maintenance while keeping user-facing behavior consistent across templates.
Apply guidance in a right sidebar layout
A right sidebar works well when the main content flow should remain dominant and supplementary tools, references or actions sit alongside as secondary information.
Use this pattern for implementation pages that combine narrative guidance with quick links, examples or downloadable assets.
Heading-link behavior should remain predictable here, regardless of how the content column width changes across breakpoints.
Maintain reliable deep links
Persistent anchors support collaboration between design, content and engineering teams by allowing precise references to implementation decisions.
This is useful in backlog tickets, design QA notes and service readiness checklists where teams need to point to exact sections.
Confirm copied links consistently return users to the intended heading after refresh, navigation and sharing.
Support scalable content operations
As teams extend the NSW Design System into more services, automatic heading anchors help keep content discoverable and easier to reference in delivery workflows.
Collision-safe generated IDs are essential when pages grow over time and headings are reordered, renamed or duplicated during iteration.
Test this section on desktop, tablet and mobile to ensure icon visibility, tooltip feedback and copy actions remain clear for all users.
Teams can pair implementation notes with visual examples to speed up review and maintain consistency across agency services.