Skip to content

Docs site: Fueled rebrand (headstartwp.fueled.com) - #952

Draft
jakemgold wants to merge 1 commit into
developfrom
docs/fueled-rebrand
Draft

Docs site: Fueled rebrand (headstartwp.fueled.com)#952
jakemgold wants to merge 1 commit into
developfrom
docs/fueled-rebrand

Conversation

@jakemgold

Copy link
Copy Markdown
Member

Summary

Rebrands the Docusaurus docs site for the Fueled era and visually aligns it with the new main site at headstartwp.fueled.com (the old headstartwp.10up.com domain now 301s there).

Site chrome

  • Site title/url → headstartwp.fueled.com; GA4 (GT-WRDG786, loaded in production builds only) replaces the GTM container
  • Navbar: "About HeadstartWP" CTA linking to the main site
  • Hero: lavender wash + lattice graphic mirroring the main site's hero (responsive tiers; search dropdown unaffected)
  • Footer: three nav columns (Docs & Community / HeadstartWP / Fueled (formerly 10up)) plus a bottom band mirroring the main site's footer (MIT Licensed / News / Issues, Fueled lockup, GitHub + LinkedIn)
  • Typography: IBM Plex Sans + IBM Plex Sans Condensed; primary color ramp keyed to the main site's palette

Brand/content pass

  • Legacy 10up CTA banner replaced with the current org-standard Fueled banner (same markup as 10up/classifai) in the root and package READMEs
  • Root README docs links point at headstartwp.fueled.com
  • philosophy.md now says "HeadstartWP" (its prose predated the product rename), with Fueled credited once
  • Pages-router quick-tutorial: "At Fueled (formerly 10up), we strongly believe…"
  • Guide section renamed "Documentation" → "Developer Guide" (navbar, footer, home grid card); the /learn route is unchanged

Deliberately unchanged: github.com/10up repo URLs, the js1.10up.com demo backend, the @10up/next-redis-cache-provider package name, the __10up__HEADLESS_CONFIG identifier, and the org-standard support-level sentence (ClassifAI's README still carries the same one).

Notes for reviewers

  • Merging develop → trunk auto-deploys the site (deploy-docs.yml fires on any trunk push). This PR targets develop, so nothing deploys until that later merge.
  • The old GTM container also injected the HubSpot tracker (portal 49619948); switching to GA4 drops it. Flagging in case that tracking is wanted — easy to re-add.
  • Tested with a CI-parity local build (Node 20, root install, build:packages, full typedoc): all routes green, search verified returning results from both /learn and /api.
  • If you check a production build locally, don't judge search through docusaurus serve — it mishandles the search plugin's query-stringed index fetch (302 → 404) and the search spinner never resolves. Any plain static server (e.g. python3 -m http.server) behaves like GitHub Pages and works.
  • Out of scope but spotted for a future package-source pass: TSDoc examples in packages/core/src/dom/index.ts still import from the stale @10up/headless-next name, and AbstractFetchStrategy's error string says "10up's Headless WordPress plugin."

🤖 Generated with Claude Code

Visual/config alignment with the new main site:
- Title/url -> headstartwp.fueled.com; GA4 (production-only) replaces GTM
- Navbar 'About HeadstartWP' CTA; hero lavender wash + lattice treatment
- Footer: 3 nav columns + Fueled bottom band mirroring the main site
- IBM Plex Sans / Plex Sans Condensed typography, new primary ramp

Brand reference pass:
- Org-standard Fueled CTA banner (per 10up/classifai) in root+package READMEs
- Root README docs links -> headstartwp.fueled.com
- philosophy.md says HeadstartWP (pre-rename prose); Fueled credited once
- Pages-router quick-tutorial: 'At Fueled (formerly 10up), ...'
- Unchanged by design: github.com/10up URLs, js1.10up.com demo backend,
  @10up/next-redis-cache-provider package name, __10up__HEADLESS_CONFIG

Naming: guide section 'Documentation' -> 'Developer Guide' (navbar,
footer, home grid); /learn route unchanged.
@changeset-bot

changeset-bot Bot commented Jul 26, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: d51ce16

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel

vercel Bot commented Jul 26, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
headstartwp-app-router Ready Ready Preview, Comment Jul 26, 2026 11:46pm
headstarwp Ready Ready Preview, Comment Jul 26, 2026 11:46pm

Request Review

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