## Summary This epic tracks the Vue 3 migration of every page entrypoint owned by `group::planner intelligence`, as part of the parent epic gitlab-org&23088. 📚 Each entrypoint moves through three states: 1. **Vue 2** 🔴 no `vue3_migration.yml` sibling file, the page builds and serves Vue 2 only. 2. **Rollout** 🟡 `status: rollout`, both the `<entry>` and `<entry>.vue3` bundles are built and a feature flag decides which one is served at request time. 3. **Migrated** 🟢 `status: migrated`, Vue 3 builds under the original entry name and the feature flag is gone. Migration steps per page are documented in the [Vue 3 migration guide](https://docs.gitlab.com/development/fe_guide/vue3_migration/#option-1-recommended-migrate-your-page-entrypoint-using-a-feature-flag-and-vue3_migrationyml). ## Status at a glance 📊 | State | Entrypoints | Share | | :--- | ---: | ---: | | 🟢 Migrated / on rollout | 16 | 100% | | 🟡 Rollout | 0 | 0% | | 🔴 Vue 2 | 0 | 0% | | **Total** | **16** | | ## 🟢 On rollout or migrated (16) All planner intelligence-owned entrypoints in this epic now have `vue3_migration.yml` coverage and corresponding feature flag rollout issues. Their Vue 3 versions are either fully migrated or in the final stages of feature-flag rollout. The two rollout feature flags are tracked in child issues of this epic (one for wikis, one for GitLab Pages). ### Project wikis (6) - [x] `pages.projects.wikis` — wiki index, new and edit. Mounts the content editor (`~/wikis/edit`), the sidebar (`~/wikis/mount_sidebar`) and the more actions menu (`~/wikis/more_actions`). - [x] `pages.projects.wikis.show` — wiki page view (`~/wikis/show`) - [x] `pages.projects.wikis.pages` — All pages list (`~/wikis/pages`) - [x] `pages.projects.wikis.history` — page history - [x] `pages.projects.wikis.diff` — version diff, mounts `DiffStatsDropdown` - [x] `pages.projects.wikis.git_access` — Clone repository panel ### Group wikis (5, EE only) - [x] `pages.groups.wikis` - [x] `pages.groups.wikis.show` - [x] `pages.groups.wikis.history` - [x] `pages.groups.wikis.diff` - [x] `pages.groups.wikis.git_access` ### GitLab Pages (5) - [x] `pages.projects.pages` — Pages settings, mounts `~/search_settings` - [x] `pages.projects.pages.new` — new Pages deployment (`~/gitlab_pages/new`) - [x] `pages.projects.pages.show` — Pages deployment detail (`~/gitlab_pages/show`) - [x] `pages.projects.pages_domains.new` — new custom domain - [x] `pages.projects.pages_domains.show` — edit custom domain ## Next steps ✅ 1. Monitor the two rollout feature flag issues (one for wikis, one for GitLab Pages) linked as children of this epic until they complete rollout and are stable. 2. After successful rollout and soak, ensure each `vue3_migration.yml` entry is flipped to `status: migrated` and any temporary feature flags are removed. 3. Close this epic once both rollout issues are completed and no planner intelligence-owned Vue 2 entrypoints remain. ## Notes 📝 - Wiki entrypoints inherit their ancestor bundle, so every `pages.projects.wikis.*` entry also loads the content editor, sidebar and more actions apps from `pages.projects.wikis`. The content editor is the largest Vue surface in this epic and is the main migration risk. ⚠️ - The group wiki tree has no `pages.groups.wikis.pages` entry even though the `wikis#pages` route is shared between projects and groups, and neither tree has an entry for `wikis#templates`. Worth confirming whether those views fall back to the ancestor bundle before sizing the wiki batch. 🔍 - Planner intelligence also owns GitLab Flavored Markdown, the rich text editor, GLQL and the Confluence integration, but none of those have their own page entrypoint. They ship as components inside pages owned by other groups, so they are migrated implicitly by whichever entrypoint mounts them. - The `pages.projects.pages_domains.*` entries only mount a `GlToggle` through `~/toggles`, so they are the cheapest pages here and are good candidates to go first. 🚀