Conversation
…oves Node-20 deprecation warnings) [skip ci]
…oves Node-20 deprecation warnings) [skip ci]
ci: migrate CodeQL runner to self-hosted ARC (develop)
Feat/docs UI revamp
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Not up to standards ⛔
|
| <li> | ||
|
|
||
| **Check the API is reachable** — visit{" "} | ||
| <code>[https://api.ever.team/api/health](https://api.ever.team/api/health)</code>, or your own API host, and |
There was a problem hiding this comment.
Health endpoint renders as source
The Markdown link is nested inside <code>, so the support page displays the raw link syntax instead of a clickable health endpoint, adding friction to the troubleshooting step.
| <code>[https://api.ever.team/api/health](https://api.ever.team/api/health)</code>, or your own API host, and | |
| <a href="https://api.ever.team/api/health"><code>https://api.ever.team/api/health</code></a>, or your own API host, and |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Greptile SummaryThis PR redesigns the documentation site and expands its support and product content.
Confidence Score: 4/5The PR appears safe to merge, with a non-blocking documentation formatting issue on the new support page. The site changes are internally consistent, but the health endpoint is placed as Markdown link syntax inside a code element, causing readers to see a non-clickable source-formatted URL. Files Needing Attention: website/docs/advanced-guide/support.mdx
What T-Rex did
|
| Filename | Overview |
|---|---|
| website/docs/advanced-guide/support.mdx | Adds the full support guide and channel components; one health-check URL renders as literal Markdown instead of a usable link. |
| website/docusaurus.config.ts | Reconfigures fonts, navigation, search placement, logos, footer metadata, and table-of-contents behavior. |
| website/src/css/custom.css | Replaces and substantially expands the site-wide visual system, responsive behavior, and light/dark theme styling. |
| website/src/components/SidebarPromo/index.tsx | Adds a route-aware promotional sidebar for the support page. |
| website/src/theme/MDXComponents.tsx | Wraps Markdown tables in keyboard-focusable horizontal scroll containers. |
| website/docs/kit/index.mdx | Introduces the Ever Teams Kit overview and links it into the documentation. |
| .github/workflows/k8s-build.yml | Updates action major versions and selects the smaller configurable Linux runner. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart LR
Navbar[Navbar] --> Docs[Documentation]
Navbar --> Support[Support page]
Support --> Promo[Cloud sidebar promo]
Docs --> Kit[Ever Teams Kit]
Docs --> Tables[Scrollable MDX tables]
Theme[Global theme tokens] --> Navbar
Theme --> Support
Theme --> Kit
Theme --> Footer[Custom footer]
Comments Outside Diff (1)
-
General comment
Support page causes React hydration failure
- Bug
- Loading the changed
/advanced-guide/supportpage from the production build emits many React error #418 hydration mismatches followed by error #423, indicating that hydration failed and React switched the root to client rendering. The same baseline route produced no browser errors. Although the page remains visible, this discards SSR work and can cause content replacement or layout instability during startup.
- Loading the changed
- Cause
- The new MDX wraps Markdown content in explicit JSX
<p>elements while leaving blank lines around the content, for example nearwebsite/docs/advanced-guide/support.mdx:121-128and:132-137. The generated server HTML confirms these become an empty styled paragraph followed by a separate unstyled paragraph and another empty paragraph (<p class="heroLead_…"></p><p>…</p><p></p>), producing markup that does not agree with the client render. The pattern is repeated elsewhere in the page.
- The new MDX wraps Markdown content in explicit JSX
- Fix
- Do not place Markdown blocks separated by blank lines inside explicit JSX
<p>wrappers. Keep the text inline with the opening and closing tag, or use a<div>wrapper and style its generated paragraph. Rebuild and verify that the production Support route loads with noonRecoverableErrormessages.
- Do not place Markdown blocks separated by blank lines inside explicit JSX
- Bug
Reviews (1): Last reviewed commit: "Merge pull request #71 from ever-co/feat..." | Re-trigger Greptile
No description provided.