We're very excited to announce version 01.01.02 of the Upendo DNN Page Manager module is ready for you to use.  In this release, we focused directly on just fixing a few bugs.  These bugs include...

Happy DNN Summit day, everyone!  We hope you're having an awesome time at the DNN Summit conference today and tomorrow.  Our team is split among still working, but a handful are there with you.  This year, in celebration of our epic DNN CMS 20th anniversary and the conference itself, we wanted to something special for all of you.  So, we've spent a ton of time working on some open-source stuff, starting with this project...  

We're very excited to announce that version 01.01.01 of the Upendo DNN Page Manager module has been released.  While there have certainly been several releases over the past handful of months, this release marks a significant milestone for me.  This is the first release where the current feature set represents the features I had in mind for the first release. Now, you get to learn what got released this time... 

A very common question in recent years relates to how people are building their various DNN extensions these days.  Most often, new extensions and development are using various techniques and frameworks to present features using a SPA approach.  Whether the chosen tools include Angular, Vue, or something else, it makes sense.  End-users are more engaged when the page doesn't fully reload.  However, if you're the developer building this - and especially if you're not a seasoned pro, your first obstacle will undoubtedly be whether or not you know your API endpoint path.  This post will hopefully help you figure that out.  

This is a re-post and partial rewrite of a blog article I wrote back in 2010. Yeah. That was 12 years ago, and the post is not only still relevant, I'm rewriting it because of a question in the official DNN community forum last week. Oh, and I won't even mention that DNN just had it's 20th anniversary! I mean, wow!!