Merged
Conversation
… Alerting assets - Remove monolithic flows/notification.md and notification-tokens.md (content migrated to per-channel sub-pages) - Add Notifications overview page and per-channel screenshots (In App, Email, Slack, Microsoft Teams, PagerDuty) - Rename alerting logos to TECHNOLOGY-logo.png pattern and remove deprecated settings-light.png - Rewrite Alerting Integrations Overview with centered logos and standardized layout - Update internal links in Slack and Teams integration pages - Update mkdocs.yml navigation and add redirects for old paths
- Add PagerDuty overview, deep dive, API, and FAQ pages under Settings > Integrations > Alerting - Add managing guides: add, edit, and remove integration - Add PagerDuty screenshots for all managing workflows - Add shared settings screenshot and PagerDuty logo
- Add Overview, API, and FAQ for each notification channel: In App, Email, Slack, Microsoft Teams, and PagerDuty - Add Message Variables page with channel-specific tokens - Add general Notifications FAQ - Update action overview links to new notification paths
RafaelOsiro
requested review from
Hitsu-360,
gasscoelho,
josecsotomorales,
pelegolas9 and
shindiogawa
…avigation Mermaid Diagrams: - Remove custom fill/color/stroke styles from all 5 Notification lifecycle diagrams (In App, Email, Slack, Microsoft Teams, PagerDuty) to use mermaid default theme, which auto-adapts to light/dark mode - Remove custom styles from Field Status Lifecycle diagrams (User-Driven and Automatic Transitions) for consistency - Wrap all Notification lifecycle diagrams in centered div containers using md_in_html for visual alignment Navigation: - Move general Notifications FAQ below PagerDuty in mkdocs.yml sidebar - Resolve mkdocs.yml merge conflict: combine Notification redirects with new main branch redirects (source-datastore reorganization, container operations, add-datastores, AI integrations, checks rename) Alerting Overview: - Remove Documentation column from Available Integrations table (redundant with per-section "For more details" links) - Remove Integration column links (redundant with section links)
…tructure Expand the Notifications Overview from a minimal intro + channel table into a comprehensive landing page following the established pattern used by Field Status, Datastore Grouping, and AI & Agents overviews. New sections added: - Why Notifications Matter: explains the value of real-time alerts - How Notifications Work: mermaid lifecycle diagram + 5-step processing flow - Supported Triggers: table of all 6 trigger types with available variables - Testing Notifications: describes test button behavior per channel - Reference: links to Message Variables and FAQ Also improves channel descriptions with specific details (Block Kit, Adaptive Cards, severity levels, routing key overrides) and adds contextual guidance throughout the page.
Replace numbered/generic image filenames (notification-44.png, save-8.png, test-52.png, etc.) with descriptive names that reflect what each image shows. Update all markdown references across notification channel pages accordingly. Renamed images per channel: - Root: notification-44 → notification-channels - In App: notification-45/46/47 → select-in-app, in-app-settings-panel, in-app-message-variables - Email: notification-49/50/51 → select-email, email-settings-panel, email-settings-fields - Microsoft Teams: notification-59/60/61 → select-microsoft-teams, teams-settings-panel, teams-settings-fields - PagerDuty: notification-64/65/67/68 → select-pagerduty, pagerduty-settings-panel, severity-dropdown, pagerduty-message-variables - All channels: save-8 → save-button, test-52 → test-notification-success Also fix broken image path in PagerDuty integration overview (removed extra `docs/` prefix from relative path).
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
2 participants
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.
Overview
This PR adds PagerDuty integration documentation and restructures the Flows Notification section from a monolithic page into per-channel sub-pages, improving navigation and maintainability.
Key Changes
notification.mdinto dedicated sub-pages per channel (In App, Email, Slack, Microsoft Teams, PagerDuty), each with Overview, API, and FAQnotification-tokens.mdtomessage-variables.mdwith a new channel-specific variables sectionTECHNOLOGY-logo.pngpattern, organize notification screenshots per channel, and remove deprecated assetsmkdocs.ymlsidebar with new Notifications and PagerDuty structureScreenshots