Msg#: 4643171 posted 3:33 am on Feb 7, 2014 (gmt 0)
We have a joomla site with a top menu something like
Home |Our Widgets | contact us etc
If you mouse over "our widgets" you get a submenu of
Blue widgets Green Widgets Chartruese widgets.
The problem is that the menu choice for Our Widgets has content which is an overview of our widgets.
One of the people involved thought that a lot of people might not realize that they can click on Our Widgets. He wanted the mouseover of Our Widgets to do
Overview Blue Widgets Green Widgets Chartreuse Widgets
Where "Our Widgets" and "Overview" point to the same page. The idea is that people might be more likely to hit the "our widgets" page with the different menu item pointing to it.
I realize that there will be dupe content issues and will take care of that through a joomla extension.
My questions are
1. How savvy is the average user today.. Would most people realize that they can click on the "our widgets" even though the sub menu is there . The target demographic is young people 18-28 or so with a high school education.
2. If we change things to work for those who wouldn't think to click on it, will we annoy or confuse those who would think to click on it.
Msg#: 4643171 posted 5:03 am on Feb 7, 2014 (gmt 0)
I realize that there will be dupe content issues
? Two links pointing to the same page isn't duplicate content. And you are talking about the same target page, right?
How savvy is the average user today.
It's less about user savvy and more about users' prior experience with other websites. As a user I've had two equally annoying experiences:
#1 a menu title (like "Our Widgets") that doesn't link to anything in its own right, but only triggers a dropdown, even though other seemingly identical menu items are links in their own right #2 a menu title (like "Our Widgets") that's a link in its own right but also triggers a dropdown
... and there's no way to know ahead of time which you're dealing with.
Given a choice between "annoying only" and "annoying but also useful" I'd go with #2. Keep your terminology intentionally generic, like "Overview".