About this prototype

INTERNAL REVIEW

Navigation & content reconciliation

The live county site was re-crawled before this navigation change. The baseline reports record gaps before implementation; the coverage report records the implemented catalog and links. Proposed WordPress URLs are separate from working prototype redirects.

• Current-site inventory
• PDF & download inventory
• Prototype gap analysis (before changes)
• Reconciliation after implementation
• Final local route crawl
• Proposed WordPress sitemap
• Shared mega-menu hierarchy
• Consolidation recommendations
• Document Center taxonomy
• Working prototype redirects
• Proposed WordPress redirects
• County decisions
• Broken or inaccessible resources
• Post-implementation coverage checks
• WordPress content & navigation kit

County approval is still needed for content currency, retention, ownership and inaccessible files. PDF text extraction does not establish accessibility compliance. The WordPress kit requires staging installation and validation; this prototype is not a running WordPress migration.

Demonstrated in prototype

1. Accessibility approach

Semantic page structure, labeled controls, skip navigation, visible keyboard focus, search announcements and reduced-motion support.

Planned for production: WCAG 2.2 Level AA as the target; automated scans plus manual keyboard, screen-reader, touch, contrast and 200% text-enlargement testing. Legacy PDFs require an inventory, accessibility review, remediation or accessible HTML alternatives. Conformance is not yet certified.

Demonstrated in prototype

2. Content audit and migration

County source pages and linked documents are indexed, with duplicate and historical material identified for review.

Requires County confirmation: content owners, retention policy, current versions, broken destination replacements and image rights. Production migration includes redirects, attachment verification and County sign-off.

Demonstrated in prototype

3. WordPress architecture

Structured departments, services, documents, meetings, people, notices and locations; relationship previews and department-scoped editor views.

Planned for production: standalone Mitchell County Core plugin, separate block theme and importer; server-enforced department roles, WordPress revision history, media permissions, scheduled notices and expiration. The role selector is a simulation, not real authorization.

Planned for production

4. Security, hosting and disaster recovery

SSL, multifactor authentication, least-privilege accounts, web application firewall, malware monitoring, routine updates and a staging environment.

Daily backups and documented restore testing are planned. Requires County confirmation: retention, recovery-time and recovery-point objectives, hosting responsibility, uptime expectations and contractual service levels. No uptime or security certification is claimed for this prototype.

Planned for production

5. Training and user acceptance testing

Administrator and department-editor training, task-based documentation, recorded walkthroughs and a practice environment.

County staff will test common resident tasks, department publishing, records, permissions and accessibility before launch. Requires County confirmation: participants, acceptance criteria and sign-off owners.

Planned for production

6. Maintenance, warranty and support

Routine plugin/theme/core updates, monitoring, backup checks and a documented support channel.

Warranty defects will be logged, prioritized, corrected in staging, tested and released. Requires County confirmation: warranty term, response windows, support hours, maintenance scope and distinction between defects and new features.

Requires County confirmation

7. Project timeline

Proposed sequence: discovery and content audit; architecture and prototype approval; WordPress implementation and migration; accessibility testing and staff training; user acceptance; launch and warranty support.

Milestone dates, review windows, staffing and launch dependencies must be agreed with the County. No committed delivery dates are implied.

Planned for production

8. County ownership and no vendor lock-in

Mitchell County owns its content, commissioned code, templates and administrative accounts, subject to applicable open-source and third-party asset licenses.

Handoff includes separate plugin and theme ZIPs, sample importer, source, account inventory, installation/editor documentation and accessibility checklist. Standard WordPress exports and documented data relationships support migration to another provider.

Header photography

Locally stored photographs from the county website and Discover Mitchell County. All are temporary: individual reuse rights require County confirmation.