It’s been several years since I last updated the skin on my site. Thanks to Ralph Williams, the site is looking really good again and it’s responsive. If you need a new design for your site, I highly recommend him. However, the process to get to this blog post was quite tumultuous – chock full of hours troubleshooting and continuous frustration spread over the past week. Simply put, my site “appeared” to be loading okay whenever I came to it, but I rarely browsed my own site. The process of rolling out my new design had revealed to me that this couldn’t be further from the truth.
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?