With the desire to improve the path for how people “get WordPress”, I proposed some Information Architecture ideas. Today, I’ve got a mockup to communicate these concepts.
First, I wanted to bring the different ways in which someone can ‘get WordPress’ into one single page that would communicate their relationship with one another effectively and clearly. Second, any buttons that say “Download WordPress” should actually download the software, and not link to another page.
These two points are addressed with the following mockup. The mockup combines downloading WordPress, downloading the mobile apps, and hosting into one page, with sub-pages for each. Combining these options provides a well-rounded view of how someone might go about “getting” WordPress – whether by downloading the software and setting it up themselves, having a hosting provider take care of it, or obtaining the mobile apps. Each section links to sub-pages that delve into more detail.
The mockup also slims down the navigation of this section of WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and unifies related content.
/get page mockup
View full size mockups
The mockup above has some explicit designs that are worth noting:
- Button styles are the same as the one in core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
- The title bar on this landing page has a new design, unlike others throughout WordPress.org (but somewhat similar to make.wordpress.org).
- Dashicons have been used on the page, when relevant.
- The typographic scale has been refined and Open Sans has been embraced.
This mockup is a view into the design direction for WordPress.org, so please chime in with your comments. I’d love to hear your thoughts.
(With great help from @hugobaeta.)