Table of Contents automatically generates a side navigation menu based on the headings (H2–H4) used on the page. As headings are added to the content, they become clickable links that allow users to quickly jump to each section, making long pages easier to navigate.

H1: Page Title (should NOT be in TOC)

This h1 should be completely ignored by the TOC generator. If you see it in the sidebar, the selector is too broad.

Section 1. Overview

This h2 should appear as a top-level item in the TOC. All content below it until the next h2 belongs to this section.

Purpose (H3)

This h3 should appear as a nested sub-item under "Section 1. Overview" in the TOC. Editors naturally use h3 for sub-sections.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus volutpat nibh vel tortor sollicitudin, ut convallis sem elementum. Aenean sagittis non enim id consequat. Sed vitae metus quis libero tincidunt fermentum.

Scope of the Plan (H4.red)

This h4.red should appear as a nested sub-item under "Section 1. Overview" in the TOC. This is the Elliance design pattern.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam auctor, nisi eget ultricies ultrices, nunc nisl aliquet nunc, vitae aliquam nisl nunc sit amet nisl.

Type of Incidents (plain H4, no .red class)

This plain h4 should NOT appear in the TOC. It's a body-level detail heading. If you see it in the sidebar, the selector is catching too much.

Natural Hazards	Human Caused	Technological
Severe weather Wildfire Floods	Assault/battery Cyber attack Active harmer	Hazmat spill Utility failure Structural collapse

Planning Assumptions (H5)

This h5 should NOT appear in the TOC. It's a body-level sub-detail heading.

A critical incident may occur at any time of day or night.
Most incidents are handled locally.
Emergency functions will align with normal functions.

Detailed Note (H6)

This h6 should NOT appear in the TOC. It's the lowest heading level.

Section 2. Comprehensive Emergency Management

This second h2 should appear as another top-level item. The sub-list under Section 1 should have closed.

1. Mitigation/Prevention (H3)

H3 sub-section under Section 2. Should nest as sub-item.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Donec velit neque, auctor sit amet aliquam vel.

2. Preparedness (H4.red)

H4.red sub-section under Section 2. Should also nest as sub-item alongside the H3 above.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras ultricies ligula sed magna dictum porta.

3. Response (H3)

Another H3 sub-section. All three (H3, H4.red, H3) should be siblings in the TOC sub-list.

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

4. Recovery (H4.red)

Another H4.red sub-section. Should be a sibling of the H3s above.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent sapien massa, convallis a pellentesque nec, egestas non nisi.

Recovery Timeline Detail (plain H4)

This plain h4 should NOT appear in the TOC even though it's between sections that are in the TOC.

Section 3. Concept of Operations

Third top-level section. Previous section's sub-list should close.

Plan Implementation (H4.red)

Sub-section under Section 3.

Save and protect lives
Establish command and control
Coordinate communications
Stabilize the incident
Control the scene
Prevent damage
Provide essential services
Restore critical services

Incident Reporting (H4.red)

Another sub-section under Section 3.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla porttitor accumsan tincidunt. Mauris blandit aliquet elit, eget tincidunt nibh pulvinar a.

Section 4. Roles & Responsibilities — "Key Personnel"

This h2 has ampersand, em-dash, and quotes. The slugify function should handle these cleanly.

Emergency Management Structure (H4.red)

Sub-section with normal text.

Lorem ipsum dolor sit amet.

1. Executive Leadership and Policy Group (H5)

This h5 should NOT be in the TOC — it's a detail heading under the sub-section above.

Members:

President
Provost
VP Student Life

2. Emergency Operations Team (H5)

Another h5 — NOT in TOC.

Lorem ipsum dolor sit amet.

External Agency Support (H4.red)

This should be in the TOC as a sub-item under Section 4.

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Section 5. Communications

Overview (H4.red — duplicate text test)

The word "Overview" also appears as part of "Section 1. Overview". The slugify should generate a unique ID like "overview-2".

Prévention des Risques (H4.red — Unicode test)

The accent in "Prévention" should be handled by NFKD normalization. The ID should be "prevention-des-risques" not "prvention-des-risques".

Section 6. Emergency Facilities

Incident Command Post (ICP)

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Emergency Operations Center (EOC)

EOC Locations

GRL Classroom — 1310 Maple Street
Mines Park Community Center #2, 2001 Infinity Circle
Conference room, 1318 Maple Street

Section 7. Document Control Log

Final section to test scrolling to the bottom of the page and active state tracking.

Revision #	Description	Date
1	Initial issue	10/15/2015
2	Update content	2/27/2020

Appendix A — Acronyms

Acronym	Definition
EOP	Emergency Operations Plan
EOT	Emergency Operations Team
ICS	Incident Command System
NIMS	National Incident Management System

Return to Design System Overview

About Mines

Academics

Research

Student Experience

Admission & Aid

Popular Links

Table of Contents