What is the problem?
Documentation on Wikimedia projects usually looks a bit dull and boring, and is sometimes difficult to distinguish from other content and policy pages.
In the upcoming quarters, I will write new documentation about StructuredDataOnCommons, specifically for audiences of staff members from cultural institutions and GLAM-Wiki volunteers. These are audiences that are used to well-designed websites, and they usually have a high visual and design sensitivity. So for these audiences I think it would be very good to create documentation that is designed well and pleasantly.
The documentation will cover complex processes, and it will benefit a lot from design elements that help to make it more understandable and digestible.
And in general, I would like GLAM documentation to have its own very specific and recognizable 'style' - fitting within general Wikimedia style guidelines, but definitely with a character of its own, so that users have a sense of recognition, identity and unity when they encounter and use it.
How can we help you?
In April-May 2019, I would like to request help from CommRel's Associate designer to come up with
- a set of recognizable, fun and pleasant illustrations to highlight documentation about GLAM work; preferably designed according to some basic principles upon which volunteers can build their own new illustrations as well
- and an easy-to-apply, pleasant-looking set of page design templates and design building blocks (color scheme, title formatting, other layout elements…) for structuring that documentation.
For reference, the first set of illustrations should include the steps outlined in this workflow:
What does success look like?
This specific assignment will be successful when, by June 2019, we have a package of illustrations on Wikimedia Commons, and a set of page templates on meta.wikimedia.org, that can easily be used as building blocks for GLAM and Wikimedia Commons documentation.
What is your deadline?
Ideally 31 May 2019, so that the designs can be put to use immediately when I start working on documentation in June.
There's a more extensive design brief in this Google document: https://docs.google.com/document/d/11USW5HXNWI6bUl0M4Q27LM5Z42EOdjUTPODrto-AOz0/edit#