Migrate dotcms.com content types to new Edit Contentlet mode and validate with real production data

Description

The full starter environment does not have enough data variety to reliably validate the new Edit Contentlet mode. To get meaningful QA coverage, we need a production-like environment loaded with real content.

Goal: Provision a new environment with a production database dump, then migrate the content types to the new Edit Contentlet mode one at a time — running a base QA checklist on each before moving to the next. If a content type includes a Custom Field, migrate it to the Recommended Implementation before beginning QA.

Firsts Content types to migrate (in order):

1. Heading
2. Images
3. Banner
4. Documentation
5. Course Chapter
6. Builds
7. Deprecation
8. DevResource
9. BlockPage
10. Content Block
11. VanityURL
12. Announcement

Base QA checklist (same for all):

• CRUD: Create a new contentlet · Read/view existing contentlets · Update an existing contentlet · Delete a contentlet
• Lock/Unlock: Lock a contentlet and verify locked state → Unlock and verify unlocked state
• Translate: Translate a contentlet to a non-default locale and verify it saves correctly
• Custom Field (if present): Migrate the custom field to the Recommended Implementation before running QA

Rule: Complete QA on a content type before activating the next one.

Acceptance Criteria

Environment:

• New environment provisioned with a production database dump containing all content types

Bug tracking:

• Any bugs or regressions found during QA are filed as separate GitHub issues and linked to this task

Corpsites PROD instance

• All content types in our PROD instance are migrated to the new edit contentlet

Priority

Medium

Prerequisite: The new environment must be provisioned before any migration work begins.

Start with the prerequisite of provisioning an environment from a production database dump, then follow the listed content-type order and the base CRUD, lock/unlock, and translation checklist. Migrate any custom fields to the Recommended Implementation before QA, file regressions as linked issues, and finish when all listed PROD content types have been migrated.