Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Mike,

nice to see you here, and thanks for your thoughts :-) And thanks to
Michael who currently takes care of so many things being documented in
the wiki - great to see as well!

Am Donnerstag, den 27.01.2011, 04:47 -0800 schrieb Mike Houben:
On Thu, 27 Jan 2011 09:40:48 +0100, Nino Novak <> wrote:
On Thursday 27 January 2011 00:56, Michael Wheatland wrote:

Infrastructure and admin - for plans for implementing and improving
the tools

What for tools?!

Mmh, just guessing, but maybe the administration interfaces, the
download counter, the mirrorbrain download magic, the Piwik data
collection, ...

Category "Website/Admin" created (as "Infrastructure" is already used) 

Web Design - for Theming and standard reusable element development

Do I understand it right that this is about all those issues of the 
Design team that are related to the website? 

I created a category Website/Design but maybe the other way suites 
better ("Design/Website"???) 

It's more about the Interface not the Design. It's a Team overlapping

True, but not harmful :-) Maybe even fruitful.

Structure - For Information Architecture and wireframe development

created category "Website/Structure"

Wireframe's are part of the Design Team. The Structure is Website Team.

Hhm, information architecture might also be supported by the Design team
(user experience, usability, information architecture, ...). Some of the
stuff will be delivered in wireframes that can then be enhanced
(finalized) by visual design.

But, it (to me) it doesn't matter who wants to come up with proposals -
e.g. a wireframe design. Whether it is the Website team, the Design
team, or anybody else. Usually - and hopefully - we will end up in close
cooperation, so it rather matters that everybody is aware of "where to
find" stuff.

So, why not adding categories for the teams being involved to a certain
degree? For example, we might additionally add the (not yet existing)
"Design/Support" to (just a proposal) "Website/Development". Same
applies for Marketing, Local Teams, ...

Resources - A collection of logos, elements, images, links to videos

Created category "Website/Resources" 

Shouldn't this better be a Link to where the Design Team has his Inventory
for all?! (So everything is up-to-date and no duplicate problems)

Good point - something I also thought about, because we e.g. created the
MIME icons (provided to the development), supported the development of
the branding (important for many teams) and will also continue with the
presentation template (which is mainly used by Marketing). Weird
thing :-)

So I think Mike has a good thought here: How about providing the "final"
things to the website team, where it can be "just used"? I expect those
things to be important to the outer world as well. In this case, the
development, the discussions ... might be done within the Design Team;
until the stuff is ready for production use.


Have I missed anything?
Can someone with wiki moderation/admin experience weigh in on how
better to practically implement a structure.

Categories can be used for quick categorizing existing pages.

Find all Categories here:

Thanks Nino, thanks Michael and Mike!


Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.