BusPatrol
BusPatrol
- ClientBusPatrol
- StackWordPress · Custom development
- StatusUnder care
Three audiences, one page
Stop-arm enforcement has three readers who want completely different things. A school district wants to know what it costs and who runs it. A municipality wants the legal and procurement position. A parent wants to know their child is safer, and is not interested in either of the first two answers.
Writing one page for three readers usually produces a page that works for none of them.
Let each reader self-select, early
A structure where each audience picks its own route and then stays in it, rather than one scrolling argument attempting to serve everyone. Program information, evidence workflow and district-facing material each got their own track.
Underneath, the same discipline as the rest of the work: a theme that owns the design, content types that survive a redesign, and an editor experience narrow enough that a program manager can publish without a developer.
Program pages without a build
New districts can be stood up as content rather than as work — the difference between a site that scales with the business and one that becomes a bottleneck in it.
Before you publish
Editor note: this write-up is placeholder. The client, the scope and the stack are real; the figures and outcomes are not measured. Replace them or cut them before publishing.