I wanted to log two enhancements to the Blog module in Gemini but I could not see how to do so (I logged into Gemini successfully, navigated to the Blog home page in Gemini but could find not 'create issue' link). Therefore I outline below the two enhancements so that someone else (on the Blog Project team?) could introduce them to Gemini:

Both enhancements will improve the Blog module in terms of Search Engine Optimisation (SEO):

SEO Enhancement request 1)
Ensure that in an individual blog entry the title of the blog entry appears within <H1> or within <H2> tags (currently it appears between <span> tags that assign it a class="Head"). I request this as the accepted best practice with other leading blog platforms is that the title of the blog entry appears within <h1> or <H2> tags, the contents within such 'Headline' tags are assumed by the search engines to represent a strong indication of what the blog entry is about and therefore are weighted with much higher importance when it comes to ranking the blog entry for relevant keywords. The search engines do not assign such a weight to something with a class="Head".

SEO Enhancement request 2)
With the DotNetNuke blog module each blog entry resides at two different URLS. For example the following two URLs (taken from the Blogs on Dotnetnuke.com) are generated by the Blog Module but contain exactly the same content and mark up:
URL Type A) http://www.dotnetnuke.com/Default.aspx?tabid=825&EntryID=1420
URL Type B) http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1420/Default.aspx

URL Type A, for example, is the permalink, while URL Type B can be found embedded in the title of the blog entry on your the blog's main page.

This is very sub-optimal from the point of view of a search engine - the same content exists in two places (and so the value of the content for the search engine is 'shared' across 2 pages, instead of being 'concentrated' in one page.). To resolve this either:

(a) all URLs of Type B should be made in the Blog module to be like URL Type A (Permalink)
    or
(b) vice versa

As far as I can see it, of the two options above option (a) is by far the best as this is 'future proof' (e.g. if any changes are made to the 'page name' in the page settings of the 'mother' blog page the URL will continue to work as it only contains two 'fixed' parameters (tabid and entryid) and the 'page name' (in URL Type B above the Parent page title ="Community", child page title = "Blogs") is not part of the URL).

I hope my explanations above are enough for someone to introduce these enhancements requests into Gemini. If I need to clarify anything further, let me know!

Eoghano

eoghano,

Please go here: http://support.dotnetnuke.com/project/Project.aspx?PROJID=23

You must login in order to create an issue.

Once you submit your ticket in there, the project leads (in this case, me) will review the validity on the issues and "move" the ticket into the Module's "Project.

Hope this helps.  (I know it is not intuitive - but the good news is that we know about it and are discussing ways to improve)

Antonio,

I see that the two proposed enhancements that I logged into Gemini (as you advised) have not yet been either approved or rejected by you. Have you had a chance to look at them yet? The links to the issues are above.

Thanks

eoghano