Hello,
On 23/11/2018 09:09, kainz.a wrote:
I would recommend to focus on some toppics and don't mix everything in one
Poster.
Yep, I agree! Drew, it's a great idea and thanks for working on it, but
I think we need to focus on one thing at a time with the messaging.
Otherwise people may get the idea that LibreOffice is too complicated,
can't decide on a cohesive interface etc.
The NotebookBar is going to be a big deal for LO 6.2, so we need to
focus on one or two variants of it and say:
* What it is (a new, OPTIONAL user interface design -- we're not
changing everything! Otherwise we'll get a huge amount of angry comments
on social media ;-) )
* Why it's great (work with items in context, faster workflow etc.)
* How to try it -- and super important, how to go back!
IMO we need to simultaneously communicate that LibreOffice 6.2 has the
same reliable, trusted, familiar user interface as previous releases,
but is also modern, forward-looking and adaptable. This isn't easy, but
if we do it right and not overload people with lots of information and
screenshots, I think we can make it work...
Mike
--
To unsubscribe e-mail to: marketing+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/marketing/
Privacy Policy: https://www.documentfoundation.org/privacy
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.