设计

This page is a translated version of the page Design and the translation is 29% complete.

TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate

Other languages:

我们在这些页面上提供关于我们的工作内容、工作方式以及您可以如何做出贡献的信息。我们为所有对加入感兴趣的人准备了任务。

我们为LibreOffice所做的工作包括：

用户体验设计（UX）是通过提升LibreOffice产品的易用性、可访问性和用户愉悦感，来增强用户满意度的过程。它不仅涵盖了传统的人机交互设计，还通过考虑品牌和设计等方面对其进行拓展。

可用性工程是一种基于结构化方法的设计过程，旨在提高界面设计的效率和美感。我们通过进行调查和快速投票来了解用户如何使用LibreOffice，并从中获取用户体验的见解。

在这些了解的基础上，我们从通用的人机交互准则开始着手。我们设计工作流程时设想了两个角色，分别为初学者Benjamin和高级用户Eve。正如我们在宣言中所强调的，我们的重点是

默认情况下以简洁为主，按需提供完整功能。
一致性比效率更重要。
可用性比图形设计更重要。

当然，我们也遵循所有用户体验原则。

We also take care about accessibility, branding to the visual design including icons, and support the QA, marketing and development teams.

What you can do

The simplest ways to contribute to LibreOffice are to submit bugs and enhancement requests to our bugtracker or to review and comment on the reports of others. If you think something in LibreOffice breaks a UX principle or guideline, it's a UX bug. Learn more in the blog post about Tickets on Behalf of UX, or in general from Fabiana Simoes's GUADEC presentation about How to not report your UX bug.

We have tasks for everyone from the very beginner to advanced developers. LibreOffice calls simple tasks easyhack, and together with the keyword “skilldesign” you may search the bugtracker.

A number of tasks are not listed in the bugtracker for some reason. For instance, create a new page at the wiki, draft a guideline, or create a mockup are better managed outside Bugzilla. For this purpose we use this wiki. Many tasks can be done by everyone, some require creativity, and other need more usability knowledge.

Bug reports and feature requests needing UX evaluation are marked with the keyword needsUXEval. Feel free to add your comments and even sketches to the reports. Another approach is to look at unconfirmed feature requests with a critical eye. One task of the UX team is to help decide on what features should not be added into the core application.

How we work

Usability is about users, so we basically observe, talk, interview, watch videos, and read comments to get an impression of what our users need.

We start new topics with the reference to the bug tracker, followed by the description of current state and how competitors solve the problem, in order to get a common understanding. The intended features are listed formally as functional requirements and non-functional constraints to the design. With this input we scribble mockups using Penpot, Pencil, or LibreOffice Draw and eventually, after a couple of iterations and discussions, the proposal is published on our design blog to get input from the community.

Open tasks

We always have open tasks for creative people with no doing expertise, as well as more advanced topics for experienced usability engineers. Non-coding tasks are for instance:

Create new templates
Design new artwork such as banners, icons, etc.