Reflect Telegram as a notification destination - #23
Merged
Conversation
Notipus now delivers enriched alerts to Telegram in addition to Slack (Notipus/Notipus#37). Surface it on the marketing site without changing the Slack-first positioning: - Feature copy: "from webhook to Slack or Telegram in seconds". - New FAQ entry "Can I get notifications somewhere other than Slack?" in both layouts/faq.html and the FAQPage schema (kept in sync). Verified: bun lint:css/lint:md/format:check pass, and `hugo --minify` builds cleanly (12 pages) with the new content in the rendered FAQ page, JSON-LD, and home feature card. Co-Authored-By: Claude Opus 5 (1M context) <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.
What
Notipus now delivers enriched alerts to Telegram in addition to Slack (see Notipus/Notipus#37). This surfaces that on the marketing site.
Scoped intentionally: I kept the Slack-first hero/positioning intact (that's a brand call) and only reflected the new capability where destinations are described.
Changes
layouts/index.html): "from webhook to Slack or Telegram in seconds".layouts/faq.html) — new entry: "Can I get notifications somewhere other than Slack?" → yes, Telegram via a bot token + chat ID, per workspace.layouts/partials/schema/faqpage.html): the same Q added to the FAQPage JSON-LD (the file is marked "keep in sync with faq.html").Verification
bun run lint:css,bun run lint:md,bun run format:check— all pass (the CI gate).hugo --minifybuilds cleanly (12 pages); confirmed the new content renders in the FAQ page, its JSON-LD, and the home feature card.Note
If you'd like a deeper pass (hero subhead, the "→ Slack" eyebrow, a Telegram logo in the "Connects to" strip, or the remaining "to Slack" phrasings), say the word — I stopped short of rebranding the core positioning on purpose.
🤖 Generated with Claude Code