Migration · governance · roadmap
Migrating
Carbon's docs site doesn't surface its own v10→v11 token rename table — the migration content lives buried in @carbon/react's GitHub repo. Avala does the opposite: every migration path lives here, indexed, with explicit token-by-token diffs.
From Carbon
→Token rename map, role-by-role mapping, and the values that diverge.
From @avala/ui (legacy web kit)
→Component-by-component cutover plan for the prior React kit.
From avala_ui_kit (legacy Flutter kit)
→Codemod path from the legacy Flutter kit to avala_design.
Changelog
→Every release of @avala/design and @avala/design-tokens.
Roadmap
→Phased delivery plan and active commitments.
Governance
→Locked semantic colors, fork policy, upstream-Carbon sync cadence.