FOR CITIES, COUNTIES & PUBLIC AGENCIES

Local government websites.
Built around the people
who use them.

Design and redesign for cities, counties and public agencies: clearer paths for residents, practical editing for staff and a defined plan for content, testing and handoff.

COMPLETED INDEPENDENT WORK

See the websites.
Explore the live work.

Independent portfolio projects, not government-commissioned client work. Screenshots show the sites as captured on October 7, 2026.

Also explore Midland Odessa Now (opens in a new tab), an independent community-information project.

DESIGN & REDESIGN

Start with what residents
need to do.

A local government website should help someone find a service, understand a requirement or reach the right department. A redesign begins by reviewing those paths with your staff: paying a bill, finding a meeting agenda, reporting a concern, checking office hours or learning how to apply for a permit.

We plan navigation, page templates and content around those tasks. Clear department ownership, readable mobile layouts and useful links matter alongside the visual design. A new site or a redesign can be a standalone project or part of a broader system with staff portals, resident requests and departmental workflows.

A WEBSITE YOUR TEAM CAN MANAGE

Make editing and approvals practical.

CMS & staff editing

Choose a content management approach around the staff who will use it, your existing technology and the publishing tasks involved. Agree on templates, editing permissions and the review steps for routine updates, urgent notices and departmental pages.

Migration with a content plan

Inventory pages, documents and important URLs before moving them. Decide what to keep, rewrite, archive or remove with the responsible departments. Plan redirects and check migrated links, dates, document labels and search behavior before release.

Use the content audit workbook

Training & ownership

Include editing practice, written guides and named content owners. Staff can review a preview and send questions in writing. A focused call can support a qualified project that needs personal discussion or approval. Define who controls the domain, hosting, CMS accounts, source files and third-party licenses, and what the agency receives at handoff. Agree on maintenance and support responsibilities.

WORK WITH WHAT YOU HAVE

Fit the site to your
existing systems.

An agency may already have a CMS, framework, payment provider, agenda system, records platform or service-request tool. We review what should stay, what can connect and where a clear link is more appropriate than a custom integration. Vendor permissions, documentation, authentication and data ownership belong in the scope before implementation.

Integration work can range from a carefully labeled external service link to a supported API connection or staff workflow. The project plan should identify the responsible systems, what information moves between them, failure handling and the reviews required by your IT and records teams. Sensitive resident data needs an agreed handling plan.

REVIEW BEFORE RELEASE

Put content and testing in the plan.

Accessibility review

Agree on the pages, templates, documents and interactions to test, including keyboard use, focus, headings, form labels, contrast and image descriptions. Combine automated checks with manual review and a documented correction process. Your agency’s applicable standards and acceptance criteria guide the work.

Read the DOJ web accessibility guide (opens in a new tab)

Content & search

Use clear titles, service descriptions and verified local details so people can understand the information. Review technical indexing and redirects as part of launch. Search placement and inclusion in AI answers depend on external systems and are not guaranteed.

Optional ongoing content

Scope support for service updates, local resources, events or branded social posts separately. Source verification, captions, accessible image descriptions, calendars and client approvals can be part of the workflow. Your team can receive materials, run the calendar itself or authorize a supported publishing setup.

Explore social content support

SEE THE APPROACH

Explore independent work
and a fictional demo.

Screen detail of the actual navy Cedar Bay resident request workspace, including sample counts and the start of its staff queue.
Owned resident request demo with fictional Cedar Bay data. This is a workspace detail; no real messages are sent.

Rogue Valley Now (opens in a new tab), Midland Odessa Now (opens in a new tab) and Mazunte Now (opens in a new tab) are owned, independent community-information projects. They demonstrate information organization, local discovery and multilingual content; they are not government-commissioned client projects.

Cedar Bay is a fictional municipality used in the interactive demos. Try a six-stage resident request, staff resources, content approvals and opt-in updates to discuss how a workflow could fit your agency. The demo uses fictional records and sends no real messages.

Try the fictional municipal workflow

PROCUREMENT & HANDOFF

Agree on the work
and how it is accepted.

Agree on the completed pages, content, staff workflows and handover materials, with written review milestones and acceptance criteria before committing to a build. Include stakeholder review, migration, accessibility testing, training and launch support in the schedule. Larger or phased projects can separate discovery, implementation and ongoing support while preserving a clear plan for the whole site.

Follow the municipal website redesign process to see the stages and useful outputs. For a useful first conversation, share the current site, priority resident tasks, expected editors, document volume and systems involved. The municipal website cost and scope guide explains the decisions that shape a proposal without assuming a fixed platform or project size.

GUIDES, ANSWERS & PLANNING TOOLS

Government website planning

Choose the platform, plan the migration and agree on who will keep the site working.

Process guide

How should a municipal website redesign proceed?

Read the guide

Platform selection

How do we choose a government website CMS?

Read the guide

Ownership and support

Who controls the website and maintains it after launch?

Read the guide

Migration checklist

How do we move pages and documents without losing useful paths?

Read the guide

Service page pattern

What belongs on a resident-facing service page?

Read the guide

Usability protocol

How do we test navigation and service tasks with residents?

Read the guide

Format decision

When should a government document become an HTML page?

Read the guide

Meeting-record design

How should agendas, minutes and meeting records be organized?

Read the guide

Multilingual operations

How should multilingual pages stay aligned after a change?

Read the guide

DEFINE THE NEXT STEP

Bring the need.
Let’s work through the scope.

Share your organization, current website and the tasks you want to improve. Include known content, integration and procurement requirements. Please keep confidential records and credentials out of the project notes.

Check contact availability

Project inquiries are currently unavailable.