From 9ad9277729b92f0d86d5f3d1a72caedca611266c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20Zieli=C5=84ski?= Date: Sun, 3 May 2026 22:11:25 +0200 Subject: [PATCH] docs: lift "Where to start" up under the hero, scroll to in-page tiles MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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
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
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. --- docs/index.html | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/docs/index.html b/docs/index.html index d39d364b0..6f9dc7c17 100644 --- a/docs/index.html +++ b/docs/index.html @@ -26,7 +26,25 @@

The pieces of WordPress, without the dependencies.

Quickstart → Take the tutorial - Browse components + Browse components +
+
+ +
+

Where to start

+ +
+ + I want to learn the toolkit. + Build a real content importer across four short chapters. We'll start with one HTML rewrite and finish with a ZIP-packaged WXR export. Every code block runs in the browser; every chapter ends with something you can keep. + ~45 minutes → + + + + I'm here to look something up. + Eighteen component pages, each with a one-line definition, a minimal runnable example, refinements, the pitfalls people actually trip on, and links back to the tutorial chapters where the concept first appears. + Browse all components ↓ +
@@ -48,7 +66,7 @@

The shape of it

Eighteen components. Each is a small library focused on one job, distributable as its own Composer package, depending only on PHP itself plus other toolkit components — no Composer packages outside the wp-php-toolkit/* family, no PHP extensions beyond json and mbstring.

-
+

All eighteen components

Content and migration

@@ -86,24 +104,6 @@

WordPress runtime support

-
-

Where to start

- -
- - I want to learn the toolkit. - Build a real content importer across four short chapters. We'll start with one HTML rewrite and finish with a ZIP-packaged WXR export. Every code block runs in the browser; every chapter ends with something you can keep. - ~45 minutes → - - - - I'm here to look something up. - Eighteen component pages, each with a one-line definition, a minimal runnable example, refinements, the pitfalls people actually trip on, and links back to the tutorial chapters where the concept first appears. - Browse all components → - -
-
-

The toolkit in one line each