There are SO MANY exciting new features in XMod Pro 4 that it's hard to pick a favorite! So I think I'll pick a favorite or two and make a post about each of my top favorites. This first one is on one of my favorite time savers and improvement on file and code organization when dealing with multi-portal sites.

Continuing in the line of blog posts that help extend the ease of DNN management, today's post on DNN Enhancement is our Page Skins Manager.

As a development company with tons of DotNetNuke sites out there for our clients, we've found that we often will need to make site-wide edits and updates to the site as quickly and painlessly as possible. The larger the sites are (more pages), then the longer it takes to perform some tasks across-the-board. Here, I'm thinking of DNN skin-related changes, the kind you have to make when, for example, a client wants you to update the look & feel of the site skin for the "new 2012 web 2.0 look" that the designers have been working on.

In this post, we'll talk briefly about the settings that you may want to try out if you are using XMOD PRO on a DNN site where you are running PageBlaster.
 

One of the things that we'll be doing in our XMOD PRO blog posts is sharing some of the different solutions that we've built that help extend the functions of other modules or bridge the gap where there are functions or features that are missing in a DotNetNuke installation.

Today's blog post falls under the category of DNN Enhancements. These are the type of items where we think, "Gee, I wish that DNN could to X or that we had Y feature," to which I immediately think, "Why not build it in XMOD!"

To kick off this new XMOD blog, I wanted to start off with a bit of an introduction to myself, my development company, and our history with XMOD. In the end, the purpose of this blog is to share our tips, ideas and experience using XMOD PRO as we help promote XMOD with the DNN Community and help share in the interactions of the great XMOD community.