-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathmkdocs.yml
56 lines (49 loc) · 1.66 KB
/
mkdocs.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
# Project Information
site_name: PagerDuty Business Incident Response Documentation
site_description: A collection of information about the PagerDuty business incident response process and industry best practices. This guide will teach you how to create a business response plan that works in tandem with your technical incident response plan.
site_author: PagerDuty, Inc.
site_url: https://business-response.pagerduty.com/
# Repository
repo_url: https://github.com/pagerduty/business-response-docs
# Copyright
copyright: 'Copyright © PagerDuty, Inc.'
# Theme
theme:
name: pagerduty
title: 'Business Response'
# Contents
nav:
- Home: 'index.md'
- Definitions: 'definitions.md'
- What is a Business Incident: 'what_is.md'
- Recognizing a Business Incident: 'declaring.md'
- Before an incident:
- Different Roles: 'before/roles.md'
- The Business SME: 'before/sme.md'
- Triggering a business incident: 'before/trigger.md'
- Call Etiquette: 'before/etiquette.md'
- During an incident:
- Do not panic: 'during/panic.md'
- Incident briefing: 'during/briefing.md'
- Emergency business operations: 'during/emergency_ops.md'
- Managing communications: 'during/communications.md'
- Resolving an incident: 'during/resolving.md'
- After an incident: 'after.md'
# Analytics
google_analytics: ['UA-8759953-1', 'auto']
# Extensions
markdown_extensions:
- toc:
permalink: '#'
- sane_lists:
- admonition:
- meta:
- pymdownx.details:
- pymdownx.extra:
- pymdownx.mark:
- pymdownx.tilde:
- pymdownx.highlight:
- pymdownx.superfences:
- pymdownx.tabbed:
# Development URL, bind to local only.
dev_addr: '127.0.0.1:8000'