Ship Wave-1 SEO content: privacy-first, self-hosted, text-to-video, RAG, GPU FAQ - #4778
Merged
Conversation
…AG, GPU FAQ Adds five S-effort backlog rows from marketing/seo/CONTENT_KEYWORD_STRATEGY.md Wave 1: /solutions/privacy-first, /solutions/self-hosted, /tasks/text-to-video, /tasks/rag, and a "do I need a GPU" FAQ row. All are new rows in existing data modules, matching established page-entry shapes and verified against real template slugs and models already shipped in modelEntries.ts. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BBVKkDbrQ7PfFkToiAfViR
georgi
enabled auto-merge (squash)
August 7, 2026 16:44
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BBVKkDbrQ7PfFkToiAfViR
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
2 participants
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
marketing/seo/CONTENT_KEYWORD_STRATEGY.md, which already had an accurate "what already exists" audit and a prioritized Wave 1 backlog of S-effort items (new rows in existing data modules, no new routes needed)./solutions/privacy-first(landingEntries.ts) — local-first/no-data-leaves-your-machine positioning/solutions/self-hosted(landingEntries.ts) — Docker/docker-compose.ymlself-host story, sourced from documented deploy facts/tasks/text-to-video(taskEntries.ts) — models verified againstmodelEntries.ts(Veo 3.1, Sora 2, Kling 2.6, Wan 2.6)/tasks/rag(taskEntries.ts) — retrieval-augmented generation hub, matched to the realchat-with-your-documentstemplatedo-i-need-a-gpuFAQ row (faqEntries.ts)marketing/seo/CONTENT_KEYWORD_STRATEGY.md./alternatives/comfyui-for-*pages) — those need/alternatives/[slug]route changes beyond a data row, out of scope for this pass.Note:
docs/SEO_STRATEGY.mdis stale relative to the current site (it still describes ~13 indexed pages; the site now ships ~100+ across models/providers/tasks/solutions/templates/apps/showcase/blog/faq engines).marketing/seo/CONTENT_KEYWORD_STRATEGY.mdis the accurate, current source of truth and is what this PR builds from — a full rewrite ofdocs/SEO_STRATEGY.mdis a good follow-up but out of scope here.Test plan
npx tsc --noEmitinmarketing/— cleannpm run lintinmarketing/— clean (only pre-existing, unrelated warnings)image-enhanceandchat-with-your-documentstemplate slugs exist intemplateEntries.generated.tsnext buildfull static generation (not run — large build, typecheck+lint sufficient per repo convention for data-only changes)Generated by Claude Code