Szablony: Różnice pomiędzy wersjami

Przejdź do nawigacji Przejdź do wyszukiwania

Szablony (tekst źródłowy)

Wersja z 19:24, 2 lis 2021

Usunięte 5590 bajtów ,  19:24, 2 lis 2021
brak opisu edycji
Znacznik: Wycofane
Znacznik: Ręczne wycofanie zmian
Linia 79: Linia 79:
<br>
<br>
<br>
<br>
{| align="left" cellspacing="10px" cellpadding="0" width=100%
! style="width: 49%;" |
! style="width: 49%;" |
<!-- First row -->
|- valign="top"
| {{portal box|{{anchor|We|}}What we do for LibreOffice|2=
User experience design (UX) is the process of enhancing user satisfaction by improving the usability, accessibility, and pleasure with LibreOffice products. It encompasses traditional human-computer interaction design, and extends it by addressing all aspects including branding and design.
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 [[Design/Guidelines|human interaction guidelines]]. Workflows are designed with two [[Design/HIG_foundations#Persona|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
Of course we follow all [[Design/Principles|UX principles]] too.
We also take care about [[Accessibility|accessibility]], [[Marketing/Branding|branding]] to the [[Visual_Elements|visual design]] including icons, and support the [[QA/GetInvolved|QA]], [[Marketing|marketing]] and [[Development|development]] teams.
}}
| {{portal box|{{anchor|You|}}What you can do|2=
The simplest way to contribute to LibreOffice is to submit bugs and enhancement requests to our bugtracker.  If you think it breaks a [[Design/Principles|UX principle]] or [[Design/Guidelines|guideline]], it's a UX bug. Learn more in the blog post about [https://design.blog.documentfoundation.org/2016/08/31/tickets-on-behalf-of-ux/ Tickets on Behalf of UX], or in general from Fabiana Simoes's GUADEC presentation about [https://www.superlectures.com/guadec2013/how-to-not-report-your-ux-bug How to not report your UX bug].
We have tasks for everyone from the very beginner to advanced developers. LibreOffice calls simple tasks [[QA/Easy_Hacks|easyhack]], and together with the keyword “skilldesign” you may [https://bugs.documentfoundation.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&keywords=easyHack%2C%20skillDesign%2C%20&keywords_type=allwords&list_id=638779&product=LibreOffice&query_format=advanced 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.
}}
<!-- Second row -->
|- valign="top"
| {{portal box|{{anchor|How|}}How we work|2=
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 [http://user-prompt.com/de/how-to-use-balsamiq-mockups/ Balsamiq Mockups], or other tools like LibreOffice Draw or [http://pencil.evolus.vn/ Pencil], and eventually after a couple of iterations and discussions, the proposal is published on our design blog to get input from the community.
}}
| {{portal box|{{anchor|Tasks|}}Open tasks|2=
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.
More advanced topic would be:
* Scribble redesign mockups of dialogs
* Draft a guideline
All tasks are listed on our [[Design/Whiteboards|Whiteboard]] and [[Design/Blueprints|Blueprints]] pages. And finished proposals can be found at the [[Design/Whiteboards/Archive|Whiteboard archive]].
}}
<!-- Third row -->
|- valign="top"
| {{portal box|{{anchor|Who|}}Who we are|2=
We are people from all over the world with a wide variety of knowledge and different backgrounds.
Feel free to add yourself to the [[Design/Team|list of team members]].
}}
| {{portal box|{{anchor|Contact|}}Get in contact|2=
* Follow us on our [https://design.blog.documentfoundation.org design blog], [https://twitter.com/liboDesign Twitter] and [https://t.me/LibreOfficeDesign Telegram]
* Talk to the designers on IRC at the {{irc|libreoffice-design}} channel on Libera Chat (bridged to Telegram)
* Or join the Matrix room [https://matrix.to/#/!iQDsFBMFDNORAsQhSA:documentfoundation.org?via=documentfoundation.org&via=t2bot.io #libodesign:documentfoundation.org] (bridged to Telegram)
* Register to the [https://www.libreoffice.org/get-help/mailing-lists/#design design mailing list] and write emails to all people on this list
* Join the weekly [https://jitsi.documentfoundation.org/design Jitsi meeting] every (biweekly alternating) Wednesday/Thursday, 7pm/1pm UTC (20:00/14:00 CET+1). These calls are open to everyone. The agenda is tracked in the [http://pad.documentfoundation.org/p/design minutes], and shared on the [http://nabble.documentfoundation.org/Design-f1935996.html mailing list]. An [https://wiki.documentfoundation.org/Design/Meetings archive of meeting minutes] is kept.
}}
|}
Źródło: „http://katalog-moj.pl/index.php/Specjalna:Różnica_mobilna/5329”

Menu nawigacyjne