10 / Web governance + support
Keeping 25+ school and program sites moving in the same direction.
Perry Township Schools operates a decentralized web ecosystem, with staff across 25+ school and program sites responsible for maintaining their own content.
I create the structure around that work through expectations, training, audit follow-up, accessibility guidance and ongoing support for a network of 26 webmaster contacts.
- Role
- Web governance, webmaster training, audits, accessibility guidance and ongoing support across 25+ school and program sites.
- Challenge
- A decentralized network of staff maintains public school sites while also holding other primary jobs, so consistency cannot depend on everyone already knowing WordPress or accessibility standards.
- Approach
- Built expectations, instructional resources, live training, an audit follow-through system and centralized shared resources so ownership and next steps stay clear.
- Result
- 22 webmasters trained (13 in person, 9 online) with about 64 minutes average online participation, plus a shared audit tracker for assigning and closing work.
25+
School + program sites
26
Webmaster contacts
22
Webmasters trained
~64 MIN
Average online training participation
01
The challenge.
25+ sites. Different people maintaining them. One district standard.
Most school webmasters have another primary job. They are educators, office staff or school employees who also keep part of a public-facing website accurate.
Governance has to work for people who may not live in WordPress every day: clear expectations, usable tools, live support and a way to close the loop when something still needs attention.
02
Setting expectations.
Webmasters get a shared standard for the recurring work that keeps a school site usable, from staff information and calendars to news, links and accessibility considerations.
Start of year
- Staff information
- Supply lists
- Schedules
- Transportation
- Policies
03
Giving people the tools.
Governance only works if people have the tools to follow it.
I maintain a detailed WordPress guide so webmasters have somewhere to go when they need to make an update, troubleshoot something unfamiliar or check a standard.
That keeps live training focused on judgment, recurring issues and current priorities instead of repeating the same step-by-step instructions.
Page editing
How to update existing pages, publish changes and keep layouts intact without breaking the rest of the site.
04
Training + support.
I coordinate live webmaster training so staff can work through updates, ask questions and get support in real time. For the 2026–27 school year, that included both in-person and virtual options.
22 webmasters attended: 13 in person and 9 online. Online participants with substantive attendance stayed about 64 minutes on average.
22
Webmasters trained
13
In person
9
Online
~64 MIN
Average online participation
Expectations
What needs to stay accurate.
05
Website audits.
Maintaining consistency across 25+ school and program sites takes ongoing review. I help conduct website audits alongside our web developer so findings turn into work people can actually complete.
Each finding is documented by page, issue type, priority, status and ownership. That structure separates what school webmasters can fix from what needs district or developer support, then carries the work through communication, correction and follow-up.
Review
Look at the page through both a user and governance lens.
Then it starts again as sites change.
How the work gets tracked
A shared system for follow-through
Every finding gets a page, issue type, priority, owner and status so everyone knows what needs to happen next.
| Page | Link | Issue type | Priority | Status | Owner | Done |
|---|---|---|---|---|---|---|
| Home Page | Open | User Experience | ||||
| About › Strategic Plan | Open | Outdated Information | ||||
| Departments › Child Nutrition | Open | Broken Link | ||||
| For Parents › Enrollment | Open | Missing Information | ||||
| Staff Directory | Open | Site Organization |
Interactive demo. Changes stay here and never touch the live audit.
06
Some information should live once, not 25+ times.
When information can be managed at the district level, I centralize it instead of asking every webmaster to rebuild and maintain the same thing.
That keeps shared resources consistent while webmasters focus on content unique to their schools.
One district source
- Student handbooks
- Menu links
- Shared district resources
- School site
- School site
- School site
- School site
Update once → reflected everywhere it belongs.
07
What it comes down to
People need to know what they own, have resources they can actually use, and know where to go when something gets complicated.
- Web governance
- Website management
- Webmaster training
- Accessibility + WCAG
- Content operations
- Cross-functional coordination