Repository navigation
Release: /videos public with a page per video and SEO fixes - #320
Merged
Merged
Conversation
… findings Make the page public (VIDEOS_PAGE_PUBLIC = true): indexable, in the sitemap and linked from the Resources menu. Give every video its own page at /videos/[slug] with the player, summary, description, topic links, related videos and VideoObject schema. Card, Quick starts, theatre and featured titles now link to it, so crawlers reach every video from the HTML. The thumbnail still plays inline. Also from the audit: - Page title "Container Security Videos: SBOM and VEX", H1 "Container security videos", longer meta description and lead. - Quick starts is an H2; the filter sheet title is no longer a heading. - Listing schema is a CollectionPage plus an ItemList of links to the video pages. - Sitemap lists /videos (dated by the newest video) and each video page. - llms.txt lists Videos; page registry gets a /videos/[slug] template row.
The thumbnail is the first column and has a custom cell, which Payload does not wrap in its row link, so nothing in a row was clickable. The thumbnail now links to the edit page and a new title cell does the same. Also refresh two comments that still said videos have no page of their own, and regenerate the import map.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This branch was previously deployed
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
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.
What ships
/videos goes public
VIDEOS_PAGE_PUBLICis nowtrue. The page is indexable, listed in the sitemap and linked from the Resources menu (Events group), all together.A page for every video:
/videos/[slug]VideoObjectschema.notFound(). On production this may serve a soft 200 like the other[slug]routes (see docs/operations/INCIDENTS.md and the RENDER-01 note in the SEO SOP).SEO audit fixes
CollectionPageplus anItemListof links to the video pages (theVideoObjectnow lives on each video page)./videos(dated by the newest video) and every video page.llms.txtlists Videos./videos/[slug]template row.Deploy notes
main. No migrations, no new env vars.apps/cms,pnpm exec tsx --env-file=.env scripts/seed-page-registry.ts(production run, needs the operator).VIDEOS_SOURCE=cmsis still off, so the pages read the code catalogue plus the YouTube feed./videosand a few video pages in Search Console and watch the Video indexing report.Checks
verify:page-registrypasses.buildandverify:copy(the build needs the production CMS); CI runs them.Not covered
/videosfrom blog and product pages are editorial work.