frontend(feat): add /payload-custom-components SEO landing page#154
Open
Ducksss wants to merge 1 commit into
Open
frontend(feat): add /payload-custom-components SEO landing page#154Ducksss wants to merge 1 commit into
Ducksss wants to merge 1 commit into
Conversation
Targets the "Payload custom components" organic query (scan flagged organic at 26/100). The page disambiguates the term (admin UI components vs content blocks), scopes the tool honestly, explains the four wiring edits (config/renderer/types/import-map) in founder-readable language, shows the install path, and links to relevant component docs + commands. - New crawlable route with keyword title/description, canonical, and TechArticle + breadcrumb + page-scoped FAQPage JSON-LD - Page-unique prose (not the homepage copy) plus a query-specific FAQ; reuses only the factual ledger table and catalog data - Registered in sitemap.ts and llms.txt; footer Product link plus contextual in-body links from /about and the homepage wiring section - Added to the e2e route smoke-test list Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Deployment failed with the following error: Learn More: https://vercel.com/ducksss-projects?upgradeToPro=build-rate-limit |
Owner
Author
|
Current action: keep open on |
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.
Summary
Adds a focused, crawlable SEO landing page at
/payload-custom-components, targeting the "Payload custom components" organic query (a scan flagged organic at 26/100 and named this page as the top quick-win).The page is a from-scratch, on-brand design — not a homepage clone:
Terminalreplaying a realpayload-components addrun.WiringLedger+ receipts.DemoFitFrame, each linking its docs + showing a copyable install command.FAQPageJSON-LD) and an honest MIT close.Crawlability & links
sitemap.tsand/llms.txt/aboutand the homepage wiring sectionTechArticle+ page-scopedFAQPagestructured data; keyword title, description, canonicalReuse, not rebuild
Composes existing primitives (
Terminal,WiringLedger,ComponentPreviewThumb/DemoFitFrame,CommandCopyButton, section primitives,MaintainerNote) andsite.tsdata. Page-local prose keeps it distinct from the homepage (no duplicate-content). No new components.Non-goals respected
No invented numbers/logos/pricing, no signup gating; MIT, community-first framing intact.
Tests
frontend.e2e.spec.ts)dev): tsc + lint clean; geo crawl/JSON-LD, llms.txt, route smoke, landing-sections, nav-active all green; no horizontal overflow from page content🤖 Generated with Claude Code