Skip to content

Commit

Permalink
Merge pull request #121 from WordPress/add/sketch-file
Browse files Browse the repository at this point in the history
Add Sketch file and designer contribution tips
  • Loading branch information
jasmussen authored Feb 23, 2017
2 parents 3520364 + d4a8f16 commit bb92486
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,3 +59,17 @@ These mockups are all subject to change and feedback.
**Early Mobile Chrome Concept**

![Mobile](mockups/Mobile.png)

## How designers can contribute

The editor we're building means to make the editing experience better for every WordPress user, by creating an interface that "makes writing rich posts effortless, and has 'blocks' to make it easy what today might take shortcodes, custom HTML, or 'mystery meat' embed discovery", to quote the kickoff goal.

That is difficult. So your designer eyes and help is appreciated, in what capacity you'd like to contribute.

A good place to start is having a look at <a href="https://github.com/WordPress/gutenberg#mockups">the current mockups</a> and <a href="https://wordpress.github.io/gutenberg/">the UI prototype</a>. We also have a GitHub repository, where <a href="https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+label%3ADesign">anything labelled "Design"</a> could use thoughtful replies, mockups, animatics, sketches, doodles.

With regards to specific changes to the design, the details & execution (like colors, borders, shadows), those are best done as minimal and specific iterations on the work that preceeds it, so we can ideally compare. That doesn't preclude wild ideas, but should be considered for precise tasks like "give the pressed buttons more contrast", things in that vein.

Grab the Sketch file so you don't have to start from scratch:

**<a href="mockups/editor.sketch">Download, Updated Feb. 23rd.</a>**

0 comments on commit bb92486

Please sign in to comment.