Skip to content

fix(docs): give homepage inline code chips breathing room#29

Merged
SutuSebastian merged 1 commit into
mainfrom
fix/docs-home-inline-code-spacing
Jul 20, 2026
Merged

fix(docs): give homepage inline code chips breathing room#29
SutuSebastian merged 1 commit into
mainfrom
fix/docs-home-inline-code-spacing

Conversation

@SutuSebastian

Copy link
Copy Markdown
Contributor

Summary

  • Add mx-0.5 / px-1.5 around Hero and Seams inline <code> chips so muted backgrounds don't sit flush against neighboring words
  • Bump Seams heading→lede spacing (mt-4mt-6)

Test plan

  • Homepage Hero: space around persistSource looks even
  • Homepage Seams: space around createStorage / persistSource, and more gap under the heading
  • docs label present so Deploy docs runs on merge

@SutuSebastian SutuSebastian added the docs Public docs site (apps/docs) — merge deploys /persist via FTP label Jul 20, 2026
@changeset-bot

changeset-bot Bot commented Jul 20, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 5a1bfc1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Add outer margin/padding around Hero and Seams code chips, and open the Seams heading→lede gap so the muted backgrounds don't sit flush against neighboring words.
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@SutuSebastian, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 55436a26-a0a7-4408-a663-d6ab9d993141

📥 Commits

Reviewing files that changed from the base of the PR and between 4ced227 and 5a1bfc1.

📒 Files selected for processing (2)
  • apps/docs/pages/_home/Hero.astro
  • apps/docs/pages/_home/Seams.astro
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/docs-home-inline-code-spacing

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.

@SutuSebastian
SutuSebastian force-pushed the fix/docs-home-inline-code-spacing branch from 7fc4ecf to 5a1bfc1 Compare July 20, 2026 13:56
@SutuSebastian
SutuSebastian merged commit 1a4f458 into main Jul 20, 2026
13 checks passed
@SutuSebastian
SutuSebastian deleted the fix/docs-home-inline-code-spacing branch July 20, 2026 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Public docs site (apps/docs) — merge deploys /persist via FTP

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant