docs: redirect Telegram group references to forum and GitHub#172
Open
stevep0z wants to merge 1 commit into
Open
docs: redirect Telegram group references to forum and GitHub#172stevep0z wants to merge 1 commit into
stevep0z wants to merge 1 commit into
Conversation
The OpenZeppelin Telegram community group is being discontinued. Every link to t.me/openzeppelin_tg (and the /2 and /4 topic variants) is being replaced so readers do not land on a dead endpoint. Changes: * Home page Community & Support: replace the Telegram card with a GitHub card pointing to github.com/OpenZeppelin. * Monitor index "For support or inquiries" lines (all versions 1.0.x through 1.3.x and unversioned): point to the forum and the openzeppelin-monitor issues page. * Monitor contribution Getting Reviews bullet: tag a maintainer via a comment or the forum. * Monitor contribution Getting Help: drop the Telegram bullet. GitHub Discussions and Issues bullets already cover community support. * Relayer Support sections in index, evm, stellar, solana, and zama-fhevm (all versions 1.0.x through 1.4.x and unversioned): point to the forum and the openzeppelin-relayer issues page. Intentionally preserved as product features: * Telegram-as-notification-channel docs in content/monitor/architecture.mdx and the configuration tables in content/monitor/index.mdx (trigger_type, api.telegram.org, chat_id, message templates). * Defender notification settings that list Telegram as a delivery platform. * public/defender/manage-notify-telegram.png screenshot. Verified with pnpm lint, pnpm lint:links (0 errors), and pnpm build (870 static pages generated).
✅ Deploy Preview for openzeppelin-docs-v2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
4 tasks
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
1 participant
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
t.me/openzeppelin_tg) across Monitor and Relayer docs.github.com/OpenZeppelin.Surfaces touched
src/app/page.tsx): Telegram card replaced with a GitHub card.content/monitor/**, all versions 1.0.x through 1.3.x and unversioned):index.mdx"For support or inquiries" line points to the forum and theopenzeppelin-monitorissues page.contribution.mdxGetting Reviews bullet rewritten to tag a maintainer via comment or the forum.contribution.mdxGetting Help: the Telegram bullet is dropped (GitHub Discussions + Issues bullets already cover community support).content/relayer/**, all versions 1.0.x through 1.4.x and unversioned): Support sections inindex,evm,stellar,solana, andzama-fhevmpoint to the forum and theopenzeppelin-relayerissues page.Intentionally preserved (product feature, NOT the group chat)
content/monitor/architecture.mdxand the configuration tables incontent/monitor/index.mdx(trigger_type,api.telegram.org,chat_id, message templates).public/defender/manage-notify-telegram.pngscreenshot.This is a community-group cleanup, not a product capability change.
Companion PR
The site-wide banner removal is split out into a separate PR so it can ship independently: #171.