Hi Matt, :-)
Like I said, best to consider that Michael Meeks is the "client" for this page.
On Fri, Feb 18, 2011 at 02:40, David Nelson <email@example.com> wrote:
Hi Matt, :-)
My best advice is that right now we just need to make the present New
Features and Fixes page look good with the info that it currently
contains. May be a good idea to just keep it simple for now...
We need something where *all* the features/fixes are covered on the
same page, without the visitor having to go to different pages.
We need something that is a little less bandwidth-intensive on first
load - think nicely-presented thumbnails linked to enlargments.
It would maybe be rational to go with the slideshow widget (see the
page types dropdown list) wrapped up in some pretty CSS. For the CSS,
Ivan did some styles that are incorporated into the current site CSS
that you could maybe use. See this thread for info .
The present page really sucks, but we have not yet been able to
convince any of the design guys to jump in and start re-formatting...
Oh, and the last thing would be that we need it this year and not next
century! :-D (let's forget the "iterative, community-based approach"
normally recommended by the Design team for the moment and let's just
"get the job done quickly").
Don't be shy to mail Michael directly, he's very interested in this page.
My 2 cents. HTH. ;-)
Unsubscribe instructions: E-mail to firstname.lastname@example.org
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