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.
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.
TLDR: To enable this feature in Office 365. Upload a 3D model saved as a GLB file to any document library and you are able to preview it live in your browser.
The more exciting story is now how to use technology but why and what are the possible application.
Following the instruction on how to create a library component, get you pretty easy up and running to try out this new feature.
To make it production-ready you have to do some manual steps and tweaks. Here are some suggestions.
SharePoint Framework offers you a pretty solid project setup, but on the other hand, it doesn’t give you options to optimise the gulp, build or the webpack configuration.
The more web parts exist in a single project, the slower the build task become and all the code in the project will be compiled at once, instead of smaller incremental builds. Technical possible but not yet supported.
The good thing is that there are some options you can directly trigger from your web part code. Some of these options affect webpack others can be applied in ReactJS. Not only in case of build times but also case of user experience and web part performance.
I case you are working with photos; it is obvious to have these pictures full-sized in your SharePoint. Sometimes it makes sense to handle images that should land, for example, on a communication site with a little bit more care. Especially when you are dealing not with photos but with illustrations.
Sometimes you don’t like to have a background on your images. Let me show you why.
A common practice these days is to organise site collection in hub sites. It gives you a great possibility to arrange your content more dynamically than ever before in SharePoint. On specific site type, we are dealing in any SharePoint project, for example, are project sites.
These project workspaces only have a defined start and end date. A site collection like this can be useful for a couple of weeks, to month or in case of long-running projects for years. What to do when the workspace reached his end of life?
During last weekend I already teased a web part named ‘Panthema’. I was a bit surprised by the interest in this helpful tool for developer, consultant and everyone who has to manage themes in SharePoint on Office 365. I also think it helps a lot in debugging the colours used.