aem-cms-react / cox-ui-core / ui8

Theme Migration Refinement

Revised with existing branch work, publish blocker ownership, and story gap analysis
!!

Waiting on DevOps: Publish @cox/ui-theme to Artifactory

Jeff is handling the publish from cox-ui-core, waiting on DevOps response today. Once published, Alexander's EMKT-18811-Sass-use-migration branch can swap the file: link for a real version and merge. Additionally, packages/theme will be removed from cox-core-ui8, converging ui8 onto the same published package.

Jeff — Waiting on DevOps
Convergence: One Package, Three Consumers
Current: 3 Sources
  • cox-ui-core — consumes @cox/ui-theme natively (internal package)
  • ui8 — uses @cox/theme-ui8 (local workspace package, separate copy)
  • aem-cms-react — local copies at src/assets/theme/v3/ (manually synced)
After Publish: 1 Source
  • @cox/ui-theme published to Artifactory = single source of truth
  • cox-ui-core — same as now (owns the package)
  • aem-cms-react — Alexander's branch adopts it (swap file-link)
  • ui8 — remove packages/theme, adopt published @cox/ui-theme
Cross-Repo Status
cox-ui-core
Monorepo, owns @cox/ui-theme
Sass Complete
@import remaining0
@use statements301 / 79 files
Total SCSS184 files
Publish branchfeature/publish-ui-theme
ui8 (legacy)
Sass done, theme convergence pending
Theme Pending
@import remaining0
@use statements285 / 77 files
Current theme@cox/theme-ui8 (local)
Target theme@cox/ui-theme (published)
After publish: remove packages/theme, adopt @cox/ui-theme. Needs validation — @cox/theme-ui8 may differ from @cox/ui-theme.
aem-cms-react
Branch ready, blocked on publish
Blocked on Publish
master @import120 / 75 files
branch @import0
@cox/ui-themefile-linked
BranchEMKT-18811
AuthorAlexander (Feb 4-10)
Existing Branch Work

Alexander's Branch Covers Two Tickets

Branch EMKT-18811-Sass-use-migration already handles EMKT-19342 (@import→@use) and most of EMKT-19182 (@cox/ui-theme adoption) in 9 commits.

EMKT-18811-Sass-use-migration
  • All @import → @use complete
  • ~63 component .scss deleted, now from @cox/ui-theme
  • globalStyles.scss replaced by _shared.scss + @forward
  • craco.config.js updated with Sass includePaths
  • Sass variables replaced with CSS custom properties
  • Color + typography token migration done

Branch Delta

177
files changed
+451
additions
-13,556
deletions

Impact on Existing Tickets

DONE ON BRANCHEMKT-19342 — @import→@use
DONE ON BRANCHEMKT-19182 Phase A — paths + config
PARTIALEMKT-19182 Phase B — color/typo done, dupes TBD
BLOCKEDMerge — needs published @cox/ui-theme
NOT STARTEDEMKT-19266 — hardcoded token cleanup
Ticket Scope vs. Existing Work
Ticket
Planned Scope
Branch Status
Remaining
EMKT-19342
88 SCSS files: @import → @use in aem-cms-react
Done
Review + merge
EMKT-19182
Add @cox/ui-theme dep, craco config, swap paths, delete dupes
Mostly Done
Swap file-link, verify
EMKT-19266
Replace 61 hardcoded hex, spacing, border-radius with tokens
Not Started
Full scope
Story Gap Analysis — Do We Need New Tickets?
GAP

Publish @cox/ui-theme to Artifactory

No existing ticket tracks the publish pipeline setup and first publish. This is the blocker for everything — needs its own story with AC: package resolves from Artifactory, CI publish pipeline on merge, semver versioning.

NEW STORY NEEDED
GAP

ui8: Adopt Published @cox/ui-theme, Remove packages/theme

No ticket covers converging ui8 from @cox/theme-ui8 (local) to the published @cox/ui-theme. Scope: swap dependency, validate no regressions, remove local package. May be trivial or may need a validation pass depending on how much @cox/theme-ui8 diverges.

NEW STORY NEEDED
RETHINK

EMKT-19342: @import → @use in aem-cms-react

Already done on Alexander's branch. Re-scope to "review and merge EMKT-18811 branch" or close as completed-by EMKT-18811. The 88-file scope is covered.

CLOSE OR RE-SCOPE
RETHINK

EMKT-19182: Migrate aem-cms-react to @cox/ui-theme

Phase A (paths + config) done on branch. Remaining scope is Phase B only: swap file-link for published version, delete local dupes, verify .cox-resi/.cox-busi tokens. Update AC accordingly.

UPDATE AC
EXISTS

EMKT-19266: Replace Hardcoded Values with Tokens

Still full scope. Recommend doing in @cox/ui-theme so both consumers inherit. Alexander's branch did color + typography tokens — clarify overlap. 61 hex vars in header/footer/nav = high-vis risk.

CLARIFY SCOPE
Revised Sequence
Now (Blocked)
PUBLISH @cox/ui-theme
Jeff + DevOps
Artifactory pipeline setup, first publish from cox-ui-core
Unblocked
EMKT-19342
EMKT-19182 Phase A
Done on branch — swap file-link, rebase, PR review, merge
Parallel
EMKT-19182 Phase B
Delete local dupes, verify build, validate tokens
ui8: Adopt @cox/ui-theme
Remove packages/theme from cox-core-ui8, swap to published package
Then
EMKT-19266
Token cleanup in @cox/ui-theme — both consumers inherit changes
Colors → spacing → border-radius. High-vis risk on header/footer/nav.