Recently version 0.3.0 of hTWOo UI was released, time to give you an update on the new additions.
Fluent Design is all about the consistent experience through all applications in the Microsoft 365 stack. While Fluent UI Framework still tries to harmonise the various Frameworks, hTWOo extends the reach from pure SharePoint framework UI components into the Teams customisations space.
Suppose you have great customers like I have that do not rely on IE 11 anymore. There is no time to wait to make the web parts and extension only work in true modern browsers.
The switch you have to make it simple and in seconds, even for older projects. When you created a new project and run the first build, the code output in your lib folder would look similar to this.
Last week I had the great honour to talk with friend Andrew Connell about my newest project, hTWOo UI, on the Microsoft Cloud Show. I highly recommend listening to this podcast in general but in specific this episode.
We talked about the ideas and concept behind hTWOo, Fluent Design and the current problem developers facing. Especially why it is a suitable alternative for your development on the Microsoft 365 platform.
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.
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.