Modernization concept for state.gov: a component-based design system, a radically lighter tag/script footprint, a contained REST API, and Section 508 accessibility — built on the CloudFront delivery the site already has.
Speculative concept — prepared independently by Offlabel, LLC. Not affiliated with the U.S. Government.
The Brief
state.gov is the flagship digital presence of U.S. diplomacy: newsroom, press briefings, travel advisories, the A–Z countries directory, and policy content.
It is WordPress on Apache behind CloudFront — fast delivery, but a heavy page payload and a sprawling third-party script estate.
The concept modernizes the experience without disrupting the publishing workflow that State staff rely on.
Audit Findings
WordPress on Apache with a custom "state" theme; delivered through CloudFront CDN + HTTP/2 (a solid baseline).
The full WordPress REST API is publicly exposed at /wp-json/ — a large attack surface and an SEO/performance liability.
Plugin & tag sprawl: Complianz, Gravity Forms, TablePress, Total Survey Pro, plus GTM, Google Analytics, DAP (Digital Analytics Program), ForeSee CX, Brightcove video, GovDelivery, Convert experiments, and Google Ads.
Heavy payload — the homepage HTML alone is ~250KB, before images and scripts.
Section 508 federal accessibility obligation (WCAG-based) applies site-wide.
Search rides on Search.gov — the mandated federal search service.
Approach
Rebuild the presentation layer as a documented component library (design tokens + Storybook) on top of the existing publishing workflow.
Consolidate analytics and tags into a single stack (GTM + GA + DAP), removing redundant pixels.
Restrict the REST API to authenticated/admin contexts; publish read-only content via a controlled layer.
Lead with Section 508 / WCAG 2.2 AA compliance, tested automatically.
Introduce WebP/AVIF responsive images and static-friendly rendering on the existing CloudFront edge.