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

Re: [tdf-discuss] main LibO website content [was: deb installer - have to manually modify link]


Hi David, *

This thread certainly belongs to website@libo, because such details should be discussed among all people interested in this area.

As I read there, some community members already put content on these pages, and at least Marc and Michael wanted to contribute to the Silverstripe site too - so discussing here might result in double work.

More comments below...

David Nelson schrieb:
[...]
On Tue, Dec 7, 2010 at 22:04, Christian Lohmaier
<lohmaier+ooofuture@googlemail.com>  wrote:
Well I'm kind of puzzled that after weeks and weeks, scores of
messages in the lists and various conference calls, there's very
little concrete progress with producing content.

Yes, I'm also very disappointed at that, but I don't have an answer as
to why that is so :-(

I personally just did not have enough time to come up with content
myself, and I was hoping for the marketing team to come up with some
content... (and also with some artwork)

Sorry for not providing any artwork - but there has not been any request, neither on website@libo, nor on marketing or design@libo (the latter might be the appropriate list IMHO).

Probably this is due to the fact that nobody really had the time / dedication to work on these pages. So I still hope this might change.

I can propose an IA. Already we can work with the specific items you
mentioned below. Let's get started with those, and I will probably
find some suggestions to put to you.

I'm quite sure that the people working on the pages up to now did have some ideas how to organize the website. Some of them already created native-lang pages, so you should ask them for their structure.

Just "unpublishing" their content without contacting them on the list before might have annoyed them - they might have thought you don't respect their work on structure and content but just want to publish your ideas.

I use Gimp and Photoshop, so I
can do any needed stuff, too.

If you want to, you're welcome to do so.

Please be aware that the website should reflect our visual design - even if this is not finished yet, I'd like to see all artwork integrate the design of the TDF logo and the other graphics provided at the wiki:
http://wiki.documentfoundation.org/Marketing/Branding

You might also want to refer to the installer and start center images:
http://wiki.documentfoundation.org/File:LibreOffice-Initial-Artwork-Package.zip

But it might be easier to ask at the design list for support in this area.

[...]

Source files: no, I only have the files as they appear on the site.
https://github.com/tdf/cms-themes/tree/master/tdf/images/buttons

They can already serve as a basis. We can see what else is needed as I
start posting content for consideration.

As already discussed in another thread, the buttons have either to be removed or to extended a lot in order to work with the improved download scripts proposed on website@libo.

So I'd suggest to start with the structure and ask for graphics when the structure and content has been decided.

Best regards

Bernhard

(working on too many other topics to contribute to the website in a substantially way...)

--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived for eternity ***

Context


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.