fix(docs): increase gap between feature grid and action buttons on landing page

[jdx]

Summary

• Increase margin-bottom on .usage-hero-features from 2rem to 8rem so feature tooltips don't overlap the "Get Started" button

Problem

On the landing page, hovering over bottom-row feature buttons (e.g., "Completions") shows a tooltip that covers the "Get Started" action button, making it difficult to click.

Fix

Increase the gap between the feature button grid and the action buttons so tooltips have room to render without overlapping.

Test plan

• Hover over bottom-row feature buttons → tooltips render fully without covering "Get Started"

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR fixes a UI interaction bug where tooltips on the landing page were blocking clicks on the "Get Started" button beneath them by making the tooltips non-interactive.

Changes:

• Added pointer-events: none to tooltip styling to allow click-through behavior

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Summary of Changes

Hello @jdx, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a user experience issue on the landing page where informational feature tooltips were unintentionally blocking clicks on the "Get Started" action button. By making the tooltips non-interactive to pointer events, users can now seamlessly click through them to access underlying elements, enhancing the overall navigability of the page.

Highlights

• CSS Styling: Added the pointer-events: none CSS property to the .usage-hero-feature-tooltip class. This change prevents the tooltips from intercepting mouse clicks, allowing interaction with elements positioned underneath them.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request addresses a UI issue where feature tooltips could obstruct underlying elements, specifically the 'Get Started' button. The solution of adding pointer-events: none to the tooltip's CSS is a clean and correct way to solve this problem, allowing mouse events to pass through the non-interactive tooltip. The change is well-implemented and effectively resolves the bug.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.57%. Comparing base (35bdd17) to head (21bef65).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #482   +/-   ##
=======================================
  Coverage   70.57%   70.57%           
=======================================
  Files          47       47           
  Lines        6597     6597           
  Branches     6597     6597           
=======================================
  Hits         4656     4656           
  Misses       1264     1264           
  Partials      677      677           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cursor]

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

^{Bugbot Autofix is ON, but a Cloud Agent failed to start.}

[cursor]

Described fix not implemented - missing pointer-events property

Medium Severity

The PR description claims to add pointer-events: none to .usage-hero-feature-tooltip to let clicks pass through tooltips, but this was never implemented. The actual change only increases margin-bottom from 2rem to 8rem, which is a fragile workaround that relies on specific spacing rather than the robust semantic fix described. Tooltips can still intercept clicks if they extend beyond the margin boundary.