Skip to content

docs: lift "Where to start" under the hero, scroll-to-tiles for "Browse all components"#259

Merged
adamziel merged 1 commit intotrunkfrom
docs-landing-where-to-start
May 3, 2026
Merged

docs: lift "Where to start" under the hero, scroll-to-tiles for "Browse all components"#259
adamziel merged 1 commit intotrunkfrom
docs-landing-where-to-start

Conversation

@adamziel
Copy link
Copy Markdown
Collaborator

@adamziel adamziel commented May 3, 2026

Summary

Two small landing-page tweaks at https://wordpress.github.io/php-toolkit/:

  1. Moved the "Where to start" two-doors block up. It used to sit below the 18-component grid, so visitors had to scroll past every tile before getting the tutorial-vs-reference choice. Now it's right under the hero — the high-level decision is the second thing you see.
  2. "Browse all components ↓" now scrolls to the in-page tiles via #components instead of navigating away to /reference/. The hero's "Browse components" CTA gets the same anchor for consistency. Arrow flipped from → to ↓ to match scroll-down semantics.

Added id="components" to <section class="all-components"> so the anchor resolves.

New section order

hero (CTAs: Quickstart · Take the tutorial · Browse components ↓)
Where to start                              ← moved up
The problem
The shape of it
All eighteen components  (id="components")  ← scroll target
The toolkit in one line each
Credits
How the runnable examples work

No other reordering, no CSS changes.

🤖 Generated with Claude Code

The landing page used to put the two-doors "Where to start" block
below the eighteen-component grid, so visitors had to scroll past
every tile before getting the high-level "tutorial vs reference"
choice. Two small changes:

  1. Moved <section class="two-doors"> to immediately follow the
     hero, so the choice between learning and looking-something-up
     is visible without scrolling.

  2. Pointed the "I'm here to look something up" door's link
     (Browse all components ↓) at #components — an anchor on the
     in-page component grid — instead of /reference/. Now it
     scrolls down to the tiles instead of navigating away. The
     hero's "Browse components" CTA gets the same anchor for
     consistency.

Added id="components" to <section class="all-components"> so the
anchor resolves. Arrow on the door's call-to-action changed from
→ to ↓ to match the scroll-down semantics.

No other section reordering, no CSS changes.
@adamziel adamziel merged commit 6a78f1a into trunk May 3, 2026
27 of 28 checks passed
@adamziel adamziel deleted the docs-landing-where-to-start branch May 3, 2026 20:11
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