Skip to content

feat: add 111 outcome-named packages and redesign package pages - #5

Merged
dhruvjainin merged 1 commit into
mainfrom
feat/replacement-suites
Nov 1, 2026
Merged

dhruvjainin merged 1 commit into
mainfrom
feat/replacement-suites

Conversation

@dhruvjainin

Copy link
Copy Markdown
Contributor

What

  • Grows the catalog to 111 packages covering operations, sales, support, finance, people, IT, marketing and industry work. Each package is named for the job it does. Every package was installed and run against a live workspace.

  • Redesigns the package detail page around outcomes:

    • what happens automatically
    • who the package is for
    • getting started steps
    • common questions
    • four related packages

    Contents, inputs and the JSON move into a collapsible Technical details section.

  • Removes the resource counts and artwork from the catalog cards.

  • Serves package pages at /packages/<slug>/. public/_redirects sends the old versioned URLs there with a 301. The versioned JSON endpoints are unchanged.

  • SEO: meta descriptions are now 120–155 characters, FAQPage structured data is added, the sitemap lists only the latest version of each package, and the heading order is fixed.

  • Keeps the install-in-chat link from main on the new page.

Checks

pnpm check, pnpm lint, pnpm build (113 pages) and pnpm test (6/6) pass.

Expand the catalog to 111 packages across operations, sales, support,
finance, people, IT, marketing and industry work. Each package is named for
the job it does and validated against a live workspace.

Redesign the package detail page around outcomes: what happens
automatically, who it is for, getting started, common questions and four
related packages. Technical contents move into a collapsible section.

Serve package pages without a version in the URL, redirect the old
versioned URLs, shorten meta descriptions and add FAQ structured data.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying tulipfarm-packages with  Cloudflare Pages  Cloudflare Pages

Latest commit: 002c6ac
Status: ✅  Deploy successful!
Preview URL: https://b7148956.tulipfarm-packages.pages.dev
Branch Preview URL: https://feat-replacement-suites.tulipfarm-packages.pages.dev

View logs

@dhruvjainin
dhruvjainin merged commit 7e1e336 into main Nov 1, 2026
2 checks passed
dhruvjainin added a commit that referenced this pull request Nov 2, 2026
TulipFarm apps validate every catalog.json entry and reject the whole feed
unless page resolves to /packages/<name>/<version>/. #5 changed page to the
unversioned detail path, so the in-app Packages page has shown 'Could not
load packages' since 2026-11-01 05:33 UTC. Emit the versioned path again; it
301-redirects to the canonical page.
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