This post is part of a four-part series on using Angular in SharePoint Framework projects (this post) Using Angular Elements in SharePoint Framework Projects HowTo: Angular Elements in SharePoint Framework Projects - One Big Project HowTo: Angular Elements in SharePoint Framework Projects - Two Projects The Good, Bad & the Ugly: Using Angular Elements with the SharePoint Framework Check out my Mastering the SharePoint Framework course by Voitanos which will contain a chapter on using Angular Elements in SharePoint Framework projects including step-by-step demonstrations on how to make this work using the latest version of Angular.

This month’s update on my Mastering the SharePoint Framework course features the transition from one sprint to the next.

Around this time last year, I attended my first SharePoint Fest conference in Seattle, an event I had wanted to be involved in for quite some time.

Late last year I blogged about the future of ngOfficeUIFabric, a project I kicked off and managed for a few years.

In the past, I’ve written how I prefer Yarn over NPM not just for SharePoint Framework (SPFx) projects, but also for all my Node.

This post has been cross-posted to the Voitanos blog here: SharePoint Framework Generator Updated to v1.

Over the last month of May, we’ve seen quite a few announcements from Microsoft with respect to what’s new and coming related to the SharePoint Framework (SPFx).

Microsoft introduced a new extensibility and customization development model for SharePoint in 2016. The SharePoint Framework brings client-side development to SharePoint as a first class option for developers.

Someone had to say it… I’m not thrilled to write this post, but I get this question often enough that I think it’s time for someone to take a stand against this package.

Microsoft introduced a new extensibility and customization development model for SharePoint in 2016. The SharePoint Framework brings client-side development to SharePoint as a first class option for developers.