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.
TLDR: Thanks to SharePoint, it is possible to write an Office UI Fabric styled button without using ReactJS or Office UI Fabric at all. The code is simple and easy to reproduce for any project. Copy the source this blog post contains and you are ready to go.
The longer story is that recently, more theme slots are available in SharePoint Online than before. I created a reference chart for the documentation of SPFx-uifabric-theme project.
So isn’t it exciting to create buttons, hyperlinks and input fields just using SASS variables and fundamental HTML elements?
During summer there were two great PnP Summer Camps. In the second edition, I had the opportunity to demonstrate a cool looking web part. A web part that allows the user to edit the content directly on the page. Similar to the out of the box web parts but with a big difference. All the edit capability don’t use any fancy third party library.
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.
The following configuration shows the webpack.js generated during the build process of a SPFx
Hello World wep part. References to fixed path in the generated webpack config were replaced with the default way of resolving path. (
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.