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.
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.
When you write a web part, that don’t use Fluent UI or its predecessor Office UI Fabric, you might have recognised Segoe UI from SharePoint is not loaded there.
SPFx web part in Teams do not load Segoe UI
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.
Its been a while since the last release for my toolset for Theming in SharePoint development. I work on a product, and I have to make sure that the web part design is flexible enough to work great with any SharePoint applied theme. I discovered many changes in the currently available theme slots.
The support in case of SASS variables in your standard SharePoint project is limited. It was time to update my tool, but it comes with more great features that only SASS variables.
Microsoft recently released new design assets to create experiences using the latest Microsoft Fluent design language. These design assets are available as free downloads on the Office UI Fabric dedicated web site.
Most of their asset is available for design tools such as Figma, Sketch, and some are still available for Adobe XD.
A while a GitHub issue in the sp-dev-docs came to my attention, where someone had a problem titled as Can’t get grid system working using office fabric ui react. I took a closer look on why it is so challenging to get the grid system running right now and in SPFx projects in general. There are some catches you need to be aware.
Some of those issues are already documented in the a blog post on How to make your web parts responsive to the parent container or How to use Bootstrap in SharePoint Framework projects. Here is the rest of the story.
Office UI Fabric is somewhat like the first and foremost first third-party Framework that you may want to use in all your projects to create a seamless experience with the rest of the Office 365 platform. It is not exclusively to SharePoint or SharePoint Framework Projects.
It has been a while since I release the last version of my spfx-uifabric-themes npm package to make it easier to handle theming in SPFx projects.
New Release spfx-uifabric-themes
I’m proud to present now a new version that supports theming through CSS variables instead of SASS variables. If you hear this the first time, let me give you a short introduction on that.