feat: add flaglint-go callout to homepage#18
Conversation
Two small additions, not a redesign — the homepage is heavily hand-tuned and JS/npm-specific throughout (hero copy, terminal demo, workflow steps all show npx flaglint), so a full "Go" section would fight the existing design rather than fit it: - A secondary CTA in the hero row, same btn-sm styling as the existing "View audit docs" link, pointing to /docs/go/ - A "Go CLI" footer link alongside the existing Docs/Blog links Verified in-browser: both links render correctly and resolve to the Go docs section. Signed-off-by: Krishan Kant Sharma <krishansharma0327@gmail.com>
|
Warning Review limit reached
Next review available in: 10 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ 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 |
Deploying flaglint with
|
| Latest commit: |
80469ba
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d5cec24e.flaglint.pages.dev |
| Branch Preview URL: | https://feat-homepage-go-callout.flaglint.pages.dev |
Feedback: the footer was already at 9 links before this addition — a 10th
made it noticeably crowded. The hero CTA ("Using Go? Try flaglint-go →")
already covers the discovery goal more prominently anyway, so the footer
addition was redundant.
Signed-off-by: Krishan Kant Sharma <krishansharma0327@gmail.com>
2 participants
Summary
Two small additions to the homepage, not a redesign — the page is heavily hand-tuned and JS/npm-specific throughout (hero copy, terminal demo, workflow steps all show
npx flaglint), so a full "Go" section would fight the existing design rather than fit it:btn-smstyling of "View audit docs", pointing to/docs/go/Test plan
npm run build— clean, 90 pages