feat(site): featured extensions homepage section + constellation motif#3883
Merged
Conversation
Add a "Take your graph further" Featured Extensions section to the homepage and reuse the WordPress.org banner constellation motif across the site's branded surfaces. - New shared `Constellation` component: deterministic (seeded PRNG, memoized — no hydration mismatch), brand-agnostic (tints via the surrounding `.theme-*` `--primary`), with `opacity`/`intensity` knobs. - New `HomepageExtensions` section wired into `front-page.js`, sourced from the canonical `featuredExtensions` data. - Constellation backgrounds added to the homepage hero, the /extensions archive featured cards, each extension's dedicated-page hero, and the Extensions nav-dropdown hover state. Depends on the extension landing pages / featured-extensions data from the IDE rebuild branch; open as a follow-up PR after that merges. (cherry picked from commit cebacc45dafe443118e098cd7048182c505bedf4)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
jasonbahl
added a commit
that referenced
this pull request
Jun 4, 2026
Sync main (split PRs #3877/#3878/#3879 + asset-pipeline #3880/#3882/#3883) into the IDE rebuild branch. Conflicts were all IDE release-metadata + the plugin header; resolved as: - package.json / wpgraphql-ide.php Version / readme.txt Stable tag: 4.5.0 (the release-please manifest value; release-please bumps to 5.0.0 at release — the in-repo version tracks the last release per the plugin's CLAUDE.md). - CHANGELOG.md / readme.txt changelog: union — keep the 5.0.0 notes AND main's released 4.5.0 entry. - Requires at least: 6.1 (not the 7.0 the branch had staged). WordPress 7.0's i18n features (.l10n.php 6.5, JIT textdomain 6.7) degrade gracefully and no runtime gate gates on 7.0, so there's no reason to lock out current installs. Dropped the "raised floor to 7.0" breaking-change note and aligned CLAUDE.md + i18n docs to 6.1. - Tested up to: 7.0 (WordPress 7.0 is released).
jasonbahl
added a commit
to josephfusco/wp-graphql
that referenced
this pull request
Jun 4, 2026
Sync main (split PRs wp-graphql#3877/wp-graphql#3878/wp-graphql#3879 + asset pipeline wp-graphql#3880/wp-graphql#3882/wp-graphql#3883) onto the IDE rebuild branch, on top of Joe's floor/CI commits (floor 6.1, WP 7.0 CI coverage + tested-up-to). Conflicts (all IDE release metadata) resolved as: - Version / Stable tag / package.json: 4.5.0 (release-please manifest value; release-please bumps to 5.0.0 at release — in-repo version tracks last release per the plugin's CLAUDE.md). - CHANGELOG.md / readme.txt changelog: union — keep the 5.0.0 notes AND main's released 4.5.0 entry. Dropped the now-inaccurate "raised floor to 7.0" breaking-change note (Joe set the floor to 6.1) and the 7.0-floor framing in the i18n docs. - Requires at least: 6.1 / Tested up to: 7.0 — kept Joe's values.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ships the unshipped website work from
feat/extensions-constellation-branding(commitcebacc45d) as the follow-up its own message called for — now that the extension landing pages, sibling-brand logos, andfeaturedExtensionsdata it depends on are all onmain.What this adds
Constellationcomponent (new) — the glowing star-node motif from the WordPress.org plugin banners, as a reusable background layer. Brand-agnostic (tints via the surrounding.theme-*--primary/currentColor), withopacity/intensityknobs. Deterministic: a seeded PRNG (noMath.random) + module-level memo cache, so server and client render identically (no hydration mismatch) and repeated instances are free.HomepageExtensionssection (new) — a "Take your graph further" featured-extensions block wired intofront-page.js, sourced from the canonicalfeaturedExtensionsdata (stays in sync with the header dropdown and/extensionsarchive). Each card carries its product'stheme-*scope so its logo, constellation field, and glow render in the sibling brand accent./extensionsarchive featured cards, each extension's dedicated-page hero, and the Extensions nav-dropdown hover state.Scope
9 files, +313/−21, website-only (
websites/wpgraphql.com/). The source branch is the full IDE-rebuild stack; this PR isolates just the genuinely-unshipped branding work via cherry-pick, leaving the IDE plugin changes to their own PR (#3784).Verification
main.main(Constellationis new;featuredExtensions,SectionHeading, theui/button, and the logo marks already shipped).featuredExtensionsdata shape matches whatHomepageExtensionsdestructures (name, href, description, theme, Mark).Constellationis SSR-safe (noMath.random/Date/windowat render).