Hi Nigel Kennedy,
You can safely ignore that constructor, because the code executed there takes care of some unique blogs internal functionality.
The constructor for your module can look like this:
| foreach (GenericContentElement element in ConfigHelper.Handler.GenericContentProviders)
| contentSettings.Add(element.ProviderName, element);
Because Sitefinity is supporting multiple providers in its modules, this constructor simply loops through all the providers for the current module and adds it to the static contentSettings field. This way, when you work with the data later on, you are able to create a new instance of BlogManager class and specify with which provider you are going to work (e.g. one provider can store blogs data in SQL database, another provider can store blogs data into an XML file, and so on).
Sitefinity is built on top of the standard ASP.NET 2.0 provider model, so understanding that concept would help you a great deal when developing for Sitefinity. Here is an article where you can find more about it:
the Telerik team