Main page: design.wikimedia.org
Statement of Purpose
At Wikimedia, we design with and for curious humans who rely on trustworthy content.
We as a design team work with a global community of humans who come from different experiences and places, with different goals. We are ever-evolving, learning, and growing. We remain open to change and feedback.
When making design decisions, we are guided by our principles. We use these guidelines to hold ourselves and each other accountable. We invite the broader community to engage with our design work on the basis of our Design Principles.
Design Principles
Design with Others
We collaborate with others through means of inclusion of ideas, research sessions, and working as openly as possible.
- Is this design the outcome of collaboration?
- Did we listen to and learn from people with different backgrounds and perspectives?
- Have we learned from the target audience that their needs are met?
For Curious Humans
We welcome and consider a universal audience, striving to remove barriers to accessing knowledge which satisfies human curiosity.
- Is this design accessible, inclusive, and equitable?
- Does this idea encourage or allow for adaptability based on the preference of the person using it?
- Is there opportunity for wonder in the experience?
Trustworthy
We design to enable the sharing and greater understanding of trustworthy knowledge, while maintaining the integrity of people's privacy.
- Are we minimizing the data we collect about people in both our design solution and the process to create it?
- Are we communicating information explicitly and honestly?
- Does this design help users confidently access and share well-sourced, reliable knowledge?
Content First
We aim for content to be at the center of Wikimedia projects, and to facilitate its comprehension and use.
- Is this design prioritizing the most contextually important information?
- Is the content presented in a way that supports clear understanding?
- Does this design help make it easy to learn from, improve, and spread content?
Read more about the background for this work.
About the team
The product design team has over 500 years of combined user experience design and research, engineering, information architecture, HCI, visual design, and usability experience.
Product Design
UX Research
The Product Design team works closely with UX Research. More info on their team page here.
Process
How to get involved and work with us
We welcome help in many ways, but we have limited time and have priorities based on the Foundation's roadmap to focus on. We want to make sure we foster an environment where community designers can contribute to the projects as well as developers.
A few ways to help out by volunteering your time:
Projects
Product teams
Many (but not all) of our cross-disciplinary product teams have a UX designer embedded into the team, where they focus on the User Experience (UX) for the team. Here's a list of the teams in which designers are currently working.
| Team
|
Description
|
Designer
|
Area of focus
|
| Reader Experience (formerly Web team)
|
Focuses on the reading experience on web.
|
Sneha Patel
|
Consumers
area managed by Carolyn Li-Madeo
|
| Reader Growth (formerly Web team)
|
Focuses initiatives to attract new readers to Wikipedia.
|
Justin Scherer
|
| Android
|
The Android team focuses on building inclusive mobile-first experiences, equitably filling knowledge gaps and increasing quality contributions to Wikipedia.
|
Sarah Chekfa
|
| iOS
|
The iOS team focuses on building mobile first inclusive, consistent, and permeable features to make editing, reading, and participating on Wikipedia intuitive for iOS app users.
|
Taís Lessa
|
| Future Audiences
|
The Future Audiences Team is in charge of exploring strategies to expand beyond our existing audiences of readers/users and contributors, in an effort to truly reach everyone in the world as the "essential infrastructure of the ecosystem of free knowledge."
|
Maryyann Crichton
|
| Editing
|
The Editing team work on products for editing—generally across MediaWiki, and the suite of editors including VisualEditor, as well as initiatives that facilitate more productive contributions (such as On-wiki collaboration and Edit Check).
|
Nicolas Ayoub and Bárbara Martínez
|
Contributors
area managed by Nicolas Ayoub, with Amin Al Hazwani
|
| Growth
|
The Growth team focuses on features to encourage activation and retention of new editors on Wikipedia and other Wikimedia projects.
|
Amin Al Hazwani
|
| Moderator Tools
|
The Moderator Tools team focuses on content moderation needs and processes, including page protection, deletion, reporting, and recent changes patrolling.
|
Olga Tichonova
|
| Connection
|
The Connection team is focused on building tools to help campaign and event organizers effectively engage participants as successful editors and retain them as contributors on Wikimedia projects.
|
Julieta Fernandez
|
| Language and Product Localization
|
The Language and Product Localization team focuses on reducing barriers to access and share knowledge. Main focus is to reduce knowledge gaps across languages with content and section translation. This team was created as the union of the former Inuka and Language teams.
|
Pau Giner and Sudhanshu Gautam
|
Languages, Content Growth, and Communities
area managed by Joydeep Sengupta, with Pau Giner
|
| Abstract Wikipedia
|
The Abstract Wikipedia team is focused on building Wikifunctions and Abstract Wikipedia, both efforts towards a multilingual Wikipedia where more people can share more knowledge in more languages.
|
Gregory Onyeahialam
|
| Community Tech
|
The Community Tech team is focused on equity and community impact, building and improving curation and moderation tools crowdsourced from experienced users through the Community Wishlist Survey.
|
Ruth O'Donoghue
|
| Product Safety and Integrity
|
The Product Safety and Integrity team focuses on features to increase digital and physical safety and security on the Wikimedia projects.
|
Katie Coleman (interim coverage by Kieran McCann), with support from Ruth O'Donoghue
|
| Codex Design System Steering Committee
|
The Codex Steering Committee is composed of a lead designer, an engineering manager, and a principal engineer with a constant degree of commitment dedicated to stewarding Codex, the Wikimedia design system. The committee reviews design system priorities and coordinate design and engineering resourcing. The Codex Steering Committee was formed as a successor to the Design System Team.
|
Derek Torsani
|
| MediaWiki & Data Platform
|
The MediaWiki Engineering Group specializes in working with MediaWiki and various parts of its core software, whilst the Data Platform Engineering team comprises data teams and systems from across the Product and Technology department with a goal to deliver end-to-end data capabilities for data producers and consumers.
|
Sarai Sanchez
|
Design resources
| This page is outdated. Codex style guide replaced Wikimedia Design Style Guide. If you have checked or updated this page and found the content to be suitable, please remove this notice. See the talk page for a possible discussion on this. |
Our resources for majority of our work are public and in open source projects. Have a look at the Wikimedia Design Style Guide (on Github) and its Resources section.
When designing with us bear in mind our Design best practices.
All our graphics assets are licensed under open licenses (but note that many of the logos are trademarked). All our user interface development is public in open source projects.
Reach out or stay up-to-date
Archived, obsolete resources
For historical context:
Design Fellow Alumni
.jpg)
