You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've brought this up before but this is a last attempt to get the naming right. Once it releases I suspect we are stuck. I won't rehash fully why we should be using the official name: Fluent2, however, it's a matter of branding and versioning.
If the versioning is out of sync this is going to cause an issue if ever we do need a Fluent1 or a future Fluent3
You are violating Microsoft's own branding and naming conventions. See here:
I agree it is in the spirit of existing themes that Fluent2 should be able to co-exist with any other future theme. This also provides a stability guarantee (not migrating apps automatically to a new theme if they explicitly ask for Fluent)
Description
I've brought this up before but this is a last attempt to get the naming right. Once it releases I suspect we are stuck. I won't rehash fully why we should be using the official name: Fluent2, however, it's a matter of branding and versioning.
For non-developers calling it Fluent is fine. But developers and designers need to be more specific.
Reproduction Steps
N/A
Expected behavior
Fluent2 should be the name of the new theme
Actual behavior
Fluent without any version is the current name of the theme
Regression?
No response
Known Workarounds
Fluent Theme
Impact
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: