In the recent blog post on how to make a web part works with different section backgrounds using CSS variables, I already covered. At the same time, this works perfectly for just regular web parts. There are specific scenarios, where this approach fails.
SharePoint Online for a long time, has multilingual support. On classic experience, there were language packs and Variations available for that. Yet also the modern experience has multilingual capabilities for that.
It might look that SharePoint is well capable of providing the language chosen by the user for the user. While I had to take a closer look under the hood over the last couple of month, multilingual and SharePoint has a complicated relationship.
Building a grid system in the past had a lot to do with math. Luckily, implementing a grid system has dramatically changed over the last years. You don’t rely on any framework such as Fluent UI to get your things done right.
SharePoint also has a concept of single part app pages. This page type gives you an entirely blank canvas, enabling the full potential and possibilities for an application. It also comes without any grid system, but this is something we can address.
Over the last couple of days, I banged my head against the wall. I hate when things don’t work as expected. On the other hand, I love challenges.
The thing we are talking about the documentation on “Supporting section background“. To be clear, the documentation is correct. It works as described. The issue I and many others have with this documentation it does not apply to your project.
In one of the latest design iterations, the site logo has changed to incorporate the new Fluent UI design. The site logo has now rounded borders. Let’s do a quick design review of how this work or don’t work for some companies.
In the end, you will learn a trick on how to revert the changes, Microsoft did on the logo.
Track down fonts rendered on a web site sometimes can be challenging. Reply purely on the font family is not a safe bet. The network trace only shows that the font has been downloaded but not that it will be used and applied correctly.
Luckily, the latest versions of all major Browser offer now especially support that makes it easier to identify the real applied font. Besides, never trust what you see in the Browser; it might be something that sits only on your client.
[Read more]
If you like to enable the new meeting experience for Microsoft Teams, you might assume that this setting is application based.
Teams settings that enables the new meeting experience
First of all, I like the new “Create a list” experience. The organisation of all the different possibilities is excellent now.
This wizard-like experience allows you to create list quickly and guides you to what you want to do. Also, it comes with great new features such as create a new plan based on existing across all site collections in your tenant.
The base idea of how it looks now is promising, but there are some design and user experience issues I like to uncover in this design review.
There are multiple ways to add custom web fonts to SPFx projects. The best options are to load fonts from a CDN, your own, a commercial provider or via fonts.google.com.
Sometimes this is not enough cause our customer has their custom fonts or my want to use a custom font for a single web part only. Let me show the steps to get this accomplished in the SharePoint Framework.[Read more]