Improve discoverability of support and escalation/contact guidance in docs #975
Description
Context
Slack thread: https://slack.com/archives/C0AE8A81LE6/p1770829408004689
A recent internal thread only captured channel-topic updates and owner mentions, which suggests people may be relying on Slack metadata to find the right contacts instead of finding this information quickly in docs.
Problem
The docs do not appear to make support-routing and ownership guidance easy to discover from common entry points. When users or contributors need to know who to contact (or where to ask specific questions), they may fall back to Slack channel topics rather than documentation, which is hard to scale and easy to miss.
Suggested Fix
- Add a clearly titled page/section for support routing (for example: "Where to Ask for Help" or "Support and Escalation").
- Link this page from high-traffic docs entry points (for example, intro/README/FAQ-style pages).
- Include search-friendly keywords and phrasing such as: support, help, contact, owner, escalation, Slack, troubleshooting.
- Add a short decision table (question type -> recommended channel/contact path).
- Ensure the page title and headings are explicit enough to be discoverable via site search.
Existing Documentation
- README.md
- cloud/faq.mdx
- cloud/sso.mdx
- cloud/intro.mdx
- sql/functions/mathematical.mdx
- operate/telemetry.mdx
- troubleshoot/meta-failure.mdx
- sql/commands/sql-alter-fragment.mdx
- ingestion/sources/postgresql/neon.mdx
- operate/secure-connections-with-ssl-tls.mdx
Related docs PRs:
Codebase References
Related PRs in risingwave:
- feat: risectl command to force change Source Connector Props
- feat: support LogicalExpand in DataFusion
- refactor: update some metric level
- fix(snapshot-backfill): fix deadlock caused by next_epoch
- feat(sink): support copy into wihout barrier for redshift
Source files: