docs(comparison): restructure product section by current product modules - #235
Merged
Conversation
- Reorganize the product dimension into the current module split: On-call (noise reduction, schedules, dispatch & escalation, notification channels), Response, Status Pages, AI SRE, and Platform (ingestion & integrations, alert pipelines & label enrichment, insights & reporting, account & security, developer ecosystem) — replacing the legacy integration/incident-handling/platform grouping - Keep the guide at three purchase dimensions: product, service, pricing - Flatten all Accordions and product-section Tabs into plain headings and tables so the whole comparison is scannable without clicks - Dissolve the standalone customization table into its owning modules and deduplicate rows that appeared in multiple sections
…ar rendering - War room: supported on Slack too, drop the China-IM-only qualifier (Teams not yet supported) - Status Pages: full feature parity from the free tier vs plan-tiered features - AI SRE: reflect PagerDuty's four preset AI Agents (SRE/Scribe/Shift/Insights) and their extensibility model (preset connector list + prompt-style Skills, outward-facing MCP); contrast with the open-ended Agent loop (Skills/MCP/Subagents/A2A); concretize AI Actions allowances per plan - Developer ecosystem: add a PagerDuty column (CLI status, official client libraries) - SSO: compare protocols only - Escape bare dollar signs that triggered LaTeX math rendering in tables - Add an SVG cost-curve chart (zh/en) to the cost comparison example
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.
Follow-up to #233/#234 — structural pass on the same page, no fact changes.
zh and en are line-for-line aligned (380/380, identical heading positions, 136 table rows each); all internal links verified.