Reflect Microsoft Teams as a notification destination - #25
Merged
Conversation
Notipus now delivers enriched alerts to Microsoft Teams in addition to Slack and Telegram (Notipus/Notipus#178). Surface it on the marketing site alongside the existing destinations, keeping the Slack-first positioning unchanged: - Home feature copy: "from webhook to Slack, Telegram, or Microsoft Teams in seconds". - Extended the "Can I get notifications somewhere other than Slack?" FAQ answer to name Teams and its Workflows webhook setup, in both layouts/faq.html and the FAQPage JSON-LD schema (kept in sync). Verified: bun lint:css / lint:md / format:check pass. `hugo --minify` builds cleanly (12 pages) with the new copy in the rendered FAQ page, JSON-LD, and home feature card (local build confirmed with the PostCSS asset step bypassed — the local Bun PostCSS shim gap is a pre-existing environment issue that reproduces on clean master and does not affect the actions-hugo CI build). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GMSEWRc8EtJUAeRWEJLw8u
Reframes /integrations into two sections: "sources" (the billing/commerce platforms events come from — Stripe, Shopify, Maxio) and "destinations" (where enriched alerts land — Slack, Telegram, Microsoft Teams), reflecting that Notipus now delivers to all three. - Add @tabler/icons as a bun dependency (our icon kit, matching the app) and mount it into Hugo assets; a new `tabler.html` partial inlines the real brand SVGs (brand-slack/telegram/teams) tinted per brand color. - Destinations are data-driven via data/destinations.yaml. - Drop the stale "Microsoft Teams … on the roadmap — Slack is the delivery channel today" footnote and the Slack-only hero/CTA copy. - Update the index title/description for the added destinations. Verified: bun lint:css / lint:md / format:check pass; hugo --minify builds cleanly (12 pages) with both sections, all three inlined Tabler brand icons, and the roadmap footnote gone (local build confirmed with the PostCSS asset step bypassed — pre-existing Bun/PostCSS env issue, unrelated, CI unaffected). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GMSEWRc8EtJUAeRWEJLw8u
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.
Summary
Notipus is adding Microsoft Teams as a notification destination (Notipus/Notipus#178). This surfaces it on the marketing site alongside Slack and Telegram, without changing the Slack-first positioning — mirroring how Telegram was rolled out in #23.
Changes
layouts/index.html) — "from webhook to Slack, Telegram, or Microsoft Teams in seconds".layouts/faq.html) — extended the "Can I get notifications somewhere other than Slack?" answer to name Teams and its Workflows-webhook setup.layouts/partials/schema/faqpage.html) — same answer text, kept in sync with the visible FAQ.No other Slack references were touched (demo card, integration page titles/aria-labels, the event definition) — those stay Slack-first by design, consistent with the Telegram change.
Verification
bun run lint:css,bun run lint:md,bun run format:check— all pass.hugo --minifybuilds cleanly (12 pages); confirmed the new copy renders in the FAQ page, its embedded JSON-LD, and the home feature card.🤖 Generated with Claude Code