Hi,
I've spent some time working on documenting the templates in
wiki.o.o as suggested in [1], so here is small report and some random
thoughts:
1. Every template (except a few - more on this below) in wiki.o.o
instance now has its /doc subpage with information about how to use
the template (code), general description, where to use it/not to use
it and in some cases there is also list of related templates. The
documentation could definitely not perfect, but IMHO it is a good
start to having general policy that every template should be
documented.
2. It seems nobody has objections against making it policy
that every $template has to be documented in $template/doc, so
I'll mention it in [2] (this is yet to be done if nobody raises
objections).
3. The exceptions for which I did not make /doc subpage, as mentioned
in point 1, are:
Template:App \
Template:Appg |
Template:Appk +-> I don't understand what are these good for
Template:Appj /
Template:Meeting - marked as 'template to rethink', looks useless to me
Template:Infobox software, Template:Information: these two templates
look very similar, I don't get the difference. Are both really needed?
4. TOCRight template: do we really need this? In en.o.o, only a few
pages use this template and IMHO it doesn't look very nice.
5. The templates related to portals were taken from wikipedia, where
these templates are also perfectly documented. IMO it would
be useless to copy their documentation to wiki.o.o, so I've
basically just linked the documentation to our wiki.
6. There are several navigation bar templates in the wiki. I think
these templates might be placed into something like
[[Category:NavBars]], so it would be easier to find proper
Navbar when creating new article. Wikipedia uses something similar.
What do you think?
7. I've fixed capitalization of categories, so all the categories
now follow the naming conventions.
8. ATM, the documentation of a template is displayed below the
template content, which is fine for small templates like AI [3], but
isn't so fine for bigger templates like Article boilerplate [4]. If
the user opens [4], the documentation should be better visible.
I see two options, none of them ideal:
a) put the documentation above the template content
b) make the template content <includeonly>, so only the documentation
would be visible, but then it couldn't be used as an example
of recommended article layout.
Any ideas?
9. Template:{Torrent, Video}
These two templates were implemented using titled-click-external
template, which
a) isn't in wiki.o.o
b) is deprecated according to Wikipedia
So I've reworked Video and Torrent templates using
[[image:Video.png|22px|link={{{1}}}]] syntax. It should work the same
way as before except that it now adds another icon representing external
link [5]. I don't know how to get rid of this icon (does it mind
actually??), so if ((this is not desired && can not be fixed) ||
(there are some other drawbacks I didn't notice)), then please revert
these two templates back.
[1] http://lists.opensuse.org/opensuse-wiki/2010-02/msg00055.html
[2] http://wiki.opensuse.org/Help:Template
[3] http://wiki.opensuse.org/Template:AI
[4] http://wiki.opensuse.org/Template:Article
[5] http://wiki.opensuse.org/User:Puzel/Test
Petr
--
Petr Uzel, openSUSE Boosters Team
IRC: ptr_uzl @ freenode
Team,
JFYI, I'm in discussion with the forums admin team in order to keep
this going. Will keep you in the loop.
Best,
R
2010/2/26 Jim Henderson <jhenderson(a)novell.com>:
> I don't know that any of us have direct familiarity with the RSS bot, but I think I know who wrote it (I can check and see) - if it's written by the person I think it is, he'd be able to let us know the capabilities pretty easily.
>
> Jim
>
>
> --
> Jim Henderson
> Program Manager, Novell Testing
> Novell, Inc.
>
>
>
>
>
>
>
>
>
>
>
>
>
>>>> On 2/26/2010 at 05:48, in message
> <26d1a5471002260448o5b6afa85r76f3e24021a7436b(a)mail.gmail.com>, Rupert
> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>> All,
>>
>> 2010/2/25 Thomas Schmidt <tom(a)opensuse.org>:
>>>
>>> According to http://www.vbulletin.com/ this is a
>>> commercial product, I cannot even download the documentation...
>>> So we need the technical forums admin to do that.
>>>
>> I just got notice from Kim that he's rather unavailable these days due
>> to too much on the plate atm. That said, I'll ask him about the
>> forumsbot configuration capabilities in a private conversation and
>> forward the answers to you. Also I try to get the vBulletin
>> documentation we need from him. Furthermore I herewith CC: the rest of
>> the admin team in order to ask for their involvement. Please keep the
>> CC: as is. I'm sorry for the inconvenience.
>>
>> Forums admins,
>>
>> we need some help/input regarding the FlaggedRevs Wiki QA, i.e. the
>> configuration capabilities of the RSS forumsbot. Kim is rather busy
>> these days, so I'm wondering if you, Carl, John, Jim would be able to
>> jump in as an interim replacement?
>>
>> In order to sync up with the current discussion, please read this thread [1]
>>
>> Thanks,
>> R
>>
>> [1] http://lists.opensuse.org/opensuse-wiki/2010-02/msg00069.html
>
>
--
Rupert Horstkötter, open-slx gmbh
openSUSE Board Member
openSUSE Community Assistant
http://en.opensuse.org/User:Rhorstkoetter
Email: rhorstkoetter(a)opensuse.org
Jabber: ruperthorstkoetter(a)googlemail.com
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Jim,
2010/2/26 Jim Henderson <jhenderson(a)novell.com>:
> Looking in the admin interface, it looks pretty straightforward to set up a feed; it's not a custom bot, but part of the admin functionality in vBulletin. We'd need to create a forum for the feed to feed into and the URL to the XML doc that provides the RSS feed.
>
> We could test this in the sandbox and then reset it for a public feed view.
>
Actually that's exactly what I'm planning to do as soon as we thought
the "hack-possibilities" to auto-merge the thread whole through.
Grabbing the feed and posting doesn't seem to be an issue, providing
RSS with Hermes is fine as well. Remaining and most important now is
to investigate the re-opening/merging of subsequent threads related to
one single article "foobar"
All,
vBulletin doc is at http://www.vbulletin.com/docs/html/
Best,
R
> Jim
>
>
> --
> Jim Henderson
> Program Manager, Novell Testing
> Novell, Inc.
>
>
>
>
>
>
>
>
>
>
>
>
>
>>>> On 2/26/2010 at 05:48, in message
> <26d1a5471002260448o5b6afa85r76f3e24021a7436b(a)mail.gmail.com>, Rupert
> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>> All,
>>
>> 2010/2/25 Thomas Schmidt <tom(a)opensuse.org>:
>>>
>>> According to http://www.vbulletin.com/ this is a
>>> commercial product, I cannot even download the documentation...
>>> So we need the technical forums admin to do that.
>>>
>> I just got notice from Kim that he's rather unavailable these days due
>> to too much on the plate atm. That said, I'll ask him about the
>> forumsbot configuration capabilities in a private conversation and
>> forward the answers to you. Also I try to get the vBulletin
>> documentation we need from him. Furthermore I herewith CC: the rest of
>> the admin team in order to ask for their involvement. Please keep the
>> CC: as is. I'm sorry for the inconvenience.
>>
>> Forums admins,
>>
>> we need some help/input regarding the FlaggedRevs Wiki QA, i.e. the
>> configuration capabilities of the RSS forumsbot. Kim is rather busy
>> these days, so I'm wondering if you, Carl, John, Jim would be able to
>> jump in as an interim replacement?
>>
>> In order to sync up with the current discussion, please read this thread [1]
>>
>> Thanks,
>> R
>>
>> [1] http://lists.opensuse.org/opensuse-wiki/2010-02/msg00069.html
>
>
--
Rupert Horstkötter, open-slx gmbh
openSUSE Board Member
openSUSE Community Assistant
http://en.opensuse.org/User:Rhorstkoetter
Email: rhorstkoetter(a)opensuse.org
Jabber: ruperthorstkoetter(a)googlemail.com
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Hi, I added the current state of the bento theme[1]
to our wiki staging server [2]. It can be set in Preferences->Skins.
There are some issues to solve, I think we need a much wider
content area.
Greetings
[1] http://gitorious.org/opensuse/webdesign/trees/master/design_concept/theme_o…
[2] http://wikistage.opensuse.org/Test?useskin=bento
--
Thomas Schmidt (tschmidt [at] suse.de)
SUSE Linux Products GmbH :: Research & Development :: Tools
"Don't Panic", Douglas Adams (1952 - 11.05.2001)
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
