Support Themable CSS Without Having To Customize The Master Page
For light-touch customisations, we simply want to use SharePoint Themes and also add our own Themable CSS to sites.
Unfortunately the only way to add a Themable CSS to a site is add a CssRegistration control to the Master Page referencing the Themable CSS file. We want to avoid having to customise the master page simply to add a Themable CSS link.
It is contrary to current Microsoft guidance to modify the master page unnecessarily, and in doing so, in the best case we lock ourselves out of any future enhancements as SharePoint evolves that are dependent upon an upgraded out of the box master page. In the worst case functionality may stop working, or have a degraded user experience if SharePoint or O365 evolves while the master page remains static.
We don't want our users to have to fix the master page anytime O365 evolves, or have to go back to development, for the sake of a CSS file link.
Sig Weber commented
Yep, I'm in the same boat. Upvoted +3
Nick Hobbs commented
Please see my blog post on this subject that explains the alternative approaches that we have tried but do not work, and why this is such a concern, and results in conflicting Microsoft guidance in Patterns & Practices.
This has been acknowledged by Microsoft as a problem, but needs others to show that they have the same issue so that this can be progressed, so please vote this up.