News System Architecture, Content Governance & Scalable Publishing

Overview

The Workers’ Compensation Board website requires timely, accurate communication across multiple program areas. News content was previously difficult to manage, lacked consistent structure, and required repetitive manual updates across numerous pages.

To address these challenges, I designed and implemented a centralized, scalable news publishing system that streamlined content management, improved organization, and reduced maintenance effort across the site.

The solution combined HTML, CSS, JavaScript, reusable include architecture, and dynamic filtering logic to support scalable publishing while improving usability, governance, and long-term maintainability.


Challenge

The existing news structure presented several operational and usability challenges:

  • No clear separation of news by audience or program area
  • Duplicate content updates required across multiple pages
  • Inconsistent structure between landing pages and archive pages
  • No automated system for:
    • Latest vs archived content
    • Section-based filtering
    • Year-based navigation
  • High risk of outdated or miscategorized information
  • Manual publishing workflows that did not scale efficiently

Goals

  • Create a centralized publishing system for all news content
  • Eliminate duplicate updates across pages
  • Improve content governance and organization
  • Support audience-specific news experiences
  • Automate archive management and filtering behavior
  • Improve usability and content discoverability
  • Build a scalable framework for future growth

Approach

1. Content Audit & Information Architecture

Initiated a full audit and restructuring of all existing news content.

Partnered closely with the Public Information Office (PIO) and stakeholders to:

  • Review and categorize legacy news items
  • Evaluate content relevance and organization
  • Establish audience- and program-based section groupings
  • Validate content placement and ownership

This process established a clear and sustainable information architecture for ongoing news publishing.

2. Section-Based Archive Structure

Designed and implemented dedicated archive pages for each section and program area.

This structure:

  • Improved audience segmentation
  • Increased content discoverability
  • Created a scalable framework for long-term publishing
  • Standardized archive behavior across the site

The archive system provided a more intuitive experience for users while simplifying ongoing content management.

3. Centralized Content Management via Includes

To eliminate duplication and improve maintainability, I implemented reusable include architecture for all news content.

Landing Page Include

Created a centralized include containing news items for multiple landing pages and program sections.

Each news item was assigned HTML/CSS labels identifying:

  • The landing page section where it should appear
  • The related archive section
  • Content categorization and routing behavior

This allowed:

  • A single update to automatically propagate across multiple pages
  • Consistent content management from one centralized source
  • Reduced duplication and maintenance effort

Landing pages display:

  • The 3 most recent items for each section
  • Section-specific content dynamically filtered from the centralized include
Archive Include

Created a separate archive include containing all archived news items across sections.

Like the landing page include, archive items were labeled by section and routing behavior, allowing:

  • Dynamic filtering by archive category
  • Automated organization across section-specific archive pages
  • Scalable long-term archive management

This structure established a centralized single source of truth for both current and archived news publishing.

4. Dynamic Filtering & Automation

Developed a dynamic filtering system using JavaScript, HTML, and CSS labeling to automate content routing and display behavior.

The system:

  • Routes content to the correct section pages
  • Controls visibility between:
    • Landing pages
    • Archive pages
  • Automatically transitions older content into archive structures
  • Reduces manual sorting and publishing errors

This created a scalable publishing workflow that significantly improved maintenance efficiency.

5. Intelligent Archive Navigation

Designed and implemented a dynamic left navigation system for archive pages.

Features
  • Displays years conditionally based on available content
  • Automatically updates as new content is added
  • Built as a reusable include across archive pages
  • Supports scalable long-term archive management

This improved both:

  • User navigation
  • Administrative maintainability

while reducing the need for manual archive restructuring.

6. Implementation, Testing & Approval

After development, implemented and validated the system across all related pages and sections.

Responsibilities Included
  • Implementing includes and filtering logic
  • Conducting QA and cross-page validation
  • Coordinating structured review and approval workflows with PIO and stakeholders
  • Validating:
    • Content accuracy
    • Section ownership
    • Accessibility
    • Usability

This ensured publishing consistency and stakeholder alignment before launch.

Accessibility & Usability Considerations

Implemented accessibility and usability improvements throughout the system design.

Accessibility Enhancements
  • Maintained semantic heading and content structure
  • Ensured predictable keyboard navigation patterns
  • Supported screen reader usability
  • Improved navigation clarity and consistency
Usability Improvements
  • Reduced cognitive load through clearer content grouping
  • Improved discoverability of both current and archived content
  • Created more intuitive archive navigation and browsing experiences

Results

  • Established a centralized publishing system for all news content
  • Eliminated duplicate updates across 20+ pages
  • Reduced risk of outdated or inconsistent information
  • Improved governance and ownership clarity
  • Automated content lifecycle management (latest → archive)
  • Improved usability and content discoverability
  • Created a scalable publishing framework for future growth
  • Reduced maintenance overhead through reusable includes and automated filtering

My Role

Lead on information architecture, content governance, front-end implementation, and publishing workflow design.

Responsibilities included:

  • Leading content audit and restructuring efforts
  • Designing scalable archive and publishing architecture
  • Developing reusable includes and filtering logic using HTML, CSS, and JavaScript
  • Coordinating with PIO and stakeholders throughout implementation
  • Managing QA, testing, and publishing validation
  • Ensuring accessibility and usability standards were maintained
  • Supporting long-term scalability and governance processes

Tools & Technologies

  • HTML5
  • CSS3
  • JavaScript
  • JSP-based include architecture
  • Dreamweaver
  • Siteimprove
  • Google Analytics 4
  • Accessibility testing tools:
    • NVDA
    • WAVE
    • Keyboard-only testing

Key Takeaways

Large-scale publishing systems require scalable architecture, structured governance, and automated workflows to support long-term maintainability.

This project demonstrates my ability to:

  • Design scalable content systems within complex enterprise environments
  • Combine information architecture with front-end development and automation
  • Improve governance and operational efficiency through reusable publishing structures
  • Translate business and stakeholder needs into maintainable, user-centered technical solutions
  • Lead projects from audit and strategy through implementation, QA, and launch