feat(cms): Experience content type and section components

[tataihono]

Resolves #37

Summary

Add Experience collection type with dynamic sections for the watch page. Enables i18n, Video collection type, and section components (media-collection, promo-banner, info-blocks, cta) with enrichment (video relation + overrides).

Contracts Changed

• yes
• no

Regeneration Required

• yes
• no

Validation

• Build passed (pnpm --filter @forge/cms run build)
• Contracts validated
• Generated code verified (no manual edits)
• Terraform plan reviewed (if infra change)

Note: Add locale es via admin: Settings > Global Settings > Internationalization > Add new locale. en is default.

Summary by CodeRabbit

• New Features
  • Enabled internationalization support for all content creation
  • Added new content structures for managing experiences, videos, promotional banners, information blocks, and call-to-action elements
  • All new content types include built-in localization capabilities for multi-language publishing

[coderabbitai]

Warning

Rate limit exceeded

@tataihono has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 18 minutes and 24 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

This PR enables internationalization in the CMS plugin configuration and introduces a new Experience content type with multiple section components to model a structured watch page in Strapi, including Video entities and reusable section builders.

Changes

Cohort / File(s)	Summary
Plugin Configuration apps/cms/config/plugins.ts	Modified plugin config to enable i18n with i18n: { enabled: true }.
Experience Content Type apps/cms/src/api/experience/content-types/experience/schema.json	New collection type defining Experience with localized slug, isHomepage flag, and dynamic zone for sections; draft/publish disabled.
Video Content Type apps/cms/src/api/video/content-types/video/schema.json	New collection type for Video with title, auto-generated slug, and image; draft/publish disabled.
Section Components apps/cms/src/components/sections/{cta,promo-banner,info-block,info-blocks,media-collection-item,media-collection}.json	Six new section component schemas: CTA with heading/body/button; Promo Banner with intro/heading/description/link; Info Block and Info Blocks container for icon/title/description blocks; Media Collection Item with video relation and override fields; Media Collection with variant types (carousel/grid/collection/hero/player) and metadata.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• feat(cms): bootstrap Strapi v5 with config and scripts #26: Directly related as it adds the initial apps/cms/config/plugins.ts file that this PR modifies to enable i18n.

🚥 Pre-merge checks | ✅ 6

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: adding an Experience content type and section components to the CMS.
Linked Issues check	✅ Passed	All coding requirements from issue #37 are met: i18n enabled, Experience collection type created with slug/isHomepage/sections, Video type defined, and all section components (media-collection, promo-banner, info-blocks, cta, media-collection-item) implemented with correct attributes and relations.
Out of Scope Changes check	✅ Passed	All changes are directly related to the issue #37 objectives. The plugin configuration modification to enable i18n is a necessary prerequisite for implementing the localized Experience content type.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/37-experience-content-type

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

apps/cms/src/api/experience/content-types/experience/schema.json (1)

19-27: slug UID field has no targetField — auto-generation won't work.

Unlike the Video schema where slug has "targetField": "title", here there's no target field so Strapi won't auto-generate the slug. Since Experience has no title attribute, this may be intentional, but it means editors must manually type the slug for every entry and locale. Consider whether adding a title field (even if not displayed on the frontend) would improve the editorial experience.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/cms/src/api/experience/content-types/experience/schema.json` around
lines 19 - 27, The slug UID field in the Experience content-type lacks a
"targetField" so Strapi cannot auto-generate slugs; update the schema by either
adding a target source (e.g., add a "title" attribute to the Experience
content-type and set "slug" -> "targetField": "title") or set "targetField" to
an existing human-readable attribute if one exists, ensuring the "slug" UID
keeps its "required" and "pluginOptions.i18n.localized" settings and that the
new "title" attribute (or chosen source) is present for all locales.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/cms/src/api/experience/content-types/experience/schema.json`:
- Around line 10-11: The schema currently sets "draftAndPublish": false under
the content type's "options", which allows Experience records to go live
immediately; update the content type options (the "options" object for the
Experience content type / schema.json) to set "draftAndPublish": true so records
enter draft state and require the CMS editorial workflow for publication,
ensuring transitions remain auditable and role-gated as per guidelines.

In `@apps/cms/src/api/video/content-types/video/schema.json`:
- Around line 10-13: The Video content-type schema currently sets
"draftAndPublish": false causing records to be auto-published; update the
content type schema for Video by changing the "draftAndPublish" option from
false to true so all Video records created via API are saved as drafts and enter
the editorial review workflow (leave "pluginOptions" as-is).

In `@apps/cms/src/components/sections/media-collection-item.json`:
- Around line 10-16: The relation attribute "video" in
media-collection-item.json currently includes unsupported keys; remove the
"required": true and "description": "Reference to Video" entries from the
"video" relation (the attribute with "type": "relation", "relation":
"manyToOne", "target": "api::video.video") and instead implement any presence
validation in a Document Service middleware (create a middleware that checks the
media-collection-item's video relation on create/update and throws a validation
error) and place UI help text via the Admin panel metadata rather than the
schema.

---

Nitpick comments:
In `@apps/cms/src/api/experience/content-types/experience/schema.json`:
- Around line 19-27: The slug UID field in the Experience content-type lacks a
"targetField" so Strapi cannot auto-generate slugs; update the schema by either
adding a target source (e.g., add a "title" attribute to the Experience
content-type and set "slug" -> "targetField": "title") or set "targetField" to
an existing human-readable attribute if one exists, ensuring the "slug" UID
keeps its "required" and "pluginOptions.i18n.localized" settings and that the
new "title" attribute (or chosen source) is present for all locales.

[tataihono]

Review feedback addressed (913ce78)

Fixed:

• Experience + Video: draftAndPublish: true — editorial workflow, role-gated transitions per AGENTS.md
• media-collection-item: removed required and description from video relation — Strapi v5 doesn't support these on relation attrs

Not changed:

• slug UID without targetField: intentional — issue spec has slug (unique per locale) with no title; manual slug entry gives editors explicit control per locale