Do you know that you can use PnP-Sites-Core to add SharePoint Framework web part on modern site page before the SPFx solution package is being deployed?
This is a guide created by me and a colleague of mine, Xiyuan Zeng from Spanish point, both with extensive SharePoint experience. It is basically our experience shared in a list. It is the recommended performance document for the two teams I am currently working with.
Page hits in SharePoint modern Communication sites using Application Insights and configurable App Customizer
IoT, raspberry p3 cat feeder created due to the need that something has to feed my cats, because I live more than 2500 kms away. This is one of my most successful projects and still runs with almost no interruption.
Prevent modifying a SharePoint List specific column from end user by setting it to read only or read only enforced. Quick guide on how to it setup and what is actually the difference between the two options.
This SPFx React web part sample demonstrates mobile touch slide swiper. By default the web part is responsive, has cross device and browser touch support and uses paging, but additional features like navigation, auto play, loop of the slides and more can be enabled from the web part properties panel. The react slide swiper web part can be used as carousel as well. The slides or cards template can easily be customized.
The problem is that many developers are using PowerShell to write C# code in a different way. We should use it as automation tool able to do more with fewer lines of code. That post is about SharePoint PnP PowerShell short spinets for my own quick reference, but also shared with the world.
Assuming that your SharePoint custom list metadata is created as Site Columns and there is some content stored in those columns, SharePoint Search will automatically create Managed Properties for those columns and you will be able to use them in your solution without any manual effort. However all the automatically managed properties are added as of type text or boolean which is not always ideal you would like to take the advantage of KQL filtering by date or further refinement.
The default Members SharePoint Group that comes with newly created modern Communication site has been granted with 'Edit' rights. This permissions role grants user with rights to create lists and modify the navigation and could be to much delegation for a content author for example. If we want to invite user that should just add or edit pages, list items or document in libraries then we could create Contributors SharePoint group and grant that group with just contributor rights.
Provisioning custom list with SharePoint PnP PowerShell done right