The outcome
A surprising amount of routine member contact is, at its core, a search problem. The member couldn’t find the form they needed, so they emailed. They couldn’t find the answer to a procedural question, so they called. They couldn’t tell whether the page they were reading was current, so they rang to check.
Most associations have the content. They’ve written the policies, the guides, the procedure pages, the FAQs, the technical updates. They’ve published the events calendar, the resource library, the speaker bios. The content exists. The problem is that it’s organised the way a content team thinks about content, not the way a member searches for what they need.
The outcome here is a website that does for member self-service what a well-tuned search engine does for the open web. The member types what they’re trying to do. They get the right page. The page tells them what they need, with the form or the action they can take embedded in it. The phone doesn’t ring because the answer was already there.
This is the unsexy outcome that quietly removes a measurable chunk of routine contact. It works because content is structured properly, taxonomy is consistent, search is indexed cleanly, and the platform supports the team in keeping it all current.
What discoverability looks like to the member
The member arrives on the website. They use the site search, and the search works. Results are ranked by relevance, not just chronologically. Filters narrow the results in useful ways: by topic, by audience, by date, by type of resource. The member can find a guide to the renewal process, a recording of last month’s webinar, the policy on a particular procedural matter, the chapter event in their state, all from the same search box.
When they land on a page, the page is current. There’s no “Last updated 2019” notice on a page about a 2024 process. The cross-references go to live pages, not 404s. The forms link to fillable, modern forms, not PDFs requiring a printer.
The mobile experience is the same as the desktop experience. The page loads quickly. The content is structured, with clear headings, scannable layout, and the action the member needs is where they expect it.
What discoverability looks like to the team
The communications and content team has the tools to keep the site useful. Adding a new resource takes minutes, not hours. Updating an existing piece of content propagates everywhere it’s referenced. The metadata required for government accessibility and search engine optimisation is captured at the point of publishing, not as a remediation project years later.
The development team isn’t blocked behind a queue of small content requests. The platform supports the content team enough that can you add a banner to the events page doesn’t require a developer. Custom widgets cover the recurring content patterns: image galleries, calls to action, forms, structured listings.
Search performance is monitored, queries that return no results are visible, and the team can spot content gaps as they emerge. The content roadmap is informed by what members are looking for, not just by what someone in the team thinks should be written.
Why this was hard before, and why it isn’t now
Old CMS platforms were good at displaying content and bad at making it findable. Search was an afterthought, often a bolt-on that returned poor results. Metadata was optional and rarely captured. Content reuse was discouraged by the architecture, so the same information ended up duplicated in three places, three different versions, none of them obviously canonical.
What’s changed is that modern content platforms are built around structured content from the start. Define a content type once, capture metadata at the point of authoring, and the same content can be reused across many contexts, with search and SEO handled natively. Specialist search platforms like Funnelback can be layered on top for sites where search performance is genuinely critical. The integration patterns between CMS, AMS, and search are now reusable rather than one-off.
The other change is that mobile and accessibility expectations have caught up with reality. A site that doesn’t work on a phone, or a site that fails accessibility audits, no longer slides through. The platforms that survived are the ones that take both seriously, and the result is a member experience that’s better in every browser on every device.
The proof: associations running this outcome with 3DN
Queensland Law Society, the high-performance search story
QLS arrived with a CMS that was difficult to manage and at end-of-life on an unsupported platform. Beyond migrating to a current platform, they wanted easier and quicker content management, government-mandated metadata, a new design, and continued use of their investment in Funnelback search.
3DN implemented Kentico 12 with an MVC architecture that supported integration to existing business systems while accommodating planned new ones. A series of custom widgets covered flexible and dynamic content layouts. Custom development integrated the Funnelback search system that QLS already had. The result is a high-performing site with extensive metadata management, supporting both government compliance and improved search engine optimisation. The team can build new layouts with more than a dozen custom widgets. The on-site search is, in QLS’s own description, second to none for performance and flexibility.
Royal Australian College of General Practitioners, content that scales with a large team
RACGP supports a large internal team delivering online services to a large member base. Change moves fast. The College needed a website that could keep up. Moving from an all-in-one iMIS solution to Kentico, with 3DN’s integration suite, gave the team a best-of-breed CMS where structured content, robust integration, and strong content management worked together. The site’s ability to scale across the College’s online services has been the strategic outcome; member-facing discoverability has been the daily one.
Australian Dental Association, structured content driving multiple member-facing experiences
ADA’s Kentico platform supports the main site, the CPD self-management portal, the congress microsite, and other member-facing experiences. The structured content approach is what makes that range of experiences manageable by the same team. A piece of content can appear in multiple contexts without being duplicated, and a change in the source updates everywhere.
Kentico | iMIS Synchronisation Bridge, content that follows the AMS
The Synchronisation Bridge means that content driven by AMS data, events, courses, member directory entries, is structured Kentico content with full search optimisation. Every event is fully indexed, every course is discoverable, every member-relevant page benefits from native CMS search and SEO. More page views, more registrants, more revenue.
Where this outcome applies
Every association running a content-rich website. The urgency is highest where:
- The website carries a heavy regulatory or governance load (member directories, public registers, statutory information)
- Member self-service depends on finding the right form or guide
- The content team is small relative to the volume of content
- Search engine traffic is a meaningful source of new member enquiries
- The site has accumulated years of content across multiple platforms and migrations
Related work and tools
The Queensland Law Society is the flagship proof point for high-performance search, with a Kentico-and-Funnelback combination that delivers both content management ease and on-site search the team describes as second to none. The Royal Australian College of General Practitioners shows how structured content scales across a large internal team and a large member base. The Australian Dental Association demonstrates how a single Kentico platform can drive multiple member-facing experiences (main site, CPD portal, congress microsite) without content drift. The Kentico/iMIS Synchronisation Bridge is the structured-content pattern that drives discoverability for AMS-derived content like events, courses, and member directory entries.
The tools that supported this outcome were Kentico as the CMS underpinning structured content, custom widgets, and native search, Funnelback as the specialist search platform where on-site search performance is critical, iMIS as the AMS providing data that drives dynamic content, the 3DN integration toolkit as the connective layer, and accessibility and SEO tooling as the modern web table stakes that no longer get to be optional. A discoverable website is the result of the design, structured content authored once and reused well, more than any specific tool.
