Jump to content

設計

From The Document Foundation Wiki
This page is a translated version of the page Design and the translation is 43% complete.


本頁介紹我們的工作和你可以如何作出貢獻。我們為所有人都準備了任務。

我們的工作

使用者經驗設計(UX)目的透過提升使用性、親和力和愉悅感,以讓使用者對LibreOffice更滿意。它不僅包含傳統人機交互設計,也包括品牌和設計的各方面。

Usability engineering is based on structured methods for achieving efficiency and elegance in interface design. We run surveys and quick polls to get insights on how users work with LibreOffice.

With this knowledge we start with generic human interaction guidelines. Workflows are designed with two personas in mind, Benjamin to target beginners and Eve for the advanced user. As stated in our manifesto we focus on

  • Simplicity by default with Full Functionality on demand
  • Consistency over Efficiency
  • Usability over Graphical Design

當然,我們也遵循所有使用者經驗設計原則

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

你可以做什麼

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 [1] 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.

工作方式

可用性設計的核心是使用者,因此我們主要透過觀察、訪問、觀看影片和閱讀評論等方式,來掌握使用者的需求。

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.

更多進階題目:

  • Scribble redesign mockups of dialogs
  • Draft a guideline

All tasks are listed on our Whiteboard and Blueprints pages. And finished proposals can be found at the Whiteboard archive.

了解我們

我們來自世界各地,擁有廣泛的知識和不同的背景。

Feel free to add yourself to the list of team members.

聯絡我們