Skip to content

site: make the OSS-to-Pro path explicit#65

Open
justin808 wants to merge 2 commits intomainfrom
jg-codex/site-funnel
Open

site: make the OSS-to-Pro path explicit#65
justin808 wants to merge 2 commits intomainfrom
jg-codex/site-funnel

Conversation

@justin808
Copy link
Copy Markdown
Member

@justin808 justin808 commented Mar 26, 2026

Closes #64

Summary

  • add a dedicated OSS-to-Pro upgrade section to the homepage flow
  • make the homepage CTA and footer docs links point users through comparison and upgrade docs
  • add an examples-page card for teams evaluating when to move from OSS to Pro

Verification

  • git diff --check
  • npm --prefix prototypes/docusaurus run typecheck
  • npm --prefix prototypes/docusaurus run build (blocked in this workspace because the checked-out snapshot does not include prototypes/docusaurus/docs/; the issue body explains the limitation and this PR avoids the overlapping sync-script files already in PR Add docs audit severities, CI report upload, and dead Pro-link cleanup #61)

Note

Low Risk
Low risk: changes are limited to Docusaurus site navigation/content and CSS layout updates, with no backend, auth, or data-handling impact.

Overview
Makes the OSS→Pro journey explicit across the marketing site by routing users through a new comparison-first flow.

Updates the homepage CTAs and copy to point to docs/getting-started/oss-vs-pro, adds a dedicated UpgradeSection with links to the comparison and docs/pro/upgrading-to-pro, and adds an “Move from OSS to Pro” card on the examples page (with minor grid/CSS adjustments to fit the new cards).

Written by Cursor Bugbot for commit 9656181. This will update automatically on new commits. Configure here.

Summary by CodeRabbit

  • New Features
    • Added OSS vs Pro comparison guide link in the footer and homepage CTA.
    • Introduced a dedicated "OSS to Pro" upgrade section on the homepage with step-by-step links.
    • Added an "Upgrade path" decision card to the evaluation/decision grid.
    • Adjusted homepage and decision-grid layouts to better display three-column cards on larger screens.

@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 26, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 52d3df78-d52d-4c0b-8923-e612a7c6a665

📥 Commits

Reviewing files that changed from the base of the PR and between ae60835 and 9656181.

📒 Files selected for processing (1)
  • prototypes/docusaurus/src/pages/index.module.css
🚧 Files skipped from review as they are similar to previous changes (1)
  • prototypes/docusaurus/src/pages/index.module.css

Walkthrough

Added OSS-to-Pro comparison and upgrade guidance sitewide: footer links, updated home messaging and hero CTA, a new UpgradeSection on the homepage, an extra "Upgrade path" card in examples, and related CSS grid adjustments for layout.

Changes

Cohort / File(s) Summary
Navigation & Configuration
prototypes/docusaurus/docusaurus.config.ts
Added two footer navigation items linking to /docs/getting-started/oss-vs-pro and /docs/pro/upgrading-to-pro.
Examples Page — Layout & Content
prototypes/docusaurus/src/pages/examples.module.css, prototypes/docusaurus/src/pages/examples.tsx
Changed .decisionGrid from 2 to 3 columns; added a new "Upgrade path" entry to evaluationPaths which renders an additional card linking to OSS-vs-Pro docs.
Home Page — Styling
prototypes/docusaurus/src/pages/index.module.css
Added .upgradeGrid class (2-column grid) and included it in the shared grid selector and responsive single-column rule.
Home Page — Content & Components
prototypes/docusaurus/src/pages/index.tsx
Reworded Pro/OSS messaging to emphasize comparing first; changed hero CTA to /docs/getting-started/oss-vs-pro; added a new local UpgradeSection() component and inserted it into the Home render sequence.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 I nibbled docs and hopped a while,
Added links and polished style,
Three-card rows and a guiding show,
From OSS to Pro, the pathways glow,
A tiny rabbit cheers: onward we go! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'site: make the OSS-to-Pro path explicit' clearly and concisely summarizes the primary change: introducing an explicit upgrade path from OSS to Pro on the documentation site.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jg-codex/site-funnel

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix prepared a fix for the issue found in the latest run.

  • ✅ Fixed: Upgrade grid missing from responsive media query
    • Added .upgradeGrid to the existing @media (max-width: 996px) single-column grid rule so the upgrade cards stack correctly on smaller viewports.

Create PR

Or push these changes by commenting:

@cursor push c7b5f4c249
Preview (c7b5f4c249)
diff --git a/prototypes/docusaurus/src/pages/index.module.css b/prototypes/docusaurus/src/pages/index.module.css
--- a/prototypes/docusaurus/src/pages/index.module.css
+++ b/prototypes/docusaurus/src/pages/index.module.css
@@ -318,6 +318,7 @@
   .personaGrid,
   .flowGrid,
   .migrationGrid,
+  .upgradeGrid,
   .quoteGrid {
     grid-template-columns: 1fr;
   }

You can send follow-ups to this agent here.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 26, 2026

Cloudflare preview deployed.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@prototypes/docusaurus/docusaurus.config.ts`:
- Around line 136-137: Before merging the change to docusaurus.config.ts that
modifies the navbar links ({label: 'Compare OSS and Pro', to:
'/docs/getting-started/oss-vs-pro'} and {label: 'Upgrade to Pro', to:
'/docs/pro/upgrading-to-pro'}), obtain explicit approval from the repository
maintainers as required by the project's config-change policy: add a comment in
the PR tagging the maintainers or the designated approver, wait for their
explicit sign-off, and update the PR description to note that this Docusaurus
config edit has been approved before proceeding to merge.

In `@prototypes/docusaurus/src/pages/index.module.css`:
- Around line 190-192: The .upgradeGrid CSS defines two columns and isn’t
included in the responsive collapse, causing cramped cards on small screens;
update the responsive `@media` (max-width: 996px) block (also apply same change
for the other occurrence around the 317–323 region) to include .upgradeGrid and
override its grid-template-columns to a single-column layout (e.g., repeat(1,
minmax(0, 1fr))) so the OSS-to-Pro cards stack on mobile.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 897d14f0-013a-454b-b3ca-628a6e02b348

📥 Commits

Reviewing files that changed from the base of the PR and between 7fd228b and ae60835.

📒 Files selected for processing (5)
  • prototypes/docusaurus/docusaurus.config.ts
  • prototypes/docusaurus/src/pages/examples.module.css
  • prototypes/docusaurus/src/pages/examples.tsx
  • prototypes/docusaurus/src/pages/index.module.css
  • prototypes/docusaurus/src/pages/index.tsx

Comment on lines +136 to +137
{label: 'Compare OSS and Pro', to: '/docs/getting-started/oss-vs-pro'},
{label: 'Upgrade to Pro', to: '/docs/pro/upgrading-to-pro'},
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Please confirm maintainers approved this docusaurus.config.ts edit first.

This repo has a specific process gate for config-file changes, so this update should be explicitly pre-approved in the PR discussion.

As per coding guidelines, "Ask first before making changes to Docusaurus configuration (prototypes/docusaurus/docusaurus.config.ts)."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@prototypes/docusaurus/docusaurus.config.ts` around lines 136 - 137, Before
merging the change to docusaurus.config.ts that modifies the navbar links
({label: 'Compare OSS and Pro', to: '/docs/getting-started/oss-vs-pro'} and
{label: 'Upgrade to Pro', to: '/docs/pro/upgrading-to-pro'}), obtain explicit
approval from the repository maintainers as required by the project's
config-change policy: add a comment in the PR tagging the maintainers or the
designated approver, wait for their explicit sign-off, and update the PR
description to note that this Docusaurus config edit has been approved before
proceeding to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Homepage/docs: make the OSS-to-Pro upgrade path explicit

1 participant