Skip to content

Unify homepage card system and enlarge header tap targets#419

Merged
Dgiordano33 merged 3 commits into
mainfrom
docs/homepage-cards-and-tap-targets
Jul 8, 2026
Merged

Unify homepage card system and enlarge header tap targets#419
Dgiordano33 merged 3 commits into
mainfrom
docs/homepage-cards-and-tap-targets

Conversation

@Dgiordano33

Copy link
Copy Markdown
Collaborator

What & why

Follow-up to an /impeccable critique of the docs. Two repo-controlled fixes it surfaced, scoped to what this repo owns outright:

1. Unify the homepage card system (index.mdx)

The homepage ran four different <Card> treatments on one page — big img cards, icon cards, plain cards, and cards with a nested #### sub-heading — which read as inconsistent and created stray heading anchors (#monitor-&-test, etc.).

Collapsed to two intentional types:

  • Hero cards (img): the blue Detect / Communicate / Resolve row — kept as the single brand moment and primary product journey.
  • Icon cards: everything else (Ready to get started, Developer Tools, Learn More, Quick Links) — icon + title + one-line description.

Specifics:

  • Dropped every nested #### double-heading (and their stray anchors); each card now has a single heading.
  • Removed the one-off cta props so no single row is styled differently.
  • Added icons to the Learn More and Quick Links rows so all non-hero cards match.
  • No copy rewrites — descriptions are unchanged apart from the removed sub-labels.

2. Enlarge header icon tap targets (style.css)

The header icon buttons (search, assistant, dark-mode, more-actions) measured 18–32px — under the 44×44 WCAG 2.5.5 minimum, worst on mobile. Added an invisible ::after hit-area overlay that expands the clickable region to 44×44 without changing the visual layout, so the theme's responsive show/hide of those buttons still applies.

Verification

  • Previewed the redesign locally with mint dev (desktop + 390px mobile): all 13 icons resolve, double-headings are gone, hero row preserved, cards stack correctly on mobile.
  • Tap-target CSS verified live against the production page: hit-tested at 390px, the target zone reads ~44px (up from 18–32px) with overflow: visible (not clipped) and zero visual shift.

Deliberately out of scope

Per the critique triage, these were parked:

  • Floating assistant bar occlusion (P1) — lives in Mintlify assistant config, not repo code.
  • Brand-blue link contrast (#0075FF = 4.21:1) — kept as-is to preserve exact brand parity with the marketing site.
  • ~85 console SyntaxErrors + a 404 (P3) — needs first-party root-cause tracing.

🤖 Generated with Claude Code

Homepage (index.mdx): collapse the four ad-hoc card treatments into two
intentional types — the blue img "hero" row (Detect/Communicate/Resolve)
and uniform icon cards everywhere else. Drop the redundant nested ####
sub-headings (and their stray heading anchors), remove the one-off `cta`
props, and add icons to the Learn More and Quick Links rows so every
non-hero card matches.

style.css: expand the small header icon buttons (search, assistant,
dark-mode, more-actions) to a 44x44 minimum touch target (WCAG 2.5.5)
via an invisible ::after hit-area overlay — no visual change, and the
theme's responsive show/hide still applies. Verified live at 390px:
targets go from 18–32px to ~44px, hit-tested.

Addresses the homepage card-consistency and mobile touch-target findings
from the /impeccable critique of the docs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
checkly-422f444a 🟢 Ready View Preview Jul 6, 2026, 12:04 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@Dgiordano33 Dgiordano33 merged commit 96c5a89 into main Jul 8, 2026
6 checks passed
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