Microsoft 365 Community SharePoint, 18 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Introduction to updated SharePoint Starter Kit v3

Description

In this 12-minute developer-focused demo, Eric Overfield shares the latest technology demonstrator solution released 2 months ago. The kit consolidates SharePoint dev and provisioning into one piece. Full bundle of capabilities includes webparts, extensions, library, PnP and customizable SharePoint provisioning templates for sites, pages, content + documentation. Uses SPFx v1.16.1, Fluent UI, PnPjs v3.11. Normalized coding approaches. Integrations with related products. Stand up an example site in less than 10 minutes. All open-source.

This PnP Community demo is taken from the Viva Connections & SharePoint Framework Bi-weekly sync call recorded on May 18, 2023.

Demo Presenter
• Eric Overfield (PixelMill) | @EricOverfield

Supporting materials
• Repo - SharePoint Starter Kit v3 | https://github.com/pnp/sp-starter-kit
• Repo - SharePoint Starter Kit v3 | https://github.com/pnp/sp-starter-kit/tree/v3

Learn more
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 Platform Community - http://aka.ms/community/home

A

B

We wanted to be able to discuss the version three that was just released a couple months ago on the SP starter kit, which is really just an evolution of what we saw in V2, but it's designed to sort of pull together a lot of the stuff that we've, the PB community and everyone else is doing within SharePoint SharePoint, Dev SharePoint provisioning all into one piece. So it's really easy for people to get started to see a provisioning template. That's got a couple thousand lines of code in it. It releases all kinds of cool stuff.

B

It puts all these things out there with web parts and extensions and all that fun stuff all into one one bundle. So uh these three just came out, and let's kind of quickly go over what that looks like some of the things that we did here, we updated to a much more modern version of SharePoint. Yes, well that nice Cadence it can be a challenge to get all 20 odd projects updated, so we'll always be a little behind, but hey 16 ones is pretty good, updated, fluent UI.

B

We got some a time at least a more modern version of ppjs. uh We were able to upgrade the um the Microsoft cloud toolkit to a much more current version and it's all also demonstrating use of the graph API. So if you're looking for that, big bundle that sort of has a whole bunch of stuff all together that you installed in about five ten minutes into a Dev tenant, and you get all the code great place for it.

B

We're demonstrating some libraries uh with those getting provisioned out so that they can get automatically activated within sites. We would look to overall normalize our code. uh One of the great things of this project was completely Community Driven and every Dev did things a little differently. We attempted to to normalize more of the approaches we have to just be a little more consistent. We did remove support for uh on-prem.

B

If you do want that there is an on-prem uh 2019 version uh in the V2 Branch, so we left it there all for you, but we realized that that just wasn't it wasn't providing the value to attempt to maintain that. So we just said now: let's just stick with SharePoint online, where things are going, uh but it even has in some of the T tab development components which it I know it's kind of simple, but still like.

B

We just again want a complete package well as completed as can be that provides lots of different little things that were seen all over the place and pulling them all together. I mean we use a lot of the PVP controls and all that stuff. It's it's a demo of everything um and then also we wanted to ensure that within the provisioning component you know we updated to the latest in the ux design and the layout capabilities.

B

As of you know a few months ago, of course, that's going to continue to evolve and we will continue uh to to grow with that. So those are kind of the big aims of this big upgrade. uh You can easily find it, of course, at SB, starter kits part of the community.

B

um Easy stuff I always want to make sure we thank everyone. Who's been helping us, the two big ones here that really helped with the upgrade uh were shogani and Don. So, thank you both so much big thanks. Of course, everyone else has contributed as well. If I missed your name, I do apologize as I basically used the uh the GitHub commit to help do that. The the uh the chatter in the issues list has always been good as well.

B

So so thank you all so much what's included in the V3 component, so 16 web Parts, five extensions. There's a library component as well. There's two provisioning templates. So there's the full purchase, Union template pre-built for you, uh as well as the uh XML that you would use to to rebuild it.

B

If you want to rebuild a PNP file, there's another one for just the SharePoint framework components, because in V2 what we did was we split out all of the the uh all of the different web parts and extensions all into individual svpkgs to make it a little more manageable, a little more upgradeable and a little more useful for um for you all as well. So you can just grab the piece that you might have wanted. uh So there's a a provision example just for that as well and then within the primary provisioning template.

B

If you want to look at like a larger provisioning example, what's it trying to do? Is this provision a collaboration site which turns into a hub site? This is all within one command, which is super nice, those who use the provision. Of course, you know this totally possible two team sites that are associated with that uh it pre-populates the mega menu.

B

It has 15 pages within the Hub site within that communication site with different components, different layouts added to it now the provisioning template, though I mean it's huge, and you can totally see how it's all done and uh once you provide. My suggestion is that you provisioned it first see. What's provisioned then go dig into those files and- and the read means I think- are reasonably good. uh I've I've edited a lot of them myself, so so it's uh you know how old did I do for you.

B

All I would be interested to know, but we really attempted to document all of these aspects of using the starter kit so that you can turn it into your own. I would really not like to see you install it and go straight to production. To me, this whole point is it's that technology demonstrator that you can within minutes have a working example, and then you can spend hours days months years to do anything that you wanted to do and, of course, all open source. There's uh every there's, not anything in that.

B

That's proprietary that you can't uh turn into your own thing, so how to get started, how to go ahead and just you know, work today. It's basically the same when we went from V1 to V2. That was a big one. V2 to V3 is much more simple, so we got a lot of documentation here.

B

Go you go from there pretty easy Once you uh once you clone the code you're going to commit you're, okay, you're gonna, commit connect, excuse me to your site and then you're, just gonna invoke that PVP template like that's it now, there's some configuration options which I have time if I have time for demo, I'll show you and that is in the documentation as well, but that is going to install everything. I've talked about within the within your that that tenant you connected to about five or ten minutes is what my experiences is.

B

It just takes time to get all those uh Solutions in and all that kind of stuff, but that that's the way it is. This will require attendant admin permissions, um primarily because we're going into the tenant.catalog uh we're going into the term store um all those requirements, the prerequisites they're all found in the documentation. We explain what it is. We tell you why we're doing what we're doing.

B

But again, you can always dig into the code to figure out why it is that we're doing it or strip out the things that you don't want to do now what's nice is that there is an upgrade path here uh when you, you won't want to do a full provision per se, because you would be re-provisioning the sites themselves.

B

uh You'd probably want to do that to a new spot, but if you're just looking to upgrade all of the or any of the components that made up the whole uh the whole project, those are just one for one updates. There's all the IDS are the same. That should work just well you'll get all the greatest uh and latest in the the update that we did. If you want to do that and again, if you still want the on-prem, if you're still interested in that, we did attempt to document this as well.

B

You can always go back to the V2 Branch. You can go, get the old, SharePoint, 2019 aspects that we completed and have at it and have fun so yeah pretty easy to get started. uh Okay, what it looks like when you provisioned this this would be a raw provision. uh You can see a lot of the pieces here, this, the the communication side, of course, that Mega nav has already been updated.

B

You can see a lot of components here that some of them now are a little more out of the boxy, but everything your seniors actually custom. So if you were looking to take some other code or take some of the components that that were already available in SharePoint, but you want to tweak them, there's already code for you that that was built from scratch. So this isn't anything that came out of Microsoft engineering. This is just people rebuilt this stuff, um but you can see a lot of graph components over on the right.

B

You can see some some list, usage and whatnot kind of in the middle and hitting current weather and whatnot, which again you could do out of the box, but now you've got the code. If you want to do it, some news, ropes and all kinds of fun things like that, so really cool things and and cool components that you can that you could include already.

B

uh If you want to help uh ways that I think that that make sense install this and use it if you've, if you've used it in the past, you may want to get an update in it and look at see what we've done and uh go, install it again or just go dig into the code and see some of the updates that were made. Go. Look at some of the commits you'll see some of those updates, we're always looking for any kind of feedback.

B

Any kind of feature requests, uh any issues that you find a lot of times. We found issues that had to do more with uh the provisioning template or something so that's going to be interesting. I always look to to make sure this all works for you and whatnot.

B

um Hey we're, always looking for PRS you've got new ideas. New features, new bug fixes my requests there. Kind of like any other project is, is try to keep your commits. Smaller. Don't do massive big updates, because they're harder for us to push merge in, especially if we got a bunch all happening at once.

B

So, if there's an update to a solution, you know update that solution, commit it uh if you're working on documentation, you provide anything, do like a commit per file or something so it's easier to pick and choose and help massage everything into place.

B

um Let's see promote this I think this is a really good solution to help people get started with provisioning, where they want to start building a larger solution for themselves uh and then also I'm, always looking for any kind of uh content that can help promote it blog posts or recommendations or insights how-to videos- if you do them like um throw them somewhere, throw them in the issue in the issues list.

B

That would help me to help the community then promote what you're doing as well, because we just want to really help with the usage of that so um over. In the starter kit, I told you, it really is easy. uh We we start pretty quickly with getting started, and this is all in the the readme.

B

It's it's two major lines that you're looking for here, connect and invoke, um and then a command to make it go a little deeper would be something like where you can add the the um some parameters to say where you want the the three different sites to get created, so that could really help you get started and um that's it I mean if I went ahead and hit enter, which I'm not you're gonna within about five ten minutes out of that time, it's gonna, it's gonna, build your site.

B

You can see the site that I already showed you that screenshot of I mean it's. It's I think it's a good solution to help get started, especially when people are attempting to understand how to build provisioning uh within the solution itself, um pretty easy to use. There's a provisioning folder where you've got the dot PNP files that I talked about again. We talked about readme's on how to go even deeper into that, so I really I am pretty proud of the documentation. The community has helped build here, because this is a technology demonstrator solution.

B

You've got really good web Parts out there. You've got really good cases out there. You've got a lot of documentation on provisioning and stuff, but like this tries to pull it all together into one bundle so that you can use it for your org and get get started with that. um I did talk to you about the uh the provisioning template the raw XML files, so those are um uh that that's kind of fun.

B

You can just see that there's a whole bunch of cool stuff here about you know, adding to the app catalog we're building the sites, we're putting all the things in here. The thing that sort of buried in documentation but I want you to be able to find is where is it um yeah see now I've even lost it? uh It's the readme for getting for rebuilding the uh for rebuilding the template. The documentation is here.

B

I can definitely find it if you, if you get stuck with it, I can show you here that I got it I got it ready for us, though, building a templates easy you go into that that templates folder, where I talked about uh where the XML files for the position, demos. Are you read in the PNP template? That's simple! The next command is you just save it? This is really easy to do to break your own provisioning temples based on the solution. It's two commands. You read it in you, save it you're good to go.

B

You could build your own cool stuff, so yeah um I I, wish you all the luck with the solution. I hope you all find it very useful with the update and I think Hugo I can send it on back to you.

A

Awesome, thank you and again, thanks to everyone who contributed to this initiative, uh including Bo foreign.