Like the discussion about should we use tables in skins, and what's the difference about compatibility and compliance... it's a bit subjective, but the step towards making your URLS friendlier is always a more positive move, regardless of SEO, let's think about the end user visiting the site - how much help would it be for them to be able to logically or intuitively navigate around a website. But even there area a few pros and cons.

Brought out in 4.6 was the ability to customise/modify some of the skin tokens that appear in the DNN skins, so I thought I'd have a look and evaluate how handy it would be.

Looking for ways to improve the speed of your slow DotNetNuke website? One of the biggest DotNetNuke websites - http://www.afl.com.au uses it, and you can too. But who's running PageBlaster? Here's how to find out.

Looking ahead at what we can expect in this release was interesting and one of a couple of things I thought was handy includes the new page import/export feature - handy for site administrators and a feature that will be well used in the future.

Finally released the new and updated DNNSkins.com website - http://www.dnnskins.com - for some great new free skins, packed, polished and ready for preview. Simply register, login, add to your cart and then check them out!

Nina Meiers is looking for DotNetNuke developers to partner with. If you're a skilled DotNetNuke developer who is able to provide ongoing support, then you might be interested in this.

Who cares about compatibility... not those who are making a living out of selling skins. Not even bothering to get a 4.01 transitional. Who really cares these days?These are the reports for the top selling skins on snowcovered... and they still keep selling - so who really cares? Failed validation, 51 Errors,Failed validation, 64 Errors,Failed validation, 110 Errors >> Mothership ...

An overview on moving and acquiring DNN sites and an overview of the new hosting environment XD Design P/L will be offering clients.

You could be regarded as misunderstood you've been caught out and admitted being 'embarrassed' about it, but when you release another build only a day or two later, without having rectified what you said was 'a mistake'... then perhaps someone needs ad awareness to the public in general.

An objective thought on the Joomla / DotNetNuke discussion that comes up from time to time and I've tried to put in my own thoughts based on experience, so also provided here, a link to my own DotNetNuke as a Business overview article I wrote a week ago for clients who ask me about why I use DotNetNuke.