Hi Cathy_Dew. Thanks for the announcement.
The new Central Branding solution is looking promising. However, there are a few things I'd like to provide feedback on.
- Are you looking at the option to use the Private CDN? Turning on the Public CDN is potentially a blocker for us.
- What is configured (scope) when enabling the Public CDN for the Branding Center - does it just add a specific scope for the Org Library(s)?
- Really hoping you ensure the Microsoft example fonts are disabled (not shown) by default and we (your customers) can enable if we want. They are not at all in alignment with our brand so can't have them available to users, and likely won't be for most of your customers.
- One big gap is the ability to create a Theme and not make it available to users to apply to their sites. We have many scenarios where we want to apply a specific Theme to a set of sites (our Cultural Hub as an example). This has a very distinct Theme that shouldn't be used anywhere else in the tenant. This needs to be managed centrally but can't see a way to do this now. We are not looking to use the Site-specific Themes that you mentioned (see further comments about those later) as the Theme will be applied to multiple (select) sites.
- Really hoping you are looking to redesign the current Theme builder as it's very limited (similar to the original Fluent UI one we used in the past). We still need to go into the JSON to change colors at lower levels for all of our Themes to get the look and feel we need.
- How do you identify sites that have used a particular theme? We need this for governance, especially if some of our Themes change over time. We are currently only able to do this using _api/web/PrimaryColor - which is not ideal and won't work if two themes have the same primary color.
- Are you looking to provide a way to hide individual Microsoft provided Themes (currently it's all or nothing)?
- It would be great if your Learn about themes link includes low level understanding of what colors are used where.
- PLEASE ensure the (upcoming) Site specific Theme option is DISABLED by default. The whole idea is that we can centrally manage our branding. We can't have our users start creating any theme they want across the tenant and destroy our Company Branding.
A lot of these are absolute blockers for us. Note that we have well over 100k SharePoint Sites and 65k+ users, so need to ensure we are managing our governance with everything that comes through from Microsoft.