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.
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.
During development or the product design or project, you like to avoid external dependencies as much as possible to keep your code secure, reliant and consistent. With these baselines, I want to cover some aspects of Fluent UI that you should consider before adopting it. To be more specific the reason when considering Fluent UI are related to the web version.