If you didn’t already know, CMS is an acronym for “content management system.” A CMS is used by many developers, consultancies, and companies to build their website. It’s an incredibly common thing to do, as any flavor of CMS you choose will always save you effort and money, compared to building a website from nothing. This is especially true if you look at the lifetime investment of your website. Using a CMS framework or solution of some kind just seems to make sense. After all, this is what I’ve built my own career upon since 2001. However, then, CMS was known as a portal or portal framework. That’s a long time ago, so it’s not a bad idea to take stock of things every now and thing to see if what you’re doing is the correct thing. To this end, I asked myself, “How is CMS doing right now, and does it make sense to still be doing CMS-related work in the future?”
We just had the first Bay Area DotNetNuke User Group (BayDUG) meeting after having a break for over a year now. It was a great presentation. Chris Hammond did an overview of the features that DotNetNuke now offers to people that enable them to being rolling out their mobile-friendly websites. As great as the overview was, it was missing something… Why would you use one feature over another? What should I think about before deciding the “best way” for my website when building my mobile-friendly site?