Design: Difference between revisions

Content deleted Content added

Inline

Latest revision as of 23:12, 3 July 2023

Wikimedia design guidelines[edit]

Design for everyone.[edit]

We aim to support a very diverse audience as a core part of our mission. It’s a priority to help users overcome the different barriers between them and the knowledge our projects provide. These barriers include accessibility, language, device capabilities, network, and peoples’ technical expertise — among others. When improving the experience for a given group of people, we need to make sure we are not increasing the barriers for others.

Example: When choosing colors, start by looking at accessibility guidelines. Then you can make aesthetic choices, with the confidence that everyone can participate.

Design for collaboration and evolution.[edit]

Our projects are collaborative. Discussion and sharing are key factors to consider. To support diversity and a global mission, our solutions need to provide room for extension and customization to particular needs and different perspectives.

Clear to use
Simple to share
Easy to modify
Ready for wide adoption
Example: When the Wikipedia 15 mark was defined, guidelines were created so that our communities could make their own.

Design for content first.[edit]

People come to Wikimedia projects for their content, and our solutions should facilitate its creation, consumption, and sharing—without getting in the way. Our content (facts, images, quotes, etc.) is our most representative element, and needs to be emphasized in our solutions.

Example: When designing t-shirts for Wikipedia 15th anniversary, instead of featuring Wikipedia logos prominently, the Wikipedia content itself (icons and interesting facts) was used to represent the project.

Be consistent.[edit]

In order to facilitate understanding it is important to rely on familiar concepts. Keeping consistency within our designs, and maintaining common patterns helps people relate quickly and easily.

Be trustworthy yet joyful.[edit]

Wikimedia projects provide reliable educational knowledge. At the same time, our projects are a source of entertainment and satisfy human curiosity. This requires us to find the right balance: we need to convey trust with our solutions but still remain entertaining and fresh.

Example: While search and discovery capabilities are provided to help people find information in a formal way, providing ways to explore random articles adds playfulness and organic learning.

Areas of work[edit]

Below are some places that could use design.

Easy

Favicons of various projects
info action is really ugly currently
- http://xkcd.com/1273/
- use some JavaScript to create a basic text narrative of the info action
- hide behind a URL parameter? a MediaWiki easter egg!

@@ Line 1: / Line 1: @@
+== Wikimedia design guidelines ==
-A place to talk about '''design'''.
+=== Design for everyone. ===
-== Thoughts ==
+We aim to support a very diverse audience as a core part of our mission. It’s a priority to help users overcome the different barriers between them and the knowledge our projects provide. These barriers include accessibility, language, device capabilities, network, and peoples’ technical expertise — among others. When improving the experience for a given group of people, we need to make sure we are not increasing the barriers for others.<blockquote>''Example: When choosing colors, start by looking at accessibility guidelines. Then you can make aesthetic choices, with the confidence that everyone can participate.''</blockquote>Read more
-Design on our projects and in our products is important. A rich, meaningful, and aesthetically pleasing user experience is something that every user who visits our sites or uses our services should have.
+* Accessibility: https://www.mediawiki.org/wiki/Accessibility
+* Devices:
-Design is trying to see the whole board&mdash;not an easy task. What does this mean? Design is evaluating and weighing the reader, casual editor, power editor, and developer perspectives while trying to ensure that Wikimedia's principles are being upheld and that we are appropriately considering the lessons of the past, current realities, and future ideals of how software should work and what the user experience should be.
+** https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
+** https://itunes.apple.com/us/app/wikipedia-mobile/id324715238?mt=8
+* Network:
+** https://wikimediafoundation.org/wiki/Mobile_partnerships
+=== Design for collaboration and evolution. ===
-== Prettify ==
+Our projects are collaborative. Discussion and sharing are key factors to consider. To support diversity and a global mission, our solutions need to provide room for extension and customization to particular needs and different perspectives.
-Below are some places that could use beautification.
+* Clear to use
+* Simple to share
+* Easy to modify
+* Ready for wide adoption <blockquote>''Example: When the Wikipedia 15 mark was defined, guidelines were created so that our communities could make their own.'' </blockquote>
+=== Design for content first. ===
+People come to Wikimedia projects for their content, and our solutions should facilitate its creation, consumption, and sharing—without getting in the way. Our content (facts, images, quotes, etc.) is our most representative element, and needs to be emphasized in our solutions.<blockquote>''Example: When designing t-shirts for Wikipedia 15th anniversary, instead of featuring Wikipedia logos prominently, the Wikipedia content itself (icons and interesting facts) was used to represent the project.''</blockquote>
+=== Be consistent. ===
+In order to facilitate understanding it is important to rely on familiar concepts. Keeping consistency within our designs, and maintaining common patterns helps people relate quickly and easily.
+=== Be trustworthy yet joyful.  ===
+Wikimedia projects provide reliable educational knowledge. At the same time, our projects are a source of entertainment and satisfy human curiosity. This requires us to find the right balance: we need to convey trust with our solutions but still remain entertaining and fresh.<blockquote>''Example: While search and discovery capabilities are provided to help people find information in a formal way, providing ways to explore random articles adds playfulness and organic learning.'' </blockquote>Read more
+* Reinventing the encyclopedia game: http://www.ted.com/talks/rives_reinventing_the_encyclopedia_game
+== Areas of work ==
+Below are some places that could use design.
 ; Easy
 * [[Favicons]] of various projects
 * [{{fullurl:{{FULLPAGENAME}}|action=info}} info action] is really ugly currently
+** http://xkcd.com/1273/
+** use some JavaScript to create a basic text narrative of the info action
+** hide behind a URL parameter? a MediaWiki easter egg!
+== Links ==
-; Fraught
-These places are potentially [[wikt:fraught#English|fraught]]. But if you're willing to make the long journey, it may be worth it. :-)
-* Standardize Wiktionary logo
-* Redesign [[wmf:Home]]
-* [[www]] portals
 == See also ==
-* [[Wish list]]
+* [[Brand]]
+; At MediaWiki:
+* [[mw:Design]], Wikimedia Foundation Design team's page.
+[[Category:Wikimedia projects]]
+[[Category:MediaWiki design]]