[dokuwiki] Re: Improve the repository plugin
- From: Anika Henke <anika@xxxxxxxxxxxxxxx>
- To: dokuwiki@xxxxxxxxxxxxx
- Date: Sun, 04 Oct 2009 19:17:03 +0100
Michiel Kamermans wrote:
Anika Henke wrote:
<<There shouldn't be many tags which are related to one plugin only,
i.e. replace too specific tags with more common tags (or just remove the
too specific tags): E.g. don't have 'youtube, sevenload, dailymotion',
when only 'video' is the most important bit. Another example is my ABC
plugin, which shouldn't use 'abc' while just 'music' is enough. Or
'star' and 'stars' should just have 'rating' and so on.>>
Don't forget that a unique tag for a unique plugin is more likely to
lead users to find it if they've heard people talking about it. Keeping
in one or maybe two reasonably unique keywords can expedite retrieval.
Yes, I agree. As I said, those rules are not set in stone and should not
always be applied when reasonable.
<<Only use the most basic words, e.g. use 'collapse' instead of
'collapsible' and 'fold' instead of 'folding'. >>
While that seems a good idea, users will typically search for things
based on what they effect, such as "collapsible" ares or "folding"
areas, not on what they do, i.e. 'collapse' or 'fold'; I'd highly
recommend using attributive keywords in cases like these.
Tags are not there to replace a search. People normally won't search in
a tag cloud.
The word "collapsible" can and should still appear in the plugin page
itself (and therefore will be found by users who search for it) and
maybe even in its description. But having "collapse collapsible
collapsing" in a tag cloud renders it null and void ...
<<While we're at it, we should also check if the tags make sense at all.
E.g. the skill plugin shouldn't have a tag 'skill' and the stars plugin
neither 'skill' nor 'star' nor 'difficulty'. Or the 'faq' plugin
shouldn't be tagged with 'faq' but with 'headline' and 'style' instead.
(Let's ignore for now that the names of these plugins are misnomers.) >>
Be careful with overzealous pruning: as a user I would fully expect an
FAQ plugin to have the keyword 'faq', because that quite aptly describes
what it does.
The thing is, the FAQ plugin has nothing to do with FAQs!
Unless you can rigidely define what we should mean with
'tag' in the dokuwiki plugin context, most people will consider a tag to
be a keyword descriptor for the plugin and its functionality. As such,
since the skill plugin deals with skills, it should have 'skills' as
tag,
No, the skill plugin does not deal with skills. That's why I said that
tag should be removed ...
and the FAQ plugin deals with faq functionality, and so should have
'faq' as tag, too.
As I said before, the FAQ plugin has no FAQ functionality. Take a look
at those plugins I mentioned and you'll see what I mean.
It will only confuse users who click on the faq tag and won't find
anything related to faq ...
Which kind of leads me to the real question: can we describe what a
"tag" is supposed to be in the context of dokuwiki plugins? If so, then
that should serve as pruning basis. If not, then perhaps we should do
that first, because otherwise people will have no guiding principle or
clear definition of what their tags should be after the pruning, when
new people add new plugins to the list.
We could take my "rules" as a discussion basis for that. You can add new
rules and/or critise the current rules.
As I said before, I believe when new people add new plugins to the list,
the list of pruned tags will be enough to guide them.
Anika
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
Other related posts:
