From the conference call outcomes, it is clear that the wiki will
provide a pivotal role in coordinating the team.
There has been a call to restructure the website wiki page. The
question is how should we approach this.
From what I understand, a flat structure is better for translations and i10n.
I would like to see pages with sub-pages / categories dedicated to:
Infrastructure and admin - for plans for implementing and improving the tools
Web Design - for Theming and standard reusable element development
Structure - For Information Architecture and wireframe development
Resources - A collection of logos, elements, images, links to videos etc.
Stakeholders - Details about each stakeholder/team and their
requirements from our infrastructure
Content - Working copies of the website content so anyone can suggest changes.
Proposals - Discussion about bigger ideas than the current infrastructure.
Have I missed anything?
Can someone with wiki moderation/admin experience weigh in on how
better to practically implement a structure.
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 ***
- [libreoffice-website] Restructure of website Wiki · Michael Wheatland
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