Menu Comparisons
Last Post 03/20/2006 6:13 AM by Tim O'Brien. 5 Replies.
Author Messages
lynn
Nuke Master
Nuke Master
Posts:276


--
03/08/2006 7:53 AM  

Hi Lee
I have been following a DNN forum post entitles "Why does 100% Css Desing Fail in Dnn? (No Tables)" http://forums.asp.net/718428/ShowPost.aspx

I noticed you have an interest and have contributed to this post.

I read with great interest the post of isomies who has found a way of making a validated DNN site.  I am looking forward to learning how he has achieved this, if he shares his knowledge, which I feel he will.

However, I was surprised to find that Isomies uses both HouseOfNuke and Scott McCulloch's Top Menu and on his site for validation reasons.

Do you have any knowledge or experience of TopMenu and or thoughts on this?
How does one menu compare with the other, I understood that HouseMenu was the menu to choose for SEO etc. Or is one HouseMenu better suited to vertical navigation, and TopMenu best for horizontal?

I would be interested to hear your views and opinions.

Regards

Lynn

Lee Sykes
DNN Creative Staff
Nuke Master VI
Nuke Master VI
Posts:4945


--
03/08/2006 8:07 AM  
Hi Lynn,

Yes it's a very interesting discussion that is happening in that post. - It is the first DNN site I have seen that completely validates. - DNN history in the making?!

Regarding the menu. I haven't used the Top Menu by Scott and I would be interested to hear the reasons why isomies has opted to use 2 different menus.

Regarding SEO, this applies to any menu that is a CSS based menu, so if there are any other alternative CSS menus out there which compare functionality with the HouseMenu then they are both likely to have an equal footing in terms of SEO. - The reason a CSS menu is search engine friendly is beacuse the links are easily accessible to a search engine and not hidden behind Javascript functions.

You can find out more info on the TopMenu here: http://www.ventrian.com/Products/Sk...fault.aspx

Hopefully isomies will share some info on his skin soon,

Thanks,
Lee Sykes
Site Administrator
Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

Twitter: www.twitter.com/DNNCreative

Lee Sykes's Facebook Profile
lynn
Nuke Master
Nuke Master
Posts:276


--
03/08/2006 8:59 AM  

Hi Lee

Thanks for the speedy reply.

Isomies is not very clear why he used both menu types, hopfully he will elaborate at a later date.

Regards

Lynn

lynn
Nuke Master
Nuke Master
Posts:276


--
03/18/2006 6:46 AM  

Hi Lee

Answer from : isomies in DNN Forum


They both produce unordered lists.

The design for www.damnwitty.com just happens to be built that way. There is no real rationale for this, except I had them both to hand! Both work well and I would recommend them equally.

*****************************************

However, perhaps you might be able to clear up another menu question.

Re: DNN Forum Why does 100% Css Desing Fail in Dnn? (No Tables)

http://forums.asp.net/718428/ShowPost.aspx  page 15

slope wrote:

I would recomend a pure css menu without js or .hct
There are a few good ones out there, take a look at
With menues like this even large sites with thousands of pages will be easy to navigate. This is espacially true for the vertical menues, as horizontal can get rather ugly if you need lots of first level menues, because the width of the menu will be wider then the browser window. With these ones you will not have that problem. 

css.maxdesign.com.au/listamatic/

http://www.seoconsultants.com/css/menus/vertical/

http://www.cssplay.co.uk/menus/dd_valid.html

http://www.cssplay.co.uk/menus/flyoutt.html

My Question:

Would these menus be used with Housemenu so that page links are automaticaly created.  Or another method?

Thanks.

Regards

Lynn

 

 

Lee Sykes
DNN Creative Staff
Nuke Master VI
Nuke Master VI
Posts:4945


--
03/20/2006 3:57 AM  
Hi Lynn,

This is the beauty of a CSS menu. - All CSS menus are created from an unordered list of links. This means we can take any CSS menu code and apply it to the HouseMenu.

The links there provide the CSS code that you need to implement within the HouseMenu CSS, they are not 'menu modules.'

The HouseMenu automatically creates the unordered list of links from your DNN pages, whereas on an ordinary static website you would manually type in the list of links and then apply your css menu code to those links. - All we have to do in DNN is apply the css menu code to the HouseMenu.

So yes, you can adapt any CSS code from any CSS menu and apply it to the HouseMenu and still have all of the pages automatically added to the menu.

Hope this makes it clearer,

Thanks,
Lee Sykes
Site Administrator
Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

Twitter: www.twitter.com/DNNCreative

Lee Sykes's Facebook Profile
Tim O'Brien
Nuke Newbie
Nuke Newbie
Posts:5


--
03/20/2006 6:13 AM  

Well, as I have been mentioned here I thought I would respond!

The main points have been answered already, but I'll just expand a little bit more.

The House menu is very good and free, if I have a suggested improvement it would be that it had a few more options to turn off some of the id's that it generates to keep the page html as small as possible. Of course, having every element of the unordered list both the "li" and "a" elements with indicators of the active status and with unique id's makes it extremely flexible.

I have recently altered the standard links skin module to generate a unordered list and an active class on the current pages "li" item which gives most the styling required for decent css menus for a top level set of links and keeps the html light.

 



---