Fire department websites and hosting.

Custom, content-managed sites staff can update, built to read well on a phone in the field. Structure comes first: residents should reach evacuation, road closure, and burn permit information in one or two taps.

• Joomla-based, with editing that non-technical staff can handle. We maintain the platform, updates, and security; the agency handles the words.
• Clean, semantic pages that search engines read correctly and screen readers can follow.
• Migration from an old or abandoned site, with redirects so existing links and search rankings carry over.

Accessibility is now law. State and local government sites must meet the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard under the Americans with Disabilities Act (ADA) Title II. The Department of Justice set the standard in a 2024 rule. In April 2026 the compliance deadlines were extended to April 26, 2027 for entities serving 50,000 or more, and April 26, 2028 for smaller entities and special districts, which covers most fire districts. The rule reaches the vendor that builds the site, not only the agency. We build to that standard. (Source: ADA.gov; DOJ Title II web rule.)

A public agency website is public safety infrastructure. During a wildfire or major incident, traffic spikes at the moment residents need road closures, evacuation zones, and shelter information. Standard hosting can slow or fail under that load.

• Managed cloud hosting, US-based, sized to hold during local and regional emergencies.
• Each site on its own isolated hosting account, behind a web application firewall and server-side malware scanning.
• Daily backups with an off-server copy.
• When a vulnerability is announced in the CMS or an editor plugin, every site we host gets the patch, not only the one that reported a problem.
• 100% renewable energy, certified by the Green Web Foundation.
• Support 8am to 5pm Pacific, with 24-hour emergency technical support included. No outsourcing; data stays in the US and stays with the agency.

Pricing is below.

When a resident searches for burn-permit rules or an evacuation update, the agency's official page should be the result, not a third-party aggregator or an out-of-date listing.

• Sites built so search engines can read and rank them, with clean structure, titles, and headings.
• Local search signals so the department shows up for its community.
• Findability for the pages that matter most in an emergency.

Official messages only work if they arrive. We configure SPF, DKIM, and DMARC (the email authentication records) on every domain we host, so agency messages reach residents and staff and the domain cannot be easily spoofed.

You keep your domain and DNS in your name. When a vendor needs a record added (a new mail provider, an IT contractor), we add it. Nobody receives your credentials.

The website is the main channel, so the communications work is built around it. Before design, we define what the department needs to say and to whom, and the site and supporting materials follow from that.

• Public information: road closures, evacuations, burn permits, defensible space rules, inspections, and how residents reach the agency, organized so people find them quickly.
• Incident communications: a plan for what goes out, where, and who posts it when an event is underway.
• Mission and outreach: presenting programs, prevention work, and community role clearly rather than burying them.

Google Workspace or Microsoft 365 for secure internal communication across stations and in the field, with shared files and calendars. For agencies that handle patient data, Google will sign a HIPAA Business Associate Agreement covering the included services, which we configure as part of setup.

Government agencies have records-retention obligations and public-records requests. We set up systems that keep public information secure, readable, and retrievable, and that meet the accessibility standard the agency is now held to.