This was a newsletter publication and distribution system for Aboriginal Human Resources Development Canada (AHRDC), built in 2003. The interesting part isn’t the technology — it’s that the system existed at all, in an era when most federal departments either didn’t communicate this way at all or sent printed bulletins through the post.
The problem
The listserv and email-management toolset that served Fortune 500 corporate communications departments in 2003 was not built for the intake AHRDC’s program actually needed. Federal departments were not going to send citizen-facing email through a hosted commercial service, and the enterprise alternatives that did exist were priced and shaped for marketing departments, not for a federal program office with a budget and a mandate. The people writing AHRDC’s newsletters were civil servants — communications staff, program officers — not web developers.
So the question for the build was straightforward: how do you give the people who know the program enough self-serve publishing power that they don’t need a developer in the loop every time they have something to say?
The build
The platform was Classic ASP running against a Microsoft Access® back-end, with direct SMTP delivery and no third-party email service in the chain. Civil-service staff could compose a newsletter once, in both plain-text and HTML format. The system would then do two things with each issue: publish a version on the AHRDC website so a citizen who landed there months later could read the archive, and dispatch the email version directly to the subscriber list.
Public subscribers signed up and unsubscribed through the website themselves. The communications team got an editorial loop they could run without a developer’s involvement, and the department got an archive of its own outbound communications it didn’t have to maintain separately.
Self-serve publishing as the actual deliverable
Hosted email-marketing services have made this kind of system commodity infrastructure now. In 2026 the same build starts on top of a hosted service or a WordPress plugin and never writes a line of SMTP code. The underlying design lesson hasn’t aged. AHRDC’s communications team could publish without calling a developer first, and that’s still the standard I hold a WordPress build to when a non-developer team has to maintain it.
