Add dedicated Support Page#439
Open
Shah91n wants to merge 1 commit into
Open
Conversation
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new dedicated /support documentation page and wires it into the docs UI so users have a single, discoverable place to route themselves to the right help channel.
Changes:
- Introduces
docs/support/index.mdxwith support channel cards and a routing table. - Registers a new
supportSidebarand adds asupportentry to the secondary navbar configuration. - Surfaces Support entry points in the primary navbar (icon) and doc footer (internal link).
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
docs/support/index.mdx |
New Support landing page content (channels + guidance). |
sidebars.js |
Adds a dedicated supportSidebar pointing at the new page. |
secondaryNavbar.js |
Adds a Support section to the secondary navbar options. |
docusaurus.config.js |
Adds a Support icon link in the primary navbar. |
src/css/custom.scss |
Styles for the new navbar icon and icon-link padding. |
src/theme/DocItem/Footer/Footer.js |
Updates footer to point users to /support under “Get help”. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+212
to
217
| { | ||
| html: `<i class="fa fa-headset supportNavIcon" title="Support" aria-hidden="true"></i>`, | ||
| to: "/support", | ||
| position: "right", | ||
| className: "navbarIconLink", | ||
| }, |
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
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
Adds a dedicated Support page at
/supportand surfaces it across the docs.Why
There's currently no single place that explains how to get help with Weaviate. Support info is scattered,
support@weaviate.iois buried inline in a few Cloud pages, the forum is the only thing surfaced in the footer, and support plans live on the website. There's no page that tells someone which channel for which situation, so users often land in "Contact Us" on the main site even when they need actual support.Changes
docs/support/index.mdx): channel cards + a "which channel for which situation" routing table, covering:support@weaviate.io, with SLA framing)supportSidebar(sidebars.js) and asupportsection (secondaryNavbar.js)docusaurus.config.js+src/css/custom.scss)src/theme/DocItem/Footer/Footer.js)Testing
yarn build/yarn build-devyarn validate-links-dev/support