Description of problem: Currently users have to go through "About us", "Support" or "Community" to find the wiki whereas it should be one click away. Perhaps "Documentation" would be a good name for the link but whatever the name it should be on most every Mageia web page.
Here's a thought: rolldown menu items. The banner has the main menu headers, and when you mouse over them a menu rolls down with links. So to get to the wiki in one click just mouse over Support and click the Wiki link. There was a time when I knew the JS code to do this, but it shouldn't be too difficult to look for.
CC: (none) => bogusman222
(In reply to comment #0) > Currently users have to go through "About us", "Support" or "Community" to find > the wiki whereas it should be one click away. That was on purpose. The wiki isn't, in itself, a goal, but a support of various types of documentation. > Perhaps "Documentation" would be a good name for the link but whatever the name > it should be on most every Mageia web page. If it's for documentation, for now, it goes under Support or Community. If we are to add Wiki again in the top level of navigation, why not add IRC, forums, blog, mailing-lists, calendar, etc. ? However, the sub-nav of the Community section could be improved (with such tabs as above).
CC: (none) => rdalverny
It's actually quite easy using jquery (or rather one of its plugins). I once did that somewhere else but I have to look up the name. Any thoughts, Romain?
CC: (none) => oliver.bgr
Could be done, yes. But, I'm not sure mouse* callbacks are so nice now that there are touch devices; better have a consistent behaviour between click and touch. And I'm not sure either about such modal navigation. Prototypes welcome.
(In reply to comment #2) > (In reply to comment #0) > > Currently users have to go through "About us", "Support" or "Community" to find > > the wiki whereas it should be one click away. > > That was on purpose. The wiki isn't, in itself, a goal, but a support of > various types of documentation. > I'm puzzled. As a community driven distribution does the wiki which is written by/for the community take second place to other documentation which by the way I haven't found? > If it's for documentation, for now, it goes under Support or Community. > > If we are to add Wiki again in the top level of navigation, why not add IRC, > forums, blog, mailing-lists, calendar, etc. ? As I see it the wiki should be a first stop for "How do I?" help. The forum and IRC are for interactive help on things not yet covered in the wiki. The blog, mailing-lists, calendar, etc. are as I see it for announcements and an overview of what's happening in/to "OUR" as a community distribution.
+1
CC: (none) => zen25000
The problem is that the wiki, as it is structured right now, is not really built to offer HOWTO stuff. The content just isn't there. Most of that content can be found in the forums, though. The way I see it, the first step to getting help is the forum, with the occasional link to a wiki age that will hold stuff that people frequently have trouble with, like the Maqeia section in the forums.
Created attachment 2477 [details] Possible hack for rolldown menu Since my CSS skills are a bit rusty, this doesn't really work well, but as a proof of concept, I think it's enough. I took the source for https://www.mageia.org/en/map/ and modified it a little bit. I added a few JS functions to manipulate hiding/unhiding the pulldown menus. I added a rolldown menu for Support. It's actually an invisible table. If you mouse over it you'll see a previously invisible table with links. The problem is that for some reason there is some padding between the li and the table it contains, I'm not sure why. So that you can't actually click the links there, but it's a step in the right direction (I think). (Ignore the fact that the rest of the page looks all funky, that's not the point.)
@Romain: As an interim solution, as for many areas there's no other documentation for endusers exccept the wiki, why do you want to hide it? I think that's no good idea, if there are no other platforms with documentation (currently we only have the installer documentation, which is also not that visible IMHO) AND no content. So why make it harder for the users currently to reach documentation that we currently have and users helped to created? Sounds really strange to me ... Also i think it's quite bogus to say this is because of the switch to the new navbar, as that was mainly your decision from what i remember. And i still think it uses more space for less useability, the previous one was much better and had more links to important stuff, and it needed less space. But what do i know ... :/
CC: (none) => doktor5000
@Max: I suggested this via mail yet, when I updated the startpage for Mageia 3 - why don´t use a CSS-Framework? There you have dropdowns and navigations integrated. You only have to customize it for your individual project - I did some sites with Foundation... Let me know...
CC: (none) => db
(In reply to Florian Hubold from comment #9) > @Romain: As an interim solution, as for many areas there's no other > documentation for endusers exccept the wiki, why do you want to hide it? I > think that's no good idea, if there are no other platforms with > documentation (currently we only have the installer documentation, which is > also not that visible IMHO) AND no content. > > So why make it harder for the users currently to reach documentation that we > currently have and users helped to created? Sounds really strange to me ... @Romain: Ping? Can we please get the Wiki and http://doc.mageia.org/ as top-level links in the navbar, until another solution has been implemented/proposed? This bug was opened more than 15 months (!) ago, is still valid and nothing has happened in between, when there could have been an easy workaround in place in the meantime.
something like this ? (available in less that 5m on main site)
(In reply to Manuel Hiebel from comment #12) > something like this ? (available in less that 5m on main site) Hmmm, maybe you missed to add an attachment ... ?
no, look at the nav bar ;)
Thanks Manuel. I'm marking this as RESOLVED/FIXED.
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to Manuel Hiebel from comment #14) > no, look at the nav bar ;) Sorry, professional blinkers :/ Anyway, thanks for changing this! :D