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

Hi Stefan, *

Stefan Weigel schrieb:
Hallo Bernhard,

Am 04.11.2010 23:44, schrieb Bernhard Dippold:

As the author / publisher privileges can be bound to subsites, I
want to discuss the main structure of the marketing related website.

Main area will be, I think.

I don´t think so.

From what I understand, the new concept is to use the website,
created by the CMS, mainly for users focus. Developers stuff,
project collaboration stuff, resources for project members et cetera
are supposed to be on the wiki.

I've been subscribed to the website mailing list already from the beginning - and I didn't get this impression, even if it has positive aspects of course.

So, I think, we will never have something like

[...]I don´t see any concept for having subprojects like marketing or
QA or API or ux or sw or sc or whatever in the CMS. They all have
their place on the wiki.

As I think Christian is aware of the goals and the way the team decided to achieve them. On the website list he replied to my question:

"Do you plan to divide access to different areas (not only native-lang, but teams like marketing/branding, QA, ...) ?"

without mentioning any of the points you describe here:

Christian wrote:
It is possible to have different access by subsites - and by default a
member will only have access to the one subsite he requests access
for, but of course a user can be author in de project, publisher in
marketing, and subsite admn in qa project.

It is also possible to have special areas within a subsite with
different permission setup.

that's me:
I'd like to have publisher access (mainly for branding/artwork and marketing

What would the preferred hostname be? artwork or branding? or is it
meant to all be within the marketing project?

That's the reason to come up with this question here.

We want to avoid the mixture of user oriented information and
services and project orientated information and services on the
website, that we have been suffering on the website.

I'm not fully convinced - there are areas that should be presented on the website rather than in the wiki: Press material, officially approved artwork, all the stuff that shouldn't modified but used unchanged is better located on the website but in the wiki with locked pages / resources.

If we decide to replace not only the website CMS but also the wiki by Drupal (this really has not been decided - and it doesn't need to at the moment), these questions will become less important I think.

This new concept is not my invention, but my impression I got from
what I have been reading and hearing.

So this concept should be discussed and decided on the website mailing list - it's not at all a marketing only topic.

Best regards


E-mail to for instructions on how to unsubscribe
List archives are available at
All messages you send to this list will be publicly archived and cannot be deleted


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.