Guide
Government content strategy: modernizing legacy documents for digital services
Most government websites still treat content as files to store rather than services to run. This guide explains how to move from static documents to structured, accessible HTML, based on two modernization projects I led at the U.S. General Services Administration.
Why static documents fail the public
A PDF is a photograph of a decision. Once published, it is hard to search, hard to update, and often unreadable with assistive technology. When guidance lives in PDFs, people dig through dense files to find one answer, and content owners cannot fix errors without republishing an entire document.
Structured HTML solves these problems directly. Headings, lists, and tables make content scannable. Screen readers can navigate it. Search engines can index it. Content owners can update one section without touching the rest.
Conversion is not modernization
The most common mistake in a legacy migration is copying files from an old system to a new one and calling it done. That moves every existing problem to a new address.
On the HR Links project, a legacy server was being decommissioned while critical HR guidance sat in 125 aging, non-compliant files. A simple file move would have preserved the accessibility barriers and maintenance problems. Instead, we treated the deadline as a modernization opportunity: we converted priority files into accessible HTML, restructured dense guidance into task-based pages, and met Section 508 and WCAG requirements before launch.
Organize content around people, not offices
Legacy government sites usually mirror internal org charts. The public does not know your org chart, and should not need to. Effective government content strategy starts with the tasks people arrive to complete.
On the U.S. Open Government redesign, the legacy site had become a data graveyard: accountability information existed, but fragmented navigation and government-centered terminology buried it. We rebuilt the experience around a clear public path: topic, commitment, progress, evidence, participation. The redesigned site matched a full year of legacy traffic in 20 days, and the new Public Engagement page reached 78% engagement.
A phased approach that works under a fixed deadline
1. Inventory everything.
You cannot prioritize what you have not counted. A complete content inventory aligns stakeholders on what exists, who owns it, and what condition it is in.
2. Prioritize high-risk content first.
When time is short, convert the content people depend on most, and the content with the greatest compliance exposure, before anything else.
3. Treat accessibility as a starting requirement.
Section 508 and WCAG are not a final check. They shape the content model, the publishing standards, and the quality assurance process from day one.
4. Build reusable patterns, not one-off pages.
Templates and publishing standards let content owners maintain quality after launch, so the same problems do not return in the new system.
5. Plan governance before launch.
Review cycles, monitoring, and clear ownership keep the service accurate. A better page fixes today; governance protects tomorrow.
What the results look like
Across these two GSA projects, the modernization approach delivered measurable outcomes: $125K in annual cost avoidance on Open Government, a full year of legacy traffic matched in 20 days after launch, 125 legacy HR assets consolidated into accessible guidance, and engagement rates of 80 to 90% on the modernized HR Links pages.
The pattern is consistent: when government content is structured, accessible, and governed, people find what they need faster, and teams spend less maintaining it.