Skip to content

Visual consistency: unify cards + responsive grids + section rhythm#14

Merged
nmbrthirteen merged 1 commit into
mainfrom
feature/visual-consistency
Jul 1, 2026
Merged

Visual consistency: unify cards + responsive grids + section rhythm#14
nmbrthirteen merged 1 commit into
mainfrom
feature/visual-consistency

Conversation

@nmbrthirteen

Copy link
Copy Markdown
Owner

Conservative, additive CSS pass (all scoped under .aggregate-it) to make pages align:

  • .ai-cards grid is responsive (auto-fit) instead of fixed 4 columns.
  • Topic Hubs cards now use the same tokens as the dashboard cards (24px tabular-nums value, matching border/radius/padding, muted label) — the two card systems look identical.
  • Uniform 16px spacing below every postbox.

No PHP changes; 86 tests green.

…on rhythm

- ai-cards grid is now responsive (auto-fit) instead of a fixed 4 columns.
- Topic Hubs cards match the dashboard card tokens (24px tabular-nums value,
  same border/radius/padding, muted label) so the two card systems look identical.
- Consistent 16px spacing below every postbox for uniform section rhythm.
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nmbrthirteen, 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: 6b7e1f9f-94ac-43f5-9d26-754ea1021d1f

📥 Commits

Reviewing files that changed from the base of the PR and between 5ab6441 and 936112d.

📒 Files selected for processing (1)
  • assets/css/admin.css
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/visual-consistency

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.

@nmbrthirteen
nmbrthirteen merged commit 9f1a1a6 into main Jul 1, 2026
6 checks passed
@nmbrthirteen
nmbrthirteen deleted the feature/visual-consistency branch July 1, 2026 06:27
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.

1 participant