The best way to implement a design on the web is not to use fancy tools or marketing jargons. Every site and application is defined for 25 years by two fundamental technologies. HTML that gives our pages and application a structure. CSS that makes the look and feel and experience envisioned by design come to life. Both combined is all we see and interact on the web.
Happen so that no matter how many technological advancements we put in our code. HTML and CSS together is still the most performant web framework on the planet.
These two web technologies are the technological layer. I created a framework that implements Microsoft Fluent Design language.
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.
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.