This entry is the first in a series about building SEO modules for DotNetNuke.  It follows on from my earlier posts about building a module that is optimised for search engines, but in this series I am going to build a module and show the relevant steps and pieces of code that go into making it.

For us 'English as an only language' folks, it's easy to skim over globalization issues.  But with a global audience, sooner or later you'll run into problems.  Here's one of mine.

There are three main fields you should be concentrating on for each and every DNN page, and anyone who edits or maintains a DNN site should be doing this in their websites, each time they create or modify a new page.

If you're building or maintaing a DotNetNuke module, then you need to consider these factors to see if the module is Search Engine Optimised, or Search Engine Compromised.

Recently I've been requested by a number of people to explain the differences between the iFinity Friendly Url Provider, and the iFinity Url Master module. The obvious difference is one is free, and the other you have to purchase a licence. To help determine which one you need, I've done up a reference table of the features.

One of the things that has been bubbling away at the back of my thoughts for a while now is ‘DotNetNuke needs an API’.  Of course, DNN already has loads of API, what I mean by this is an open, extendable, web-service style API.  Lots of times I come across something I need to do, and I immediately think – ‘now this is where an API would be handy’.  So, with a concrete project that I needed to do that really was best done with an API, I turned thoughts into code, and the result is a very early stage DNN Web service API.

I spent a whole cache of hours yesterday tracking down a bug reported with the iFinity Friendly Url Provider. This bug was that the RSS feed button which is in-built into DNN modules didn’t work. The problem turned out to be the same old thing that causes the majority of incompatibility between my Friendly Url Provider and other DNN Core functions and DNN Modules – misuse or non-use of the Friendly Url Provider API. So, please, if anyone writes DNN code for anything, please see what I have to say

With IIS7 starting to make inroads into the installed DNN base, I've fielded a few questions about IIS7 compatibility and my existing work with DotNetNuke friendly Urls.  I know things are going to change in the future with the upcoming DNN 5 release and (probably) taking advantage of native IIS7 features.  Here's my outlook on what we might expect.

Ever since I decided to write a more comprehensive version of the iFinity Friendly Url Provider, I've had plenty of feedback, tips and requests for features.   I've got the Beta version ready for testing, and the final release won't be far behind.  Read the details on what it is and what it does.

The Tagger module is proving to be quite popular and has been implemented on quite a few sites.  I've had a couple of questions relating to it's use and how exactly to get the best from it, so here's some insight into how it works, and how to get the most from it.