Websites for public service

Websites people can use. Systems staff can manage.

We design and support accessible websites for towns, nonprofits, and growing organizations. People can find the permit, meeting packet, donation form, alert, or staff contact they came for.

  • WCAG 2.2 AA target
  • Responsive by default
  • Founder involved

Plain-language content

Accessible interaction

Fast, resilient pages

Support after launch

Who we serve

Different organizations. Many of the same website problems.

We organize each site around what visitors are trying to do and what staff need to publish, approve, and maintain.

What we do

Strategy, design, development, and support under one roof.

We can help with one stubborn problem or take responsibility for the whole website, from the first content audit through post-launch support.

01

Strategy & information architecture

Make navigation match the questions people ask, not the way the organization is structured.

See service details
02

Accessible UX & visual design

Make every page easy to scan, use by keyboard, and read on a phone or at high zoom.

See service details
03

Development & integrations

Build a fast, maintainable site and connect the forms, calendars, payments, and alerts people rely on.

See service details
04

Content & document migration

Decide what to keep, rewrite, merge, archive, or retire before migration begins.

See service details
View all six services

Featured concept

A town website organized around resident tasks.

Northfield is a fictional municipality we use to show how meetings, alerts, permits, payments, records, and community information can share one predictable structure.

  • Task-based navigation
  • Accessible service pathways
  • Simple staff publishing
  • Emergency-ready notices
Walk through the Northfield concept

How we work

You always know what happens next.

Each phase ends with something concrete to review, a named decision-maker, and a short list of open questions.

  1. 01

    Discover

    Interview the people closest to the work, review the current site, and write down the goals, constraints, and risks.

  2. 02

    Structure

    Agree on priority tasks, navigation, page types, content ownership, and the delivery plan.

  3. 03

    Design

    Review wireframes and responsive components with real content before the build is far along.

  4. 04

    Build

    Develop the site, connect required services, migrate approved content, and document the setup.

See the six-phase process

Founder involved

The people you meet stay responsible for the work.

A founder stays involved from the first conversation through launch and support. You get direct answers from the people doing the work.

Portrait of Eddy Elkhashab wearing a dark polo shirt
Co-Founder & Technical Director

Eddy Elkhashab

Technology · Delivery · Operations

Portrait of Nicholas Brooks
Co-Founder & Strategy Director

Nicholas Brooks

Strategy · Product · Client experience

Meet the founders

Before we begin

Questions worth answering before anyone signs a contract.

These are the three things we are asked most often at the start of a project.

Do we need a finished scope?

No. Send the current website, the problems people report, and any deadline you already know about. We can help turn that into a scope.

Can the work be phased?

Yes. We can begin with an assessment, one priority service, accessibility repairs, or a content plan before taking on a full redesign.

What happens after launch?

Townline can handle hosting coordination, monitoring, updates, accessibility checkups, content help, and a planned improvement list.

Read all frequently asked questions

Start a conversation

Tell us where people are getting stuck.

Tell us about your project