--- title: WordPress 2.7 Administration UI Wireframes date: 2008-10-01T23:24:05+00:00 modified: 2008-10-01T23:24:05+00:00 image:: https://kaspars.net/wp-content/uploads/2008/10/wordpress-27-ui-002.png permalink: https://kaspars.net/blog/wordpress-27-administration-ui-wireframes post_type: post author: name: Kaspars avatar: https://reverse.kaspars.net/gravatar/avatar/92bfcd3a8c3a21a033a6484d32c25a40b113ec6891f674336081513d5c98ef76?s=96&d=mm&r=g category: - Development - WordPress --- # WordPress 2.7 Administration UI Wireframes Automattic have [published](http://wordpress.org/development/2008/10/wordpress-27-wireframes/) [WordPress 2.7 user interface wireframes (.pdf)](http://wpdotorg.files.wordpress.com/2008/10/wf-dashboard_v002_093008jw.pdf) that list and explain the changes planned for the next major release of WordPress. [![WordPress 2.7 User Interface proposal (version 002)](/wp-content/uploads/2008/10/wordpress-27-ui-002-480x360.png "WordPress 2.7 User Interface proposal (version 002)")](https://kaspars.net/wp-content/uploads/2008/10/wordpress-27-ui-002.png)WordPress 2.7 User Interface proposal (version 002) I think there are only two things wrong with the purposed user interface and the information architecture: ### Main navigation menu WordPress has always been regarded as a simple and easy platform (software) for publishing blogs and by *blogs* I mean articles with photos, pictures and videos posted in chronological order. Why would one need **eleven** top level navigation items to do just that. I am referring particularly to Settings, Tools and Plugins menus items. What if a *plugin* creates a *tool* that needs to be *configured*? On *wp-testers* mailing list Stephen Rider mentions [another set of reasons why it may not work](http://comox.textdrive.com/pipermail/wp-testers/2008-October/008927.html). ### Breadcrumb Navigation Why is there a need for breadcrumb navigation if the main menu is only two levels deep. More importantly, by clicking on the top level navigation item (in the left side menu) one is only able to expand and collapse child items of that menu and not go to a particular subsection. So the question is — where will the previous level breadcrumb navigation item lead to? Will it be *Add New* or *Edit* for *Posts*, for example? > The blog name will be followed by breadcrumb navigation that shows the current screen and its parent section as well as a link to the Dashboard — *2.7 Wireframes v0.02, page 4* If it is placed there only for saving more of the vertical space by moving section titles somewhere else, then be it — lets use that space for section titles and not as another (action) area with links. ### Javascript-only Favorites Menu This is a new features which somehow correlates with [my](http://comox.textdrive.com/pipermail/wp-hackers/2008-September/021743.html) [suggestion](https://kaspars.net/examples/wordpress-dashboard/04/) [to have](https://kaspars.net/examples/wordpress-dashboard/01/) the *My Tasks* ribbon at the top of the dashboard where users can place links to administration sections that they use the most. The idea for this *task bar* came from the fact that all WordPress user have their own set and sequence of tasks which they do after logging in, and it is almost impossible to predict them. Here is the description of the *Favorites Menu* from the wireframes: > To the right is a favorites menu that expands on hover (JavaScript-enabled browsers only). Currently the menu is populated with screens most frequently accessed by users: Add new post, Comments, Stats (.com only), Plugins (.org only). Ultimately, items in this menu will be user-defined. The question is — why make it Javascript only? I think this is simply an unintended mistake and someone will turn it into an accessible CSS driven drop-down menu. However, there is another option — place the favorites items under *Dashboard* in the main menu. ### Bonus point Why do they use Flock on a Mac? ### Serious Conclusion I am fully aware that this is only a mock-up and not the final description of how the WordPress will look and function in future. Therefore this article is intended as a suggestion and not as an attack on those who are working hard to make WordPress great and fun for both experienced and first time publishers (and not only bloggers). I also understand that a single opinion can not measure up to the precise results of the user testing that was conducted to better understand how different parts of the administration section need to be organized and labeled. To do the right thing it is important to consider everyones opinion and let them know that they have been heard and their ideas considered. Only by having an open mind and through clear discussion one can come to the right conclusions. I am almost certain that [guys and gals at Automattic](http://automattic.com/about/) have their ears [wide](http://lists.automattic.com/mailman/listinfo/wp-testers "Join the discussion at WordPress testers mailing list") [open](http://wordpress.org/support/forum/12 "WordPress support forum for alpha/beta versions").