Re: [opensuse-wiki] Navigation bar (NavBar) doesn't solve all navigation problems

Remy, Rajko, 2010/2/9 Rémy Marquis :

Hi,

I'm forwarding this answer on the -wiki ML as one could add some ideas/suggestions.

On Tue, Feb 9, 2010 at 5:28 AM, Rajko M. wrote:

[...]

...

I use HCL as example as it is really large group in need of at least 2 levels of navigational bars, in our local parlance NavBar as Template:NavBar.

http://en.opensuse.org/HCL/Laptops is example of double navigational bar.

Both navigational bars are stand alone templates: http://en.opensuse.org/Template:HCL http://en.opensuse.org/Template:NavLaptops

The rest of templates that have similar layout, like one used on http://en.opensuse.org/Documentation are created using http://en.opensuse.org/Template:NavBar .

Two templates at the top are not really elegant solution, but currently we don't have better idea how to add subtopic.

The best solution I can find is this proposal (if we define that "Board" content is a subgroup of "Community" wiki pages) : http://en.opensuse.org/Community http://en.opensuse.org/Board

As you can see, I've added a link to the more global "Community" page directly in the "Board" navbar.

Advantage is that we don't clutter the user with (too) many links, but only the link of the "parent page" (in this case, "Community"). Imho, a double navbar is just too "overkill". Add too many navigation links and the user is lost again.

The disadvantage (or advantage too) is that we need to define a very clear "tree-structure" on  the new wiki, i.e. : Community Portal  \__ Board  \__ Members  \__ Ambassadors  \__ Teams  \__ How to Participate         \__ Artwork                 \__ subtopic

Documentation Portal  \__ Installation  \__ Package Management (end user) doc  \__ HOWTOs  \__

Developer Portal  \__ Packaging  \__ OBS

...

I second what Remy presented here. This is a very elegant solution in solving the two navbar issue. I thought about that one for some time now and I cannot imagine a better solution actually .. Good job Remy! Rajko, thanks for explaining the general issue to me. What do you think about Remy's solution? Are we all three on the same page here? Do you see any issues? Best and thanks, R

...

I short conversation with Remy on IRC we came to conclusion that we have to experiment on the new wiki, as creating solutions on old wiki that are missing abilities of extensions and parser hooks leads nowhere.

I still have no idea how to organize tests as it was mentioned in topic 'New "Need consent" tag in transition table' we have some articles that we can't handle as we don't have any written or spoken policy about that.

Even worse, we never listed wiki content by type, and besides end user documentation we have quite a few other types, like developer documents, teamwork related articles, meetings, team pages, plans, etc, etc.

Yeah, we really have to separate content by "user case". See above.

...

My time is currently even more restricted as company needs more hours and the current weather doesn't cooperate, so if all will wait on me it will stretch quite a bit. I guess that Remy and you are not in a better position.

-- Regards Rajko,

-- Rupert Horstkötter, open-slx gmbh openSUSE Board Member openSUSE Community Assistant http://en.opensuse.org/User:Rhorstkoetter Email: rhorstkoetter@opensuse.org Jabber: ruperthorstkoetter@googlemail.com -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org