Hi Ben, all,
Benjamin Horst schrieb:
On Oct 12, 2010, at 6:22 PM, Bernhard Dippold wrote:
Per Eriksson schrieb:
I was looking at the Fedora project and how nicely they have
integrated their normal website with their wiki. The navigation
between the sites works seamlessly, and they look very much the
I would like to see even more integration.
Why do we need a visible distinction between wiki and website?
It would be sufficient (in my eyes) to differ between static and
If the URL shows /wiki/ or not is quite irrelevant for the user, if
he reads "static content|proposals for improvement" (linking to the
same webpage as wiki page hosting ideas for improvement and a
discussion page) or the wiki navigation with
(I don't see a reason for a "Page" and a "Read" tab in the wiki,
but I'm not very deeply involved in wikis).
I'd add these tabs as a second level of tabs just below the main
navigation (if this is possible) and keep the wiki tabs (perhaps
just a few main expandable entries) on the static webpages too.
With integrated search functionality over both areas this might
improve user's experience with our site...
I don't know if I can come up with a mockup during the next days,
but I hope you understand what I mean.
These seem like great points. Have you had the chance to think them
over further, or to create a mockup yet?
No chance for a mockup at the moment - sorry.
Thinking is easier ;-)
With the OOo website we have static webpages being outdated for years -
just because nobody was interested to modify them (or didn't get access,
didn't manage to work on CVS...).
Wiki pages are much easier to modify.
What I'd like to see is:
Our website mainly based on a wiki - containing modifiable and locked
pages depending on the content.
The main pages should be static HTML pages able to handle a maximum of
users at the same time.
Static and locked pages should have corresponding wiki page for
improvement proposals that can be turned easily in the locked or HTML
page after approval.
In the past it was not easy to move from a wiki page to the static HTML
page, but perhaps there is a feature in the wiki software?
For a user it is totally irrelevant if a page is wiki or HTML content.
She should be able to follow a consistent navigation system and search
all the content (website and wiki).
We need pages that should not be changed easily (locked) and others able
to handle the traffic after a new release (main page, download, press
The different teams can work on the wiki pages - whether they contain
the standard navigation or not. But a common login and search feature
would help them too.
I don't know about the technical background - positive or negative
effects of different servers, stability of the overall website and so
on. So my thoughts might be irrelevant.
I don't want to blow the other thread with my thoughts, because I will
be just one of the volunteers creating pages with any CMS (I'm quite
sure I'll learn to work with them - managed CVS and basic HTML coding
for OOo too). I can't admin any website, so I don't think my thoughts
are as valid as yours in the other thread.
I agree that the distinction between site and wiki is probably
meaningless and confusing to a normal user, though maybe less so if
the wiki is used just as a community tool and the website fully
covers end-user needs.
This would mean to move all the end-user stuff from creation at the wiki
to the website.
PS: One more (even more irrelevant) point. On discuss there are people
thinking about the allowance to post to all mailing lists once the user
has created his account on the website. Subscribing to the lists would
only mean to be sent the mails. Would this be technically possible?
E-mail to firstname.lastname@example.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/website/
All messages you send to this list will be publicly archived and cannot be deleted
- Re: [libreoffice-website] Website and wiki design (continued)
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