fixing minor template parse errors for transcript pages

[LiamRandall]

Fixes applied

#1 softwareHelp was a bare URL │ src/pages/_index/index.tsx:47 │ Wrapped as { '@type': 'CreativeWork', url: 'https://wasmcloud.com/docs/' } │

#2 isPartOf: { '@type': 'Series' } (invented │ src/theme/wasmcloud/community/video-seo.tsx:339 │ Changed to '@type': 'CreativeWorkSeries' — the schema.org-canonical CreativeWork subtype │
│ type) │ │

#3 transcribes (not a schema.org property) │ src/theme/wasmcloud/community/video-seo.tsx:336 │ Removed transcribes; replaced with associatedMedia: { '@id': videoObjectId } — a valid Article property whose range (MediaObject)

Header doc-comment also updated to match. npm run build is green.

Verified emission on build/index.html (homepage SoftwareApplication) and build/community/2026-05-27-community-meeting-transcript/index.html (transcript Article): softwareHelp is now a CreativeWork object, isPartOf is CreativeWorkSeries,
transcribes is gone, associatedMedia correctly references the meeting's #video @id.

Flag for review (per the brief's request): transcript pages still emit BOTH a BlogPosting (from Docusaurus's BlogPostPageStructuredData via blog-post-schema.tsx) and an Article (from video-seo.tsx). Both describe the same page. The Article
carries the transcript-specific relationships (associatedMedia → VideoObject, isPartOf → CreativeWorkSeries, speakers as mentions) that the BlogPosting doesn't. Two safe options to deduplicate:

1. Keep Article, drop BlogPosting on transcript permalinks — modify the BlogPostPage swizzle to skip when isTranscriptPermalink(permalink).
2. Merge — fold the transcript-specific properties into the BlogPosting and drop the Article.

Option 1 is mechanically smaller. Tell me which to take and I'll make the change.

Validators: hit the homepage (https://wasmcloud.com/) and any transcript page (e.g. https://wasmcloud.com/community/2026-05-27-community-meeting-transcript/) in validator.schema.org (https://validator.schema.org/) and Google Rich Results once
deployed; both flagged nodes should now report 0 errors. Re-run Ahrefs Site Audit issue c22e9647-5a8f-4352-8b38-14cb66d7f101 after the next deploy to confirm.

[netlify]

✅ Deploy Preview for dreamy-golick-5f201e ready!

Name	Link
🔨 Latest commit	9f35d91
🔍 Latest deploy log	https://app.netlify.com/projects/dreamy-golick-5f201e/deploys/6a2498fdabac0000083d019b
😎 Deploy Preview	https://deploy-preview-1186--dreamy-golick-5f201e.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

🔎 Structured data validation

• Mode: PR-incremental (base: origin/main)
• Files checked: 828
• JSON-LD payloads: 4708
• Errors: 0
• Warnings: 526

⚠️ Warnings by kind

Kind	Count
no about or mentions (M12 entity refs)	526

Warnings don't fail the build — they surface authoring gaps that should be backfilled when convenient (typically missing M12 about/mentions entity refs).

_{⚙️ Generated by ci_structured_data.yml • structured-data spike}