Skip to content

Commit

Permalink
Updated migration documentation (#28074)
Browse files Browse the repository at this point in the history
  • Loading branch information
GeoffCoxMSFT authored May 31, 2023
1 parent 93fe951 commit 23d7cf2
Showing 1 changed file with 9 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -80,11 +80,16 @@ See _Extending themes with new tokens_ section in [Theming](/docs/concepts-devel
## You can make v0, v8, v9 components have the same style

While you have both old and new components together in your application, you may see some differences in the theme and styling of components.
You can choose to live with the minor discrepancies until you have fully migrated to v9.
You can also choose to make everything look like a previous version or like v9.
You can choose to live with the minor discrepancies during migration, or make everything look the same.

> We recommend moving to v9's Fluent 2 design.
> It has improved accessibility and has consistent style across components.
> We recommend moving to v9's Fluent 2 design. It has improved accessibility and has consistent style across components.
### You can use the Fluent 2 theme for v8

If you want to make v8 components look like v9, you can pass the Fluent 2 theme for v8 to the ThemeProvider.
For more information read the [v8 Fluent 2 theme documentation](https://developer.microsoft.com/en-us/fluentui#/controls/web/themes).

In the v8 documentation for each component, you can select the Fluent 2 theme to see how it looks.

### You can create custom themes

Expand Down

0 comments on commit 23d7cf2

Please sign in to comment.