Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Emergency services

Index for fire and rescue services, civil protection and emergency management bodies planning an Exponential site - what they publish, content model, structure and roles, requirements, a 90-day plan, and alerts with…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/levels/emergency-services/README.md

On this page

Emergency services

This folder is for project managers, administrators and website creators at a fire and rescue service, a civil protection authority or an emergency management body. Their websites have two lives: a quiet one (prevention advice, recruitment, reports) and an emergency one, when many people need current, correct information at once and the site must stay up. The pages answer what emergency services publish, how to build it in Exponential, which requirements weigh most, how to run the first 90 days, and how to keep alerts available with caches, static pages and maintenance mode.

Product facts come from the documentation of this repository; descriptions of emergency services are general public-sector practice. A website is never the only warning channel; emergency warning systems, broadcast and telephone networks are outside Exponential.

Contents

  1. The pages
  2. Reading order
  3. What sets emergency services apart

The pages

PageThe answer in one line
What an emergency service publishesIncident and warning information, preparedness advice, prevention, services, recruitment, reports
Content model for emergency servicesShipped classes plus Incident update and Preparedness guide classes, small and fast to fill
Structure, sections and roles for emergency servicesAn incident area at the top, an on-call publishing team without approval, everything else reviewed
Requirements emphasis for emergency servicesAvailability, speed, accuracy, accessibility under stress, languages, security
The first 90 days for emergency servicesA plan that proves availability and the incident procedure before launch
Alerts, availability, maintenance mode and static cacheKeeping incident information online under load and during failures, with the tools that exist

Reading order

  1. Alerts, availability, maintenance mode and static cache: it shapes the rest.
  2. What an emergency service publishes.
  3. Requirements emphasis.
  4. Content model and Structure, sections and roles.
  5. First 90 days.

Up: Levels of government. The landing page of the Governments section, Governments: start here, is the starting point for every reader. Health alerts are covered in Alerts in many languages and plain language.

What sets emergency services apart

TopicWhy it matters
Peakstraffic during an incident can be far above normal
Speedinformation is useful for minutes or hours
Failuresthe incident may affect power, networks or the hosting itself
Stressreaders are frightened; clarity and accessibility matter most
Night and weekendpublishing happens at any hour, by few people

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x