Author Archive
Menus, the Merge, and a Patch Sprint!
Posted by: | CommentsA Report from the 3.0 Development Cycle
Menus
There’s been a flurry of blog posts about the integration of the WooThemes Custom Navigation into WordPress core, so I thought it was time we posted the official word. For 3.0, the main user-facing feature we wanted to include was a better site menu management system. Currently, dealing with menus is clunky, using Page IDs or in some cases categories, if a theme uses categories instead of pages for the menu. We wanted a menu system that had the drag and drop ease of the widget management screen, could combine Pages, Categories, and Links, was able to be re-ordered, allowed submenus, and enabled hiding specific Pages or Categories from the menu altogether. We were in the process of building this when WooThemes introduced their Custom Navigation system. Watching their introductory video, it seemed that their system did pretty much everything we wanted to do for core, so we reached out to them about contributing to core.
As you’ve probably heard, it worked out, and the first patch has been submitted. It does require some code modification, which is happening now. The decision to incorporate the Woo menus happened right before our planned feature freeze for the 3.0 development cycle, so we pushed our freeze date back by two weeks to allow the addition. We’re now targeting the 3.0 release for early May, and we think it will be worth the extra two-week wait.
I’m personally really happy that it worked out this way, because I think it will show commercial theme and plugin authors that contributing to core is a win-win proposition. More people can contribute to and improve the basic functional code now, while WooThemes can continue to innovate on top of it for their customers. They get massive bragging rights (which I have no doubt will lead to even more customers), core gets a nice menu system without having to reinvent the wheel, and WordPress users all over the world will benefit. I’m hoping other plugin and theme developers will take a cue from Woo and look at core as a place for collaboration, rather than competition.
The Merge
It was announced at WordCamp San Francisco last year that WordPress and WordPress MU would be merging codebases. This has now happened in 3.0-alpha, and we’re working on smashing bugs and tidying up a few screens. If you’re currently using a single install of WordPress, when you upgrade to 3.0 you won’t see any of the extra screens associated with running a network of sites. If you’re currently running MU, when you upgrade you’ll notice a few labels changing, but upgrading should be as painless as usual. If you’re going to set up a new WordPress installation, you’ll be asked as part of the setup if you want one site or multiple sites, so that’s pretty simple. If you want to turn your single install into one that supports multiple sites, we’ll have a tool for you to use to do that, too. So if you’ve been worried about the merge, have a cup of chamomile tea and relax; it will all be fine. 
Patch Sprint!
Okay, so where are we now? The new feature freeze date is on Monday, March 1, 2010. That means that after that date, no more enhancements or features will be added, and we’ll switch gears to focus solely on crushing bugs and fixing up the features that have already made it in. That means we only have a week to try and finish up the many Trac tickets on the 3.0 milestone that either need a patch or have a patch that needs testing. You can help! From now until noon eastern time on March 1 (that’s 17:00 UTC on March 1), head on over to Trac and pitch in. If you hit a wall, hop into the core development channel at #wordpress-dev on irc.freenode.net and hopefully one of the friendly core contributors can give you a push.
WordPress On The Go
Posted by: | CommentsI like to moderate comments when I’m waiting for something: a checkout clerk to help me, the dentist to call me back to the office, a soy chai to be made. I don’t lug my laptop everywhere I go,* so I love it that we have mobile apps that make this possible. I don’t know of any other blogging platform that has mobile apps for iPhone, Android and Blackberry. Do you?
The iPhone app is up to version 2.2 (note that iPhone app version numbers do not correlate to WordPress core versions, due to separate dev cycles), while the Android and Blackberry apps are brand new. You can write posts (save drafts or publish right away), moderate comments, blog photos from your phone (and video on Blackberry!**), and more. Check out the glory that is mobile WordPress in the image below:
“But what about my Nokia,” you ask? Raanan Bar-Cohen, who oversees the mobile projects, recently announced:
“We are very excited to share with all of you that in the coming weeks we’ll be opening up a beta test for the official Open Source WordPress for Nokia app. For developers who are interested in getting involved, we just opened up a dev blog with details, links to the source code and trac tickets, and an early alpha build. We’ll be leveraging the Qt framework which means will be able to support both the S60 and Maemo platforms.”
W00t!
Getting Involved
All of these mobile WordPress apps are free and open source. They are developed in the same manner as WordPress core, which means anyone can contribute! If you’ve got some mad mobile development skills and want to get involved, a) you’re awesome, and b) here are a bunch of useful links.
Development Blogs: Android | BlackBerry | iPhone
Development Tracs: Android | Blackberry | iPhone
Feedback Forums: Android | BlackBerry | iPhone
Language Support: WordPress users come from all over the world. The mobile apps here are available in multiple languages but need volunteers to enable even more people to use them. If you’re interested in helping localize these mobile apps, you can get involved by emailing the translation team. They’ll send you instructions on how to translate.
Getting the Apps
So go for it — download the app for your platform of choice and soon you, too, can be live posting about how slow the cashier is while you wait for him to ring you up!
* Okay, yes, I do bring my laptop everywhere, but I leave it in the bag on these occasions.
** Video support should be coming soon to the iPhone and Android apps.
2010 Open Source Design Plans
Posted by: | Comments2010 is the year we dive into open source design. We’ve dipped our toes in this pool before (icon contest, graphic design component for Trac tickets, header refresh contest, etc.), but this year we’re going to cannonball and make a big splash. Here’s what you need to know if you want to get involved.
A list for all seasons. Developers have the wp-hackers mailing list to discuss core and plugin code. Sometimes UI/UX stuff comes up and gets discussed there, but there is a whole universe of discussion around navigation labels, gradients, button styling, layouts, alignment, etc. that would be clutter on wp-hackers. Designers need a list to call their own, and now we have one. You can sign up for the wp-ui list to discuss ways to improve the interface or user experience of WordPress, and to discuss progress on design-related projects for the open source project, like the design challenges we’re going to have.
Design Challenges. We learned a lot from the icon design and header refresh contests, and we want to do these kind of open design challenges on a regular basis to give UI/UX designers who want to contribute to the WordPress open source project more opportunities to do so. If we could do one per month, that would be ideal, keeping the challenges relatively bite-sized to allow potential contributors an easy way to get involved at first. As each challenge is posted, people can use the list to bounce ideas off each other and work toward optimal solutions. I’m hoping the design challenges will evolve to be less contest and more collaboration. We’ll announce the first one before the end of January, so if you’re interested, please sign up for the list! (Hint: one will likely be a touch up to the Right Now dashboard module, to improve the information design, and there will be a couple of screen layout challenges coming up as well.)
Distributed Usability Testing. We started to try this out last year, and several dozen usability professionals volunteered to help get the program going, but a combination of scheduling and infrastructure issues combined to stall the progress. Having the “UI/UX contributor team” infrastructure in place, starting with the mailing list, will make it much easier to get this project going again.
Chit-chat. The weekly developer chats in IRC at #wordpress-dev have been very productive. We’ve created an IRC room at #wordpress-ui on irc.freenode.net so that we can have the same kind of “water cooler” for UI/UX contributors as for core code contributors. In addition to being a place where you can drop in and discuss core UI/UX (note: this room will not be a place to discuss the design of blog themes, it’s to discuss the design of the Wordpress application itself), we’ll set up a weekly chat. Choosing a day and time for the chats will probably be the first discussion on the mailing list.
A blog of our own. Once again, taking a page from the code contributor infrastructure, we’ll set up a blog for UI/UX updates, announcements, progress reports, etc. This will be on WordPress.org in the nearish future, and will be announced to the mailing list when it is live.
So, if you want to become a contributor to core WordPress by using your design skills, join the wp-ui mailing list and get ready for a fun year!