Hive Gateway landing page: top sections #6461

hasparus · 2025-02-03T17:08:45Z

Background

Description

Added the hero and a basic features tab — without the card animations from new design yet, just the old tabs.

The simpler sections and FAQs are coming in next PRs.

coderabbitai · 2025-02-03T17:11:05Z

📝 Walkthrough

Summary by CodeRabbit

New Features
- Launched a refreshed gateway landing page featuring a hero section, dynamic tabs showcasing observability, performance, and security features, and a marquee display of useful links.
- Introduced an integration highlights section to streamline access to key functionalities.
Documentation
- Added a comprehensive FAQ section addressing common questions and improving user guidance.
Chores
- Upgraded dependency versions and updated tooling for enhanced performance and stability.

Summary by CodeRabbit

New Features
- Launched a dedicated Hive Gateway page featuring a dynamic hero section, interactive feature tabs, product cards, an engaging marquee of resource links, and an "Orchestrate Your Way" segment showcasing integration options.
Documentation
- Added a Frequently Asked Questions section addressing common inquiries on migration, subscriptions, performance, tracing integrations, and customization.
Chores
- Upgraded dependencies and streamlined navigation links for a more consistent user experience.

Walkthrough

The changes update dependency versions and package management while introducing new gateway-related features. New components are added for the Hive Gateway, including the feature tabs and marquee rows, along with a dedicated landing page. The primary index page now uses a revised feature-tabs component. Additionally, the FeatureTabs component is refactored to include contextual state management, and related UI components (including the landing page feature tabs) are adjusted accordingly. A legacy Stud component is removed, and its import consolidated. Finally, the layout is updated to designate the '/gateway' route as light-only.

Changes

File(s)	Change Summary
`packages/web/docs/package.json` `package.json`	Updated dependency and package manager versions: - `@theguild/components` version changed from `9.2.0` to `9.3.2` - Project `packageManager` updated from `[email protected]` to `[email protected]`
`packages/web/docs/src/app/gateway/gateway-feature-tabs.tsx` `packages/web/docs/src/app/gateway/gateway-marquee-rows.tsx` `packages/web/docs/src/app/gateway/page.tsx` `packages/web/docs/src/app/layout.tsx`	Introduced new gateway components and page: - Added `GatewayFeatureTabs` (with new type definitions and SVG icon components) - Added `GatewayMarqueeRows` with link shuffling logic - Created `HiveGatewayPage` with SEO metadata and a hero section - Updated layout to include the `/gateway` route among "light only" pages
`packages/web/docs/src/app/page.tsx`	Replaced the use of the `FeatureTabs` component with the new `LandingPageFeatureTabs` component in the main index page
`packages/web/docs/src/components/feature-tabs.tsx` `packages/web/docs/src/components/info-card.tsx` `packages/web/docs/src/components/landing-page-feature-tabs.tsx` `packages/web/docs/src/components/stud.tsx`	Component updates and refactoring: - Refactored `FeatureTabs` to include a new context, updated types/interfaces, and introduced `ActiveHighlightImage` and related hooks - Updated `info-card.tsx` to import `Stud` from `@theguild/components` - Added new `LandingPageFeatureTabs` with specific feature highlights - Removed the legacy `Stud` component

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant HP as HiveGatewayPage
    participant LC as LandingPageContainer
    participant H as Hero & Decoration
    participant G as GatewayFeatureTabs
    participant C as Other UI Components

    U->>HP: Request Hive Gateway page
    HP->>LC: Render structured layout
    LC->>H: Render hero section with branding
    HP->>G: Render feature tabs component
    G->>C: Integrate additional UI elements (e.g., call-to-action)
    C-->>U: Display complete page

sequenceDiagram
    participant U as User
    participant G as GatewayFeatureTabs
    participant Ctx as FeatureTabsContext

    U->>G: Click on a feature tab
    G->>Ctx: Update active highlight state
    Ctx-->>G: Return updated highlight data
    G->>U: Render updated feature details

Tip

🌐 Web search-backed reviews and chat

We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
You can disable this feature by setting web_search: false in the knowledge_base settings.
Please share any feedback in the Discord discussion.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 8

🧹 Nitpick comments (6)

packages/web/docs/src/components/feature-tabs.tsx (1)
93-105: Improve readability of documentation link transformation.

The conditional logic that transforms a string into an object could be more concise with a small helper or an inline approach. Keeping it purely functional helps readability.
- if (typeof documentationLink === 'string') {
-   documentationLink = {
-     text: 'Learn more',
-     href: documentationLink,
-   };
- }
+ const linkProps = typeof documentationLink === 'string'
+   ? { text: 'Learn more', href: documentationLink }
+   : documentationLink;
packages/web/docs/src/app/gateway/page.tsx (1)
63-94: Decorative SVG usage is appropriate.

Using DecorationIsolation around SVG icons preserves layering. Make sure to provide alternative text or aria-hidden if these images are decorative only, for better accessibility.
<svg
  className="pointer-events-none -z-50 size-0"
+ aria-hidden="true"
  width="192"
  height="296"
  viewBox="0 0 192 296"
>
…
</svg>
packages/web/docs/src/app/gateway/gateway-marquee-rows.tsx (1)

3-3: Add a link check test as planned.

The TODO comment suggests verifying that none of these links are 404. Adding a link validator test or a CI check would help ensure correctness and avoid broken references.
packages/web/docs/src/app/gateway/gateway-feature-tabs.tsx (2)
5-6: Consider using an enum for tab types.

The string literal type for tabs could be better represented as an enum to ensure type safety and maintainability.
-type Tab = 'Observability & Performance Monitoring' | 'Security & Access Control';
+enum Tab {
+  ObservabilityAndPerformance = 'Observability & Performance Monitoring',
+  SecurityAndAccess = 'Security & Access Control'
+}
80-81: TODO comment needs addressing.

The TODO comment about marquee rows and timeline should be tracked in the issue tracker.

Would you like me to create an issue to track the implementation of draggable marquee rows with a connected timeline?
packages/web/docs/src/components/landing-page-feature-tabs.tsx (1)
138-146: Optimize SVG attributes.

The SVG element has redundant attributes and can be optimized.
 <svg
-  stroke="currentColor"
-  fill="currentColor"
+  fill="currentColor"
   strokeWidth="0"
   viewBox="0 0 256 256"
   height="24"
   width="24"
-  xmlns="http://www.w3.org/2000/svg"
 >

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f6d2aee and 17b6ebf.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (13)

packages/web/docs/package.json (1 hunks)
packages/web/docs/src/app/case-studies/(posts)/layout.tsx (1 hunks)
packages/web/docs/src/app/case-studies/case-studies-styles.css (1 hunks)
packages/web/docs/src/app/gateway/gateway-feature-tabs.tsx (1 hunks)
packages/web/docs/src/app/gateway/gateway-marquee-rows.tsx (1 hunks)
packages/web/docs/src/app/gateway/orchestrate-your-way.tsx (1 hunks)
packages/web/docs/src/app/gateway/page.tsx (1 hunks)
packages/web/docs/src/app/layout.tsx (1 hunks)
packages/web/docs/src/app/page.tsx (2 hunks)
packages/web/docs/src/components/feature-tabs.tsx (5 hunks)
packages/web/docs/src/components/info-card.tsx (1 hunks)
packages/web/docs/src/components/landing-page-feature-tabs.tsx (1 hunks)
packages/web/docs/src/components/stud.tsx (0 hunks)

💤 Files with no reviewable changes (1)

packages/web/docs/src/components/stud.tsx

✅ Files skipped from review due to trivial changes (2)

packages/web/docs/src/app/case-studies/(posts)/layout.tsx
packages/web/docs/src/components/info-card.tsx

🧰 Additional context used

📓 Path-based instructions (10)

packages/web/docs/src/app/layout.tsx (1)

Pattern packages/web/docs/**: The main landing page and documentation website. It's built using TypeScript, Tailwind, NextJS and Nextra.