On Thu, 27 Jan 2011 09:40:48 +0100, Nino Novak <firstname.lastname@example.org> wrote:
thanks for posting the minutes here.
On Thursday 27 January 2011 00:56, Michael Wheatland wrote:
From what I understand, a flat structure is better for translations
could you explain what is meant by "flat structure"?
I would like to see pages with sub-pages / categories
Infrastructure and admin - for plans for implementing and improving
What for tools?!
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
It's more about the Interface not the Design. It's a Team overlapping
Structure - For Information Architecture and wireframe development
created category "Website/Structure"
Wireframe's are part of the Design Team. The Structure is Website Team.
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)
Stakeholders - Details about each stakeholder/team and their
requirements from our infrastructure
Category "Website/Stakeholder" created.
I think each Team should have their own Page in the Teams Wiki Part.
Content - Working copies of the website content so anyone can suggest
created cat. "Website/Content" and "Website/Sandbox". Content - for
content related , Sandbox - as playground.
Proposals - Discussion about bigger ideas than the current
created category "Website/Proposals".
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:
Feel free to change category names or descriptions.
UI - Coding - Animation
Unsubscribe instructions: E-mail to email@example.com
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: 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