Case study · Civic tech · public-service portals

Governo do Distrito Federal (GDF)

Engineering of an expansive mobile-first ecosystem comprising dozens of civic landing pages and public service portals (Healthcare, Public Transit / Vai de Graça, SUS Re-registration). Frontend architecture focused on semantic HTML, fast mobile loading, and strict accessibility compliance for the Federal District population.

Status
In use
Context
Governo do Distrito Federal (GDF)
My Role
Tech Lead & Frontend Engineer
Stack
Semantic HTML5, Tailwind CSS, mobile-first, web performance
Core Focus
Mobile UX, Accessibility & Scale
Three public-health and mobility campaign pages for the Federal District government.
[Re-capture at 2× — the current source is 901 px wide]

The challenge

There was no problem to fix here: this is creative and design work. The challenge was the process — using AI to turn slow production into fast production. Each landing page used to take two days; now it takes two hours when the mobile layout already exists. Without it, the time depends on what has to change.

Key Engineering Decisions

Citizen-Centric Mobile-First Architecture

Responsive layouts engineered and thoroughly validated for real smartphone usage across all device tiers, featuring clear typography and zero-friction navigation for diverse age demographics.

Semantic HTML & Civic Accessibility

Semantic structuring in strict compliance with e-MAG and WCAG accessibility standards, ensuring full screen-reader compatibility and high-contrast legibility under direct sunlight.

Performance & Minimal Data Consumption

Lightweight markup, modular CSS and aggressive asset optimization delivering near-instant loading times even on unstable 3G/4G mobile connections.

Continuous Delivery Governance (2025–2026)

Systematic technical delivery reporting, upholding rigorous design consistency and code quality across 20 to 30+ thematic public portals over multiple cycles.

Results

32pages published in 2025, hand-coded in HTML and CSS
25pages in 2026 through September, with AI agents in production
2 hper landing page with AI, once the mobile layout exists — it used to take two days

What still needs a human eye is adapting images and layout to mobile.

Stack

Semantic HTML5Tailwind CSSmobile-firstweb performance