In case you recently upgrade NPM to Version 6.0 and created a new SharePoint Project through the Yeoman generator. There is a chance that you recognised the following new notification at the end of the NPM installation process.
Security Report after SPFx installation
What there are five vulnerabilities, one with severity low and four with severity high and I can run ‘npm audit’ to get a detailed report?
Don’t start to scream “fire” and run in panic through your office, uninstall all your SPFx projects from all your tenants, clean up your CDN, keep calm and learn the reason why this gets now reported after the installation.
No matter what your preferred operating system or device is, you can develop and deploy for SharePoint whatever you want to use. Even for the deploy modern experience components for branding such as themes for the modern experience.
In my case, I work mostly on Mac occasionally on Windows, whatever serves its purpose best. Sometimes I write PowerShell Scripts to configure things on Office 365, but there is a new option other than PowerShell, but those configuration changes nowadays are even possible through classic bash scripts through the opportunities provided by the Office 365 CLI.
Enough said on the new possibility let’s look why it might make sense to have multiple different themes available.
Recently I added a new sample to the PNP SharePoint Framework examples. The goal of this sample was to take text field input evaluate it against the Microsoft Graph and get information back information about a site collection, websites and list or libraries.
This blog post is no in-depth article on how to query the Microsoft Graph or how to make the code to work and authentication works. Instead, I like to give you an overview of the ideas behind the implementations.
You might have recognised that the workbench of the SharePoint Framework has a responsive design tester included. In this blog post, I take a look what possibilities we have to properly test the responsiveness and the user experience of a web part.
There are also some pitfalls included if you entirely rely on the integrated too.
Once a wise man cited a wiser woman with the following statement:
“My mom always said life was like a box of chocolates. You never know what you’re gonna get. – Forest Gump”.
This quote can be applied to SharePoint in Office 365 nowadays too. When you have a provisioned classic site or even a modern site, then you never know what primary colour you get as your default theme.
Recently I stumbled in a new challenge I haven’t had for a long time. One of my customers wants to migrate users from Active Directory Domain A to Active Directory Domain B. The problem was that all the previously edited documents should get mapped to the new users.
Not every one of our users works in marketing or is an expert in storytelling. Storytelling is a skill for the future, but like every skill, it doesn’t come overnight and requires training. I assume, like for many of my customers, have problems to find an appropriate image for the header.
On the other hand, to communicate what is happening around you is beneficial for the rest of the company too. Let me show you a use case why you use default images for events in communication sites first and how to solve this on this kind of site templates.
Recently a new feature has been added to the authoring process in SharePoint online. This new feature helps you to define appropriate alternative text descriptions for your images on pages. In general to specify alternative text for images is possible the first time in SharePoint history. Previously only the title of an image could be defined.
When a new image gets inserted on a page, the image gets analysed by a background service, which assumes the content of the image and returns an appropriate description. Through the help of pattern recognition and artificial intelligence, the returned values are pretty accurate, at least with the pictures I tested this feature so far.
I know the Feedback and Mobile App buttons are essential for Microsoft, but many of my customers ask me to remove it. There a mainly three reasons for that. The first is the location and loading behaviour of those buttons. It takes a while until those buttons are loaded and catch a lot of attention of the user once they are visible on the page.
The second reason is that the location sticky on the bottom of the page might not be the perfect spot for those buttons. I might be more useful to have them somewhere in the header or suite bar.