FUNDING PAGE DUPLICATE
DOMESTIC ASSISTANCE WRONG COPY
SERVICE AREAS CONFLICT
PROGRAMME NAMES STALE
A reconstruction from the content audit, not a picture of the old site.
CASE FILE / NDNS
Care,
made clear.
An ageing care website became a calm service system, a real enquiry path and a migration that protected the routes people already knew.
- Client
- Newcastle and District Nursing Service
- Fit
- Website, content system, migration
- Status
- Live
- Home
- Newcastle, NSW
BeforeContent drift, duplicate pages, legacy paths
AfterOne clear service system, live and findable
THE WOBBLE
A trusted organisation.
An untrustworthy structure.
NDNS had outgrown an ageing PowerSites website carrying duplicated content, conflicting service details, stale terminology and decades of legacy URLs. Replacing the homepage was the easy part. Moving people without breaking the paths they relied on was the real job.
ONE CONTENT SYSTEM
11 SERVICES8 PROGRAMMESNAVIGATIONSITEMAPENQUIRIESMETADATA
Shared lists now feed routes, cards, navigation and search information from the same source.
THE FIT
What changed,
materially.
The interface was only one layer. The stronger work happened underneath it: separating the content properly, protecting the migration and making an enquiry complete the journey.
- FRICTION
Services, funding programmes and organisational information had blurred together.
FITTED INTERVENTIONA new information architecture and reusable MDX content model.
RESULT19 service and programme detail pages with a clear place in the system.
- FRICTION
Known PowerSites paths had accumulated over years and could not simply disappear.
FITTED INTERVENTION50 path rules and 8 query-matched rules were mapped before cutover.
RESULT58 permanent redirects now carry known legacy URLs forward.
- FRICTION
A clearer site means little if the final enquiry vanishes into the void.
FITTED INTERVENTIONValidated email delivery with honeypot, origin and rate-limit protection.
RESULTA real enquiry path, tested as part of the live release.
HOW WE MADE IT
Find the wobble.
Then make the system.
The making left a trail. Evidence from the project record shows how the build moved from content archaeology to a protected live cutover.
- AUDIT
Content archaeology
Crawl the old site, inventory its routes and find the duplicated, stale or contradictory material.
- RECONCILE
Turn uncertainty into questions
Put every unclear service, funding, contact and accreditation claim into one reviewable QA list.
- PROTECT
Map the move
Preserve canonical intent, map known paths and plan a cutover that leaves mail and DNS undisturbed.
- OBSERVE
Sweep it live
Check every public route after launch, then correct stale government references and broken links found in the field.
RUNNING SWEET
Proof, without
the theatre.
These are release facts, not invented uplift figures. Traffic, conversion and enquiry-volume comparisons were not available, so we do not pretend otherwise.
- 32
- Live sitemap routes
- 19
- Service and programme detail pages
- 58
- Permanent redirect rules
- 0
- Broken images in the dated full-route sweep
DECISION LEDGERWHY IT MATTERED
Content in MDX, not a traditional CMS
The content needed structure and version control more than another general-purpose editing surface.
Known legacy paths mapped explicitly
A redesign should not ask referrers and returning visitors to relearn how to find care.
Enquiry delivery treated as infrastructure
Validation, spam protection and failure handling were part of the build, not an afterthought.
HANDOVER
Put it in
their hands.
- CONTENT
- Structured source files and shared route lists
- OWNED
- OPERATIONS
- Launch runbook and post-launch review record
- DOCUMENTED
- DELIVERY
- Production deployment with tested enquiry email
- LIVE
- ACCESS
- Code and project history retained in the repository
- PORTABLE
