feat(cms): add schema for Card component

[Kneesal]

Background

Need a Card component schema so editors can create card-style content blocks (image, title, description, optional link) for use in grids or lists on the web.

Expected outcome

• A Card component exists with attributes such as image, title, description, optional link/CTA, and any variant (e.g. default, featured).

Acceptance criteria

• Card component JSON schema added in CMS.
• Attributes support at least title, description, optional media and link.
• Component registered and available in sections/containers; GraphQL regenerated if contracts change.

Possible solution(s)

1. Add components/shared/card.json or sections/card.json with title, description (text), media (file or relation), link (optional), variant (optional enum).
2. Reuse for card grids by placing Card in a repeatable container or section.

References

• apps/cms/src/components/

• apps/cms/schema.graphql

• Parent: epic(cms): Experience schema for Easter-style watch page #175 Epic A (CMS)

• Related (web implementation): feat(web): add Card component #161

[Ur-imazing]

Execution plan (completed)

Branch: feat/151-card from main

Steps completed:

1. Card component – Added apps/cms/src/components/sections/card.json with sectionKey, title, description, media, link, variant.
2. Experience – Registered sections.card in sections dynamic zone.
3. Section & container-slot – Added sections.card to Section content and container-slot content dynamic zones.
4. GraphQL/codegen – Regenerated apps/cms/schema.graphql (Strapi build) and packages/graphql client. pnpm run check:generated passes.

Commits:

• feat(cms): add Card component schema
• feat(cms): register Card in Experience and Section/container-slot
• chore(graphql): regenerate after Card schema

PR: #221 — Resolves #151.