feat(seo): make linkedin required for blog authors#4593
Draft
feat(seo): make linkedin required for blog authors#4593
Conversation
…ng posts Completes the work started in #4469 by adding the linkedin field to the 25 remaining blog posts that were missed, and makes the field required in the Zod schema so future posts fail validation without it. - 15 posts get real LinkedIn URLs (Shruti Mantri, Elliot Gunn, Federico Trotta, Parham Parvizi, Ludovic Dehon, Emmanuel Darras) - 10 posts get empty string (external contributors with unconfirmed URLs) - content.config.ts: linkedin changed from optional() to required in both author and authors schemas Co-Authored-By: Claude Opus 4.6 <[email protected]>
Contributor
☁️ Cloudflare Worker Preview Deployed!🔗 https://ks-seo-blog-author-linkedin-requi-docs.kestra-io.workers.dev ## 🔦 Lighthouse Benchmark
Scores (0–100, higher is better)
Core Web Vitals (lower is better)
Legend🟢 improved · 🔻 regressed · (blank) no significant change |
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.
Summary
Completes the work started in #4469 by ensuring every blog post has the
linkedinfield and making it required in the Zod schema so future posts fail at build time without it.""(external contributors: Dario Radecic, Kevin Fleming, Anuun Chinbat, Julien Legrand — LinkedIn URLs unconfirmed)content.config.ts:linkedinchanged fromz.string().optional()toz.string()in bothauthorandauthorsschemasWhy this matters
Without this change, new blog posts can be published without a
linkedinfield, which means the JSON-LDauthor.sameAsproperty (added in #4469) would silently be missing. Making it required ensures:""is valid for external authors (the Astro template already handles falsy values gracefully)Test plan
astro syncpasses with no content collection errorssameAsfor posts with real URLssameAsfor posts withlinkedin: ""🤖 Generated with Claude Code