Looking Beyond WordPress v3.1

model with left eye magnified The latest production release of WordPress earlier this week includes the list of enhancements mentioned in our previous post about WordPress v3.1 BETA testers. A special thanks goes out to those WordPress users who take the time to test preproduction versions and debug software issues!

View the quote below for evidence the development team is already looking beyond WordPress v3.1 to v3.2.

Often new WordPress releases involve some type of security patch or update, yet the majority of the WordPress v3.1 revisions are functional improvements to the core files.

Consider the following quote from the WordPress v3.1 release announcement:

Now is the time to drop by our development channels if you are interested in being involved with 3.2, as the agenda will be under discussion shortly. We’re hoping to get the 3.2 release out in a shorter development cycle (3.1 took too long) and include some fun improvements around plugins and the speed of the admin.

Of all the improvements since the introduction of the first v3.x release I believe the custom sidebar function for pages was a giant leap forward for using WordPress as a true cms content management system without the “bloggy” look.

For now, this WordPress blog and cms testing site uses the default sidebars. A demo and tutorial for creating custom sidebars is coming soon for readers interested in do-it-yourself web design.

Follow the above link to the v3.1 announcement and then scroll down to view a list of nearly 200 developers and testers around the world that help keep WordPress evolving as a top custom cms web design solution.

This entry was posted in blog, cms, news, wordpress and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>