Christian Boltz wrote:
Hello,
(changing the subject because this is not really about the Bug Reporting
FAQ)
Am Sonntag, 18. Juni 2006 23:49 schrieb Rajko M:
[...]
Today I was trying to figure out what would be the best logical
structure (wording, naming) of openSUSE wiki so that people find it
easy to remember and find articles.
Topic Bugs is similar to FAQ, HOWTO (HowTo), Installation, Update,
etc. It has it's global meaning for SUSE Linux and local for versions
and applications. We can go with
SUSE_Linux
Bugs
10.0
system
Well, this is what is listed in the "wiki" named bugzilla.novell.com ;-)
[...]
or
SUSE_Linux
10.0
system
kernel
[...]
or something in between.
Usually many things are version-independent, so I don't recommend to use
the distribution number by default.
The one of ideas is to structure everything similar to directory
structure on FTP servers. Once you learn one the other is the same or
easy to browse.
There's a difference between Wiki and FTP. Not everything should go into
a hierarchical tree in a wiki - and there are some symlinks on FTP when
they are useful ;-)
What to use as glue?
Simple / / / might be good, but than automatic categorizing will list
all in SUSE_Linux/ / / / and categories will be useless.
Using / is a good idea for subpages with really related topics.
Examples: Build_Service/*, HCL/*
For less related topics, create a "main" page.
Example: Pages about several KDE applications - it wouldn't be a good
idea to list them as KDE/*
Build_Service, HCL, KDE articles collected in disambiguation page is
probably more a wiki way.
I'll call it index.
To one that types KDE in search, will get index page to select articles
about applications, startup concepts, etc. Further indexes can be
provided on separate pages or as paragraphs in one page. Both are
searchable so the only criteria to select one over another is
comfortable size for edit.
Important in both cases: Enter the correct categories - these are good
glue ;-)
That is the point "correct categories". We don't have easy to follow
naming structure. Everyone is free to name articles and categories at
will, and that doesn't bring any good.
One of variants is to build groups as Basic_Topic/ / / and locate
index that will point to the articles in top node Basic_Topic. The
other way around, back to the top node, is already for free :-)
Manually created and maintained indexes are a lot of work for
editors, but it is easier to educate few editors how to build and
maintain indexes than all writers.
You can simply link to Category:something and get an index for free
also ;-)
Again, that "something" is the main problem.
Example:
Virtualization, Virtual Machines, Emulators, and probably few more
expressions for one thing. If everyone select one of names than we can
see few articles about XEN listed in different places.
Regards,
Christian Boltz
I agree that categories are good glue, but their usefulness depends on
systematic usage of words.
I have multiple tasks here, to fight old habit to see all solutions as
directory structure (/ / /), learn wiki philosophy and how they
organized document tree, and in the same time look for optimal layout :-)
Not easy.
And all started with "Frontpage Redesign".
After reading previous articles, try to find out where the problem is,
it was obvious that main problem will be to make menus easy to use (user
friendly) and that all will develop beyond simple menu arrangement.
--
Regards,
Rajko.
Visit http://en.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
