Sync with upstream + re-apply Elimu Informatics customizations#6
Merged
Conversation
Adopt the upstream content and theme wholesale: the new mkdocs-theme-pagerduty theme + Netlify config, the rewritten/added pages (crisis section, external communication guidelines, effective postmortems, expanded training course), link and typo fixes, and removal of the old custom theme/ HTML, fonts, and jekyll/circleci config. Elimu customizations are re-applied in the next commit. Upstream: https://github.com/PagerDuty/incident-response-docs @ 6353d89
Rebranding and adaptations carried over from our fork, applied onto the new upstream content: - Rebrand PagerDuty -> Elimu Informatics across operational docs, README, mkdocs.yml; drop PagerDuty marketing, copyright, and Google Analytics ID. - Tooling: alerting/paging references -> OpsGenie; incident tracking -> Jira; status domain -> status.elimu.io, email domain -> @elimu.io. - Severity scheme: SEV-1..5 -> P1..5 (docs + custom.css table classes). - ChatOps: !ic -> !ir commands; swap ic_*.png screenshots for ir_*.png. - site_url -> https://response.elimuinformatics.com (gh-pages CNAME). - Training course (training/courses/incident_response.md): full rebrand; PagerDuty-specific anecdotes generalized rather than falsely attributed to Elimu; dropped PagerDuty University / Summit Series / advocates-email plugs and the training PDF. - Removed the upstream Crisis Response section entirely (PagerDuty product marketing): crisis/ pages, images, nav, and index entries. - Fixed internal anchor links broken by the !ic->!ir rename and a pre-existing upstream anchor typo (post-mortem vs postmortem). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates our fork to incorporate 26 upstream commits from PagerDuty/incident-response-docs (we'd been pinned at the
Fix typo (#105)fork point), then re-applies our customizations on top of the new content.Per the "reset + re-apply" approach, this branch is built fresh on top of
masteras two reviewable commits rather than a conflict-ridden merge of divergent histories:Commit 1 — Sync docs with upstream (115 files)
Adopts upstream content and theme wholesale:
mkdocs-theme-pagerdutytheme +netlify.toml/requirements.txt/runtime.txt; removal of the old customtheme/HTML, Colfax fonts, and the obsolete jekyll/.circleciconfig we'd been carrying.Commit 2 — Re-apply Elimu Informatics customizations (60 files)
mkdocs.yml; dropped PagerDuty marketing copy, copyright, and the PagerDuty Google Analytics ID.status.elimu.io,@elimu.io,site_url→https://response.elimuinformatics.com(matches the gh-pages CNAME).SEV-1..5→P1..5(docs +custom.csstable classes).!ic→!ir; swappedic_*.pngscreenshots for ourir_*.png.!ic→!irrename, plus a pre-existing upstream anchor typo (post-mortemvspostmortem).Verification
mkdocs build --cleansucceeds (tested with the upstreammkdocs-theme-pagerdutytheme installed). Only remaining output is two pre-existing upstream absolute-link infos inanti_patterns.md/incident_commander.md.SEV-,!ic, or danglingcrisis/references. Remainingpagerduty.comreferences are intentional: the theme dependency and the keptsupport.pagerduty.com"Do Not Disturb" links.Notes / follow-ups
netlify.toml,runtime.txt); we deploy via GitHub Pages (response.elimuinformatics.comCNAME). Those upstream deploy files are carried along but unused by us — left in place rather than guessing on deploy changes. The README's "Deploying" section still describes upstream's S3/Netlify flow.github.com/pagerduty/mkdocs-theme-pagerduty(kept as-is per "take upstream's theme wholesale").🤖 Generated with Claude Code