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


Hi David,

Am 17.12.2010 09:30, schrieb David Nelson:

Does anyone else have and comments or suggestions to make? If so,
please post them in this thread. Thank you! :-)

First of all I think, through your work, we have made a large
progress and also by the enhancements of the styling
by the other parties. Thanks very much! :-)

You are asking for suggestions for improvement.

In general: IMO it´s too much text. I fear, a large majority of
visitors will be deterred by this. Visitors won´t be so patient and
interested, that they will sit down and read very long.

We have to achieve, that one can tell in seconds that LO
it as a great, free office suite, and that the visitor
wants to use it or at least try it.

At this point, certainly a short remark would be helpful, that LO is
an improvement of the very popular OOo. There should also be a brief
note that Libo manages pretty much all common file formats,
including Word, Excel and PowerPoint.

If the visitor then is tempted to push the "Download" button, we
must not give him the impression that this all is terrible
complicated and cumbersome for him. But that is what we do, by
presenting a full text page with notes and explanations, before the
reader reaches down to the download controls.

All this text is redundant IMO to 90% because the download function
with the controls for selection is almost self-explanatory. I would
rather outsource the whole text to a subpage.

If John Doe then looks at the installation instructions, he might
probably be deterred again. It looks terribly complex and difficult.
Primarily we should clarify, that installation usually is very, very
simple. (By the way, actually a lot easier and faster than MS
Office!) For special and specific cases we have of course
detailed support articles...

Next, I don´t like the categorization of the page "Mailing Lists"
under "Get Help". There is a description of 13 mailing lists. Only
one of them is meant for help and support. All others are for
project communication and they better belong to "Get Involved" or
"About Us".

The FAQ need still some work on the styling. The character size of
the questions is much too big.

I didn´t check the factual content of the FAQ. I only checked the
first question a sample:

Question: "Why is the Windows installer so big?"

Answer: "When you download LibreOffice for Windows, you get the
choice between two downloads: one is about 343 Megabytes in size and
the other is about 498 Megabytes. The smaller download includes a
selection of the most-commonly chosen languages, while the larger
download includes every language currently supported by LibreOffice.
However, both installers give you exactly the same features in terms
of the functionality you get in the installed software."

Well, this does not answer the question, does it? On the contrary,
it raises a new question, which nobody seems to able to answer:
Which one of the two big installers will contain my specific language?

And again, 50% of the topics of the FAQ are no support questions,
but questions of general interest. They should not be categorized
under "Get Help".

Stefan
(having a hard time writing this in English)


-- 
LibreOffice - Die Freiheit nehm' ich mir!

-- 
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/website/
*** 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.