O:9:"MagpieRSS":19:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:10:{i:0;a:12:{s:5:"title";s:20:"WordPress 2.7 Beta 2";s:4:"link";s:61:"http://wordpress.org/development/2008/11/wordpress-27-beta-2/";s:8:"comments";s:70:"http://wordpress.org/development/2008/11/wordpress-27-beta-2/#comments";s:7:"pubdate";s:31:"Thu, 06 Nov 2008 09:03:57 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:39:"http://wordpress.org/development/?p=415";s:11:"description";s:395:"WordPress 2.7 Beta 2 is ready.  Here is a quick rundown of changes since beta 1.

The Upload button didn&#8217;t always show. Fixed.
JS on the Dashboard broke for blogs with no comments, causing several UI elements to &#8220;freeze&#8221;. Fixed.
Recent Drafts Dashboard module didn&#8217;t show correct times. Fixed.
Various Autosave fixes.
Redirect after deleting a page from the editor [...]";s:7:"content";a:1:{s:7:"encoded";s:1726:"<p><a href="http://wordpress.org/wordpress-2.7-beta2.zip">WordPress 2.7 Beta 2 is ready</a>.  Here is a quick rundown of changes since beta 1.</p>
<ul>
<li>The Upload button didn&#8217;t always show. Fixed.</li>
<li>JS on the Dashboard broke for blogs with no comments, causing several UI elements to &#8220;freeze&#8221;. Fixed.</li>
<li>Recent Drafts Dashboard module didn&#8217;t show correct times. Fixed.</li>
<li>Various Autosave fixes.</li>
<li>Redirect after deleting a page from the editor went back to the deleted page. Fixed.</li>
<li>Fixed loading of translations for default TinyMCE plugins.</li>
<li>Added avatars to the edit users list.</li>
<li>Added some missing translations.</li>
<li>Fixed some validation errors.</li>
<li>Fixed some PHP warnings and notices.</li>
<li>Handle inconsistent file permissions during auto upgrade</li>
<li>Change Publish box layout to better accommodate internationalized text</li>
<li>Fix quick editing of the last page in the Edit Pages list</li>
<li>Fix Screen Options for IE</li>
<li>Fixes for choose tag from tag cloud</li>
<li>Rewrite rules fixes for certain hosts</li>
<li>Don&#8217;t check for updates on every page load</li>
<li>Easier post box dropping</li>
<li>Preview fixes</li>
<li>RTL fixes</li>
<li>Fixed broken wp-mail</li>
<li>Plugin update and install fixes</li>
<li>First draft of contextual help tab</li>
</ul>
<p>If you have already installed beta 1, you can update to beta 2 via the Tools -&gt; Update menu.  Beta 1 does have a bug in the automatic upgrade that breaks certain setups, so be prepared to download and install Beta 2 manually if you experience problems.</p>
<p><a href="http://wordpress.org/wordpress-2.7-beta2.zip">Get 2.7 Beta 2</a>.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:66:"http://wordpress.org/development/2008/11/wordpress-27-beta-2/feed/";}s:7:"summary";s:395:"WordPress 2.7 Beta 2 is ready.  Here is a quick rundown of changes since beta 1.

The Upload button didn&#8217;t always show. Fixed.
JS on the Dashboard broke for blogs with no comments, causing several UI elements to &#8220;freeze&#8221;. Fixed.
Recent Drafts Dashboard module didn&#8217;t show correct times. Fixed.
Various Autosave fixes.
Redirect after deleting a page from the editor [...]";s:12:"atom_content";s:1726:"<p><a href="http://wordpress.org/wordpress-2.7-beta2.zip">WordPress 2.7 Beta 2 is ready</a>.  Here is a quick rundown of changes since beta 1.</p>
<ul>
<li>The Upload button didn&#8217;t always show. Fixed.</li>
<li>JS on the Dashboard broke for blogs with no comments, causing several UI elements to &#8220;freeze&#8221;. Fixed.</li>
<li>Recent Drafts Dashboard module didn&#8217;t show correct times. Fixed.</li>
<li>Various Autosave fixes.</li>
<li>Redirect after deleting a page from the editor went back to the deleted page. Fixed.</li>
<li>Fixed loading of translations for default TinyMCE plugins.</li>
<li>Added avatars to the edit users list.</li>
<li>Added some missing translations.</li>
<li>Fixed some validation errors.</li>
<li>Fixed some PHP warnings and notices.</li>
<li>Handle inconsistent file permissions during auto upgrade</li>
<li>Change Publish box layout to better accommodate internationalized text</li>
<li>Fix quick editing of the last page in the Edit Pages list</li>
<li>Fix Screen Options for IE</li>
<li>Fixes for choose tag from tag cloud</li>
<li>Rewrite rules fixes for certain hosts</li>
<li>Don&#8217;t check for updates on every page load</li>
<li>Easier post box dropping</li>
<li>Preview fixes</li>
<li>RTL fixes</li>
<li>Fixed broken wp-mail</li>
<li>Plugin update and install fixes</li>
<li>First draft of contextual help tab</li>
</ul>
<p>If you have already installed beta 1, you can update to beta 2 via the Tools -&gt; Update menu.  Beta 1 does have a bug in the automatic upgrade that breaks certain setups, so be prepared to download and install Beta 2 manually if you experience problems.</p>
<p><a href="http://wordpress.org/wordpress-2.7-beta2.zip">Get 2.7 Beta 2</a>.</p>
";}i:1;a:12:{s:5:"title";s:48:"What’s your favorite thing about the 2.7 Beta?";s:4:"link";s:85:"http://wordpress.org/development/2008/11/whats-your-favorite-thing-about-the-27-beta/";s:8:"comments";s:94:"http://wordpress.org/development/2008/11/whats-your-favorite-thing-about-the-27-beta/#comments";s:7:"pubdate";s:31:"Sun, 02 Nov 2008 20:09:19 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:8:"Features";s:4:"guid";s:39:"http://wordpress.org/development/?p=396";s:11:"description";s:317:"There have been a lot of posts and twitter announcements by people checking out the WordPress 2.7 Beta since it was announced yesterday. What&#8217;s your favorite thing about 2.7 so far? Or if you haven&#8217;t made the leap yet, to which feature are you most looking forward? Tell us in the poll below. 
 What [...]";s:7:"content";a:1:{s:7:"encoded";s:1051:"<p>There have been a lot of posts and <a href="http://search.twitter.com/search?q=wordpress+2.7">twitter announcements</a> by people checking out the WordPress 2.7 Beta since it was announced yesterday. What&#8217;s your favorite thing about 2.7 so far? Or if you haven&#8217;t made the leap yet, to which feature are you most looking forward? Tell us in the poll below. </p>
<p><script type="text/javascript" language="javascript" src="http://s3.polldaddy.com/p/1068887.js"></script><noscript> <a href ="http://answers.polldaddy.com/poll/1068887/" >What is your favorite feature in WordPress 2.7?</a>  <br /> <span style="font-size:9px;"> (<a href ="http://www.polldaddy.com">  polls</a>)</span></noscript></p>
<p>If you have a extra minute or two, we&#8217;ve also put together a survey that lists all the new features and allows you to rate them, as well as give additional feedback if you&#8217;re so inclined. If you want to participate, <a href="http://www.polldaddy.com/s/96BC7ED0D63500E4/">take the 2.7 Beta Favorite Features survey</a>. </p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:90:"http://wordpress.org/development/2008/11/whats-your-favorite-thing-about-the-27-beta/feed/";}s:7:"summary";s:317:"There have been a lot of posts and twitter announcements by people checking out the WordPress 2.7 Beta since it was announced yesterday. What&#8217;s your favorite thing about 2.7 so far? Or if you haven&#8217;t made the leap yet, to which feature are you most looking forward? Tell us in the poll below. 
 What [...]";s:12:"atom_content";s:1051:"<p>There have been a lot of posts and <a href="http://search.twitter.com/search?q=wordpress+2.7">twitter announcements</a> by people checking out the WordPress 2.7 Beta since it was announced yesterday. What&#8217;s your favorite thing about 2.7 so far? Or if you haven&#8217;t made the leap yet, to which feature are you most looking forward? Tell us in the poll below. </p>
<p><script type="text/javascript" language="javascript" src="http://s3.polldaddy.com/p/1068887.js"></script><noscript> <a href ="http://answers.polldaddy.com/poll/1068887/" >What is your favorite feature in WordPress 2.7?</a>  <br /> <span style="font-size:9px;"> (<a href ="http://www.polldaddy.com">  polls</a>)</span></noscript></p>
<p>If you have a extra minute or two, we&#8217;ve also put together a survey that lists all the new features and allows you to rate them, as well as give additional feedback if you&#8217;re so inclined. If you want to participate, <a href="http://www.polldaddy.com/s/96BC7ED0D63500E4/">take the 2.7 Beta Favorite Features survey</a>. </p>
";}i:2;a:12:{s:5:"title";s:20:"WordPress 2.7 Beta 1";s:4:"link";s:61:"http://wordpress.org/development/2008/11/wordpress-27-beta-1/";s:8:"comments";s:70:"http://wordpress.org/development/2008/11/wordpress-27-beta-1/#comments";s:7:"pubdate";s:31:"Sat, 01 Nov 2008 08:00:11 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:39:"http://wordpress.org/development/?p=387";s:11:"description";s:332:"The first public beta of WordPress 2.7 is here at last.  Join the thousands of people already testing 2.7 by downloading 2.7 Beta 1.  As previously mentioned on this blog, 2.7 is bringing a new visual design.  This design is almost completely implemented, but there are still a few areas that aren&#8217;t quite finished in [...]";s:7:"content";a:1:{s:7:"encoded";s:1662:"<p>The first public beta of WordPress 2.7 is here at last.  Join the thousands of people already testing 2.7 by <a href="http://wordpress.org/wordpress-2.7-beta1.zip">downloading 2.7 Beta 1</a>.  As previously mentioned on this blog, 2.7 is bringing a new visual design.  This design is almost completely implemented, but there are still a few areas that aren&#8217;t quite finished in Beta 1.  There are also several glitches in certain browsers.  Beta 1 provides the best experience in Firefox and Safari. Don&#8217;t worry, we are working on IE and Opera and will have those looking good in time for the final release.</p>
<p>Speaking of the final release, it will not be available on November 10th as originally scheduled.  We are two weeks behind schedule at the moment.  We need a little more time to finish the visual design, do a round of user testing against that finished design, and do a proper round of public beta testing. Our plan is to keep working as if Nov. 10 is still the release date.  However, instead of releasing the final 2.7 on the 10th, we will make a release candidate available instead.  The release candidate is intended to be a high-quality, almost-finished release that we are comfortable recommending for broad use.  After Nov. 10, the focus will be on fixing high impact bugs turned up by those of you testing the release candidate. I suspect 2.7 will be ready for final release by the end of November.  A specific date will be set as we progress through the public beta cycle and get a feel for how solid the release is.</p>
<p><a href="http://wordpress.org/wordpress-2.7-beta1.zip">Get WordPress 2.7 Beta 1</a>.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:66:"http://wordpress.org/development/2008/11/wordpress-27-beta-1/feed/";}s:7:"summary";s:332:"The first public beta of WordPress 2.7 is here at last.  Join the thousands of people already testing 2.7 by downloading 2.7 Beta 1.  As previously mentioned on this blog, 2.7 is bringing a new visual design.  This design is almost completely implemented, but there are still a few areas that aren&#8217;t quite finished in [...]";s:12:"atom_content";s:1662:"<p>The first public beta of WordPress 2.7 is here at last.  Join the thousands of people already testing 2.7 by <a href="http://wordpress.org/wordpress-2.7-beta1.zip">downloading 2.7 Beta 1</a>.  As previously mentioned on this blog, 2.7 is bringing a new visual design.  This design is almost completely implemented, but there are still a few areas that aren&#8217;t quite finished in Beta 1.  There are also several glitches in certain browsers.  Beta 1 provides the best experience in Firefox and Safari. Don&#8217;t worry, we are working on IE and Opera and will have those looking good in time for the final release.</p>
<p>Speaking of the final release, it will not be available on November 10th as originally scheduled.  We are two weeks behind schedule at the moment.  We need a little more time to finish the visual design, do a round of user testing against that finished design, and do a proper round of public beta testing. Our plan is to keep working as if Nov. 10 is still the release date.  However, instead of releasing the final 2.7 on the 10th, we will make a release candidate available instead.  The release candidate is intended to be a high-quality, almost-finished release that we are comfortable recommending for broad use.  After Nov. 10, the focus will be on fixing high impact bugs turned up by those of you testing the release candidate. I suspect 2.7 will be ready for final release by the end of November.  A specific date will be set as we progress through the public beta cycle and get a feel for how solid the release is.</p>
<p><a href="http://wordpress.org/wordpress-2.7-beta1.zip">Get WordPress 2.7 Beta 1</a>.</p>
";}i:3;a:12:{s:5:"title";s:8:"Showcase";s:4:"link";s:50:"http://wordpress.org/development/2008/11/showcase/";s:8:"comments";s:59:"http://wordpress.org/development/2008/11/showcase/#comments";s:7:"pubdate";s:31:"Sat, 01 Nov 2008 00:36:27 +0000";s:2:"dc";a:1:{s:7:"creator";s:11:"Nick Momrik";}s:8:"category";s:4:"Meta";s:4:"guid";s:39:"http://wordpress.org/development/?p=380";s:11:"description";s:355:"Today we launched the WordPress Showcase, a display of some of the best and brightest WordPress users, who are using it to do a whole lot more than blog.

Pick your flavor and check out the possibilities available through WordPress MU, WordPress.com, WordPress.com VIP and WordPress.org.
Site screenshots are constantly updated, so what you see is a [...]";s:7:"content";a:1:{s:7:"encoded";s:960:"<p>Today we launched the <a title="WordPress Showcase" href="http://wordpress.org/showcase/">WordPress Showcase</a>, a display of some of the best and brightest WordPress users, who are using it to do a whole lot more than blog.</p>
<p><a href="http://wordpress.org/showcase/"><img title="Showcase Screenshot" src="http://wpdotorg.files.wordpress.com/2008/10/showcase-screenshot.png" alt="Duke Center for International Studies" width="567" height="605" /></a></p>
<p>Pick your flavor and check out the possibilities available through WordPress MU, WordPress.com, WordPress.com VIP and WordPress.org.</p>
<p>Site screenshots are constantly updated, so what you see is a realtime look at what&#8217;s going on with our hottest users.</p>
<p>Don&#8217;t see something there that should be? <a href="http://wordpress.org/showcase/submit-a-wordpress-site/">Suggest an addition!</a> We&#8217;ll check it out and add it to the bunch if we think it makes the cut.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:55:"http://wordpress.org/development/2008/11/showcase/feed/";}s:7:"summary";s:355:"Today we launched the WordPress Showcase, a display of some of the best and brightest WordPress users, who are using it to do a whole lot more than blog.

Pick your flavor and check out the possibilities available through WordPress MU, WordPress.com, WordPress.com VIP and WordPress.org.
Site screenshots are constantly updated, so what you see is a [...]";s:12:"atom_content";s:960:"<p>Today we launched the <a title="WordPress Showcase" href="http://wordpress.org/showcase/">WordPress Showcase</a>, a display of some of the best and brightest WordPress users, who are using it to do a whole lot more than blog.</p>
<p><a href="http://wordpress.org/showcase/"><img title="Showcase Screenshot" src="http://wpdotorg.files.wordpress.com/2008/10/showcase-screenshot.png" alt="Duke Center for International Studies" width="567" height="605" /></a></p>
<p>Pick your flavor and check out the possibilities available through WordPress MU, WordPress.com, WordPress.com VIP and WordPress.org.</p>
<p>Site screenshots are constantly updated, so what you see is a realtime look at what&#8217;s going on with our hottest users.</p>
<p>Don&#8217;t see something there that should be? <a href="http://wordpress.org/showcase/submit-a-wordpress-site/">Suggest an addition!</a> We&#8217;ll check it out and add it to the bunch if we think it makes the cut.</p>
";}i:4;a:12:{s:5:"title";s:44:"Usability Testing Report: 2.5 and Crazyhorse";s:4:"link";s:84:"http://wordpress.org/development/2008/10/usability-testing-report-25-and-crazyhorse/";s:8:"comments";s:93:"http://wordpress.org/development/2008/10/usability-testing-report-25-and-crazyhorse/#comments";s:7:"pubdate";s:31:"Wed, 29 Oct 2008 00:06:33 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:43:"User Interface2.5crazyhorsetestingusability";s:4:"guid";s:39:"http://wordpress.org/development/?p=375";s:11:"description";s:327:"A question I hear pretty frequently is, &#8220;Why a redesign of the admin panel so soon after 2.5?&#8221; Those who have attended WordCamps in the past few months have already heard the answer, but for the people who haven&#8217;t had that opportunity, this post is for you. 
When the community response to the 2.5 admin [...]";s:7:"content";a:1:{s:7:"encoded";s:4403:"<p>A question I hear pretty frequently is, &#8220;Why a redesign of the admin panel so soon after 2.5?&#8221; Those who have attended WordCamps in the past few months have already heard the answer, but for the people who haven&#8217;t had that opportunity, this post is for you. </p>
<p>When the community response to the 2.5 admin redesign was mixed, it seemed like a good idea to do usability testing to find out which issues were based on actual interface problems vs. which complaints were just a result of not liking change. To prevent bias, a third party was contracted to conduct usability testing, <a href="http://cms.bsu.edu/Academics/CentersandInstitutes/CMD/InsightandResearch.aspx">Ball State University&#8217;s Center for Media Design, Insight and Research</a> division. Try saying that three times fast with a mouth full of peanut butter. Or fitting it on a business card. To save time, we&#8217;ll just call that third party CMD, since that&#8217;s what they call themselves.</p>
<p>The plan that was developed involved multiple rounds of testing, as well as the creation of two prototypes, hardcore! The first phase involved a usability review of 2.5 by CMD, the results of which were discussed with lead developers. A quick prototype was created that addressed some of the lightweight issues, so that the test participants could use both 2.5 on their own blogs and the prototype on a test site. Results would be analyzed and compared, leading to a second round of suggestions. A second prototype would be developed over a week or two, which would then be tested with the same participants, and a final report delivered. But you know what they say&#8230; the best laid plans of designers and developers often go awry. </p>
<p>After the first round of testing, it was clear that a prototype delivering the kind of fixes that could be coded in a week or two wouldn&#8217;t make much of a difference overall. We all decided a more ambitious prototype was in order, one that would experiment with a new approach to screen real estate and attempt to address as many of the issues from 2.5 as was possible with a few extra weeks of time. A rapid design process was followed by an even more rapid development cycle. The second prototype is what you know as Crazyhorse. </p>
<p>The second round of testing blew everyone away. The research team had never seen such consistent results. Tasks were completed faster, participant opinions rated it higher, understanding of how interface elements worked was greater, and it wasn&#8217;t even a fully functional application. Of the test participants, every single one said they would choose the prototype over their current administrative interface, and it wasn&#8217;t even pretty (those of you who remember the original Crazyhorse will vouch for this). </p>
<p>A presentation on the process from start to finish was part of the schedule at WordCamp 2008 in San Francisco, and the <a href="http://www.slideshare.net/edanzico/riding-the-crazyhorse-future-generation-wordpress-presentation">slides are available online</a>, but as always the slides only tell you so much without the videos, live demo and verbal narration that went with it. (Use Google and you can see audience videos of the presentation.)</p>
<p>Here, then, is a PDF of reasonable size that you can download and peruse at your leisure that outlines the usability testing project in some detail. I wanted to include some eye tracking videos, but the file was so huge it would have been ridiculous for anyone to download it, so I stuck with eye tracking outputs called gaze trails to illustrate the findings. I also tried to pare down the text to the more salient points, since more than 50 hours of test video really does reveal an insane amount of data. I also cut out the section about designing Crazyhorse in the interest of staying under 25 pages. Hopefully you&#8217;ll think it&#8217;s a good balance. I&#8217;ll try to put together a separate document on the design process of 2.7 in a couple of weeks that will include the early Crazyhorse material. </p>
<p>So, if you want to know what we learned from the usability testing this summer that caused us to create what is now 2.7, go ahead and read the report. </p>
<p><a href='http://wpdotorg.wordpress.com/files/2008/10/wp-testreport-205-crazyhorse-1028a08jw.pdf'>WordPress 2.5/Crazyhorse Usability Testing Report (PDF)</a></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:89:"http://wordpress.org/development/2008/10/usability-testing-report-25-and-crazyhorse/feed/";}s:7:"summary";s:327:"A question I hear pretty frequently is, &#8220;Why a redesign of the admin panel so soon after 2.5?&#8221; Those who have attended WordCamps in the past few months have already heard the answer, but for the people who haven&#8217;t had that opportunity, this post is for you. 
When the community response to the 2.5 admin [...]";s:12:"atom_content";s:4403:"<p>A question I hear pretty frequently is, &#8220;Why a redesign of the admin panel so soon after 2.5?&#8221; Those who have attended WordCamps in the past few months have already heard the answer, but for the people who haven&#8217;t had that opportunity, this post is for you. </p>
<p>When the community response to the 2.5 admin redesign was mixed, it seemed like a good idea to do usability testing to find out which issues were based on actual interface problems vs. which complaints were just a result of not liking change. To prevent bias, a third party was contracted to conduct usability testing, <a href="http://cms.bsu.edu/Academics/CentersandInstitutes/CMD/InsightandResearch.aspx">Ball State University&#8217;s Center for Media Design, Insight and Research</a> division. Try saying that three times fast with a mouth full of peanut butter. Or fitting it on a business card. To save time, we&#8217;ll just call that third party CMD, since that&#8217;s what they call themselves.</p>
<p>The plan that was developed involved multiple rounds of testing, as well as the creation of two prototypes, hardcore! The first phase involved a usability review of 2.5 by CMD, the results of which were discussed with lead developers. A quick prototype was created that addressed some of the lightweight issues, so that the test participants could use both 2.5 on their own blogs and the prototype on a test site. Results would be analyzed and compared, leading to a second round of suggestions. A second prototype would be developed over a week or two, which would then be tested with the same participants, and a final report delivered. But you know what they say&#8230; the best laid plans of designers and developers often go awry. </p>
<p>After the first round of testing, it was clear that a prototype delivering the kind of fixes that could be coded in a week or two wouldn&#8217;t make much of a difference overall. We all decided a more ambitious prototype was in order, one that would experiment with a new approach to screen real estate and attempt to address as many of the issues from 2.5 as was possible with a few extra weeks of time. A rapid design process was followed by an even more rapid development cycle. The second prototype is what you know as Crazyhorse. </p>
<p>The second round of testing blew everyone away. The research team had never seen such consistent results. Tasks were completed faster, participant opinions rated it higher, understanding of how interface elements worked was greater, and it wasn&#8217;t even a fully functional application. Of the test participants, every single one said they would choose the prototype over their current administrative interface, and it wasn&#8217;t even pretty (those of you who remember the original Crazyhorse will vouch for this). </p>
<p>A presentation on the process from start to finish was part of the schedule at WordCamp 2008 in San Francisco, and the <a href="http://www.slideshare.net/edanzico/riding-the-crazyhorse-future-generation-wordpress-presentation">slides are available online</a>, but as always the slides only tell you so much without the videos, live demo and verbal narration that went with it. (Use Google and you can see audience videos of the presentation.)</p>
<p>Here, then, is a PDF of reasonable size that you can download and peruse at your leisure that outlines the usability testing project in some detail. I wanted to include some eye tracking videos, but the file was so huge it would have been ridiculous for anyone to download it, so I stuck with eye tracking outputs called gaze trails to illustrate the findings. I also tried to pare down the text to the more salient points, since more than 50 hours of test video really does reveal an insane amount of data. I also cut out the section about designing Crazyhorse in the interest of staying under 25 pages. Hopefully you&#8217;ll think it&#8217;s a good balance. I&#8217;ll try to put together a separate document on the design process of 2.7 in a couple of weeks that will include the early Crazyhorse material. </p>
<p>So, if you want to know what we learned from the usability testing this summer that caused us to create what is now 2.7, go ahead and read the report. </p>
<p><a href='http://wpdotorg.wordpress.com/files/2008/10/wp-testreport-205-crazyhorse-1028a08jw.pdf'>WordPress 2.5/Crazyhorse Usability Testing Report (PDF)</a></p>
";}i:5;a:12:{s:5:"title";s:43:"Calling All WordPress-loving Icon Designers";s:4:"link";s:85:"http://wordpress.org/development/2008/10/calling-all-wordpress-loving-icon-designers/";s:8:"comments";s:94:"http://wordpress.org/development/2008/10/calling-all-wordpress-loving-icon-designers/#comments";s:7:"pubdate";s:31:"Fri, 24 Oct 2008 20:33:04 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:28:"User Interface2.7designicons";s:4:"guid";s:39:"http://wordpress.org/development/?p=362";s:11:"description";s:323:"Have you seen the getting-prettier-all-the-time menus in 2.7-almost-beta? They really are. Getting prettier all the time, I mean. Once we drop in the fonts and do a little brushing up of edges and colors, the menu system is going to be smooth. The last thing we&#8217;ll need to do to is replace the icons we&#8217;ve [...]";s:7:"content";a:1:{s:7:"encoded";s:2939:"<p><img class="alignleft" title="2.7 Menus in Progress" src="http://wpdotorg.files.wordpress.com/2008/10/menu_102408a.gif" alt="" align="left" width="157" height="500" />Have you seen the getting-prettier-all-the-time menus in 2.7-almost-beta? They really are. Getting prettier all the time, I mean. Once we drop in the fonts and do a little brushing up of edges and colors, the menu system is going to be <em>smooth</em>. The last thing we&#8217;ll need to do to is replace the icons we&#8217;ve been using as placeholders. Currently, the menus are using icons from <a href="http://www.everaldo.com/crystal/">Crystal Project</a>, which is perfect because they&#8217;re released under LGPL (yay for open source!), but less perfect in that they don&#8217;t quite fit with the new visual style of 2.7, so we&#8217;re thinking custom icons.</p>
<p>I&#8217;m always meeting people at WordCamps or via email who say they wish they could give back to WordPress, but that since they aren&#8217;t PHP developers, they feel like there isn&#8217;t any opportunity for them to be a part of the open source project. Well, here&#8217;s a golden opportunity. Want to design the new WordPress icons?</p>
<p>The icons:<br />
We&#8217;ll need icons for each of the main navigation sections, plus a matching pair of list/excerpt view icons for the table screens like <em>Edit Posts</em>. That&#8217;s a total of 13, and for the navigation icons we&#8217;ll also need a larger size for use in the screen headers. Some of the sections have natural iconography, while others may be more challenging. The sections are: Dashboard, Posts, Media, Links, Pages, Comments, Appearance, Settings, Users, Plugins, Tools.</p>
<p>The style:<br />
Icons should be subtle, with a classic/designed look, nothing cartoonish. Thin lines. Maybe a little old-fashioned looking. They&#8217;ll be grayscale by default, possibly with a color version for active menu items.</p>
<p>The timing:<br />
Fast, fast, fast. 2.7 is due to release on November 10. That means icons need to be ready within two weeks, give or take.</p>
<p>The required experience:<br />
To be taken seriously, you&#8217;ll need to show a background in icon design. It&#8217;s a different skill than web site or application design, and given that there&#8217;s not much time before the 2.7 launch, someone with experience (and possibly existing work they can leverage) is going to be the best candidate.</p>
<p>Interested? <a href="mailto:jane_at-sign_automattic_dot_com">Send us an email</a> and tell us why you want to design the icons, and include a link to your portfolio. How we wind up choosing an icon designer will depend on how many people respond, but we&#8217;ll keep you posted on the process. For now, send in portfolio links by Saturday night, October 25, 2008. We&#8217;ll review them over the weekend and get in touch with people on Monday. Hopefully we can be designing by early next week.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:90:"http://wordpress.org/development/2008/10/calling-all-wordpress-loving-icon-designers/feed/";}s:7:"summary";s:323:"Have you seen the getting-prettier-all-the-time menus in 2.7-almost-beta? They really are. Getting prettier all the time, I mean. Once we drop in the fonts and do a little brushing up of edges and colors, the menu system is going to be smooth. The last thing we&#8217;ll need to do to is replace the icons we&#8217;ve [...]";s:12:"atom_content";s:2939:"<p><img class="alignleft" title="2.7 Menus in Progress" src="http://wpdotorg.files.wordpress.com/2008/10/menu_102408a.gif" alt="" align="left" width="157" height="500" />Have you seen the getting-prettier-all-the-time menus in 2.7-almost-beta? They really are. Getting prettier all the time, I mean. Once we drop in the fonts and do a little brushing up of edges and colors, the menu system is going to be <em>smooth</em>. The last thing we&#8217;ll need to do to is replace the icons we&#8217;ve been using as placeholders. Currently, the menus are using icons from <a href="http://www.everaldo.com/crystal/">Crystal Project</a>, which is perfect because they&#8217;re released under LGPL (yay for open source!), but less perfect in that they don&#8217;t quite fit with the new visual style of 2.7, so we&#8217;re thinking custom icons.</p>
<p>I&#8217;m always meeting people at WordCamps or via email who say they wish they could give back to WordPress, but that since they aren&#8217;t PHP developers, they feel like there isn&#8217;t any opportunity for them to be a part of the open source project. Well, here&#8217;s a golden opportunity. Want to design the new WordPress icons?</p>
<p>The icons:<br />
We&#8217;ll need icons for each of the main navigation sections, plus a matching pair of list/excerpt view icons for the table screens like <em>Edit Posts</em>. That&#8217;s a total of 13, and for the navigation icons we&#8217;ll also need a larger size for use in the screen headers. Some of the sections have natural iconography, while others may be more challenging. The sections are: Dashboard, Posts, Media, Links, Pages, Comments, Appearance, Settings, Users, Plugins, Tools.</p>
<p>The style:<br />
Icons should be subtle, with a classic/designed look, nothing cartoonish. Thin lines. Maybe a little old-fashioned looking. They&#8217;ll be grayscale by default, possibly with a color version for active menu items.</p>
<p>The timing:<br />
Fast, fast, fast. 2.7 is due to release on November 10. That means icons need to be ready within two weeks, give or take.</p>
<p>The required experience:<br />
To be taken seriously, you&#8217;ll need to show a background in icon design. It&#8217;s a different skill than web site or application design, and given that there&#8217;s not much time before the 2.7 launch, someone with experience (and possibly existing work they can leverage) is going to be the best candidate.</p>
<p>Interested? <a href="mailto:jane_at-sign_automattic_dot_com">Send us an email</a> and tell us why you want to design the icons, and include a link to your portfolio. How we wind up choosing an icon designer will depend on how many people respond, but we&#8217;ll keep you posted on the process. For now, send in portfolio links by Saturday night, October 25, 2008. We&#8217;ll review them over the weekend and get in touch with people on Monday. Hopefully we can be designing by early next week.</p>
";}i:6;a:12:{s:5:"title";s:15:"WordPress 2.6.3";s:4:"link";s:55:"http://wordpress.org/development/2008/10/wordpress-263/";s:8:"comments";s:64:"http://wordpress.org/development/2008/10/wordpress-263/#comments";s:7:"pubdate";s:31:"Thu, 23 Oct 2008 23:08:38 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:39:"http://wordpress.org/development/?p=356";s:11:"description";s:344:"A vulnerability in the Snoopy library was announced today.  WordPress uses Snoopy to fetch the feeds shown in the Dashboard.   Although this seems to be a low risk vulnerability for WordPress users, we wanted to get an update out immediately.  2.6.3 is available for download right now.  If you don&#8217;t want to download the whole [...]";s:7:"content";a:1:{s:7:"encoded";s:875:"<p>A <a href="http://secunia.com/Advisories/32361/">vulnerability</a> in the <a href="http://sourceforge.net/projects/snoopy/">Snoopy</a> library was announced today.  WordPress uses Snoopy to fetch the feeds shown in the Dashboard.   Although this seems to be a low risk vulnerability for WordPress users, we wanted to get an update out immediately.  2.6.3 is <a href="http://wordpress.org/download/">available for download</a> right now.  If you don&#8217;t want to download the whole release to get the security fix, you can download the following two files and copy them over your 2.6.2 installation.</p>
<ol>
<li><a href="http://trac.wordpress.org/export/9310/tags/2.6.3/wp-includes/class-snoopy.php">wp-includes/class-snoopy.php</a></li>
<li><a href="http://trac.wordpress.org/export/9310/tags/2.6.3/wp-includes/version.php">wp-includes/version.php</a></li>
</ol>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2008/10/wordpress-263/feed/";}s:7:"summary";s:344:"A vulnerability in the Snoopy library was announced today.  WordPress uses Snoopy to fetch the feeds shown in the Dashboard.   Although this seems to be a low risk vulnerability for WordPress users, we wanted to get an update out immediately.  2.6.3 is available for download right now.  If you don&#8217;t want to download the whole [...]";s:12:"atom_content";s:875:"<p>A <a href="http://secunia.com/Advisories/32361/">vulnerability</a> in the <a href="http://sourceforge.net/projects/snoopy/">Snoopy</a> library was announced today.  WordPress uses Snoopy to fetch the feeds shown in the Dashboard.   Although this seems to be a low risk vulnerability for WordPress users, we wanted to get an update out immediately.  2.6.3 is <a href="http://wordpress.org/download/">available for download</a> right now.  If you don&#8217;t want to download the whole release to get the security fix, you can download the following two files and copy them over your 2.6.2 installation.</p>
<ol>
<li><a href="http://trac.wordpress.org/export/9310/tags/2.6.3/wp-includes/class-snoopy.php">wp-includes/class-snoopy.php</a></li>
<li><a href="http://trac.wordpress.org/export/9310/tags/2.6.3/wp-includes/version.php">wp-includes/version.php</a></li>
</ol>
";}i:7;a:12:{s:5:"title";s:21:"The New 2.7 Dashboard";s:4:"link";s:62:"http://wordpress.org/development/2008/10/the-new-27-dashboard/";s:8:"comments";s:71:"http://wordpress.org/development/2008/10/the-new-27-dashboard/#comments";s:7:"pubdate";s:31:"Mon, 20 Oct 2008 18:09:35 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:42:"User Interface2.7dashboarddesignquickpress";s:4:"guid";s:39:"http://wordpress.org/development/?p=349";s:11:"description";s:335:"First, I&#8217;d like to say that I&#8217;m glad the majority response to the screenshots we posted last week was so positive. With a community as vocal as this one, it&#8217;s always a little nerve-wracking to introduce change, but this time it seems like the change was welcomed, which has been great. I&#8217;m hopeful that as [...]";s:7:"content";a:1:{s:7:"encoded";s:8846:"<p>First, I&#8217;d like to say that I&#8217;m glad the majority response to the <a title="The Visual Design of 2.7" href="http://wordpress.org/development/2008/10/the-visual-design-of-27/">screenshots we posted last week</a> was so positive. With a community as vocal as this one, it&#8217;s always a little nerve-wracking to introduce change, but this time it seems like the change was welcomed, which has been great. I&#8217;m hopeful that as we introduce the new features of 2.7 over the coming weeks, the good feelings will continue. As promised, here&#8217;s a rundown of what&#8217;s going to happen to the Dashboard over the next couple of weeks before launch.</p>
<p><strong>Menus</strong><br />
I described the menu functions last week, but I forgot to mention something. By default, when you arrive at your Dashboard the first time, two sections of the navigation will be expanded: the Dashboard section (because it is active, so it will have the color highlight) and the Posts section (because it has often-accessed screens in it, and will serve as a cue that you can view other section menus without loading new screens). Once you start clicking menus open and closed, your browser will cookie you, and will remember your menu state. So if you open Posts and Comments, when you come back the next time, Posts and Comments will be open. If you click into your Settings, Posts and Comments will still be open. You&#8217;ll need to manually close nav sections. We went back and forth on this, and there was community discussion about perhaps only allowing two sections to be open at a time, but ultimately those approaches would have removed control from the user. And since the mantra of 2.7 is to give the user control over his/her admin interface, we chose to keeps things open if the user had opened them.</p>
<p><strong>Contextual Access Tabs</strong><br />
In the upper right, drop-tabs provide access to contextual features displayed in a layer that appears between the header and the main working area. Screen Options will allow you to choose which modules to display on the current screen. Don&#8217;t like seeing the Incoming Links module because no one links to you? A simple checkbox in the Options tab will remove the module from your Dashboard until you decide to reinstate it. Help will highlight some of the changes since the previous version, and provide links to help resources such as FAQ/Forums/Contact Support for .com and Documentation/Support Forums for .org.</p>
<p><strong>Module Layout</strong><br />
In addition to using the Options tab to decide which modules to display on the Dashboard, all the modules on the Dashboard may be moved up or down or between columns using drag and drop. Modules also may be collapsed or expanded by clicking the title bar, allowing another level of screen customization. In 2.8, we also hope to make every single module configurable in terms of what content it displays&#8230; we ran out of time for this in 2.7, so for now only the newsfeed modules will be configurable. When you hover over the module, a link will appear in the module header  allowing access to the configuration view.</p>
<p><strong>Right Now</strong><br />
The Right Now module contains the same data as before, but it&#8217;s been rearranged to provide a clearer display. This list style, as opposed to the previous sentence style, will also make translation for non-English sites easier. Color cues help to highlight things that are not good (red), things that are pending (yellow/orange), and things that are good to go (green).</p>
<p><strong>Stats</strong><br />
I&#8217;d like to apologize for having a non-core piece of functionality on the Dashboard comp. It&#8217;s my fault&#8230; when we were working on the comps, we used my wireframes and my live 2.7 Dashboard to assemble our elements, and I forgot that I had the <a title="WordPress.com stats plugin" href="http://wordpress.org/extend/plugins/stats/">WordPress.com stats plugin</a> installed and a module on my Dashboard. So even though it&#8217;s not in core and it turns out the WordPress.com stats plugin is undergoing some reworking of its own, we made the Dashboard stats module easier to scan than the one I currently see when I log in. For those of you on .org who got excited when you saw the Dashboard comp with stats, again, I apologize for the oversight on my part. If you want the candy-like stats goodness we comped up you&#8217;d need to install the plugin (or another stats plugin with candy-like elements). There should be a fine-looking Dashboard module as part of the update they release. </p>
<p><strong>QuickPress</strong><br />
QuickPress is a new feature that provides the ability to start (or publish) a simple post from the Dashboard when you don&#8217;t need the full feature set of the Add New Post screen. Currently, these posts can contain title, text, media and tags. In 2.8 we hope to make the module configurable, so that each user can decide which few fields make the most sense to display. If you Save as Draft, you will see the new draft appear in the Recent Drafts module right away. Clicking Cancel will clear the form. Publish publishes the post. Posts made using QuickPress are the same as other posts and may be editing by going to Posts &gt; Edit and selecting the post in question. One last thing: both in this module and on the Add New post screen, we&#8217;ve put as much space as possible between the Save Draft and Publish buttons, so for all of you who&#8217;ve asked at WordCamps or emailed or posted somewhere to request this, ta da! Hopefully this will reduce accidental publications.</p>
<p><strong>Recent Drafts</strong><br />
During the summer testing, one thing we heard over and over was the desire to access recent drafts more easily, preferably with one click from the Dashboard (as opposed to clicking on Drafts from the Right Now module, waiting for page to load, then clicking on a specific draft title and waiting for a second page load). The Recent Drafts module is meant to address that need, displaying the five most recent drafts with the date they were created. In a future version, this module will be configurable as well. In the meantime, if you&#8217;re a crosswords-in-pen kind of person and you don&#8217;t write drafts, just use the Options tab at the top to hide the Drafts module, and it won&#8217;t take up space on your Dashboard.</p>
<p><strong>Feeds</strong><br />
News feeds of WordPress-related news will function largely the same as they did in 2.6 in terms of configurability, and will simply have a new look. You can still specify the URL of the feed, how many items to display, whether to show headline vs excerpt, author, date, etc.</p>
<p><strong>Incoming Links</strong><br />
Just getting a face lift. Or maybe not a face lift, more like a visit to the Clinique counter.</p>
<p><strong>Hooks</strong><br />
Plugins can still add modules to the Dashboard. They also still can add top-level menu items if necessary (as opposed to having them in Tools, Plugins, Settings or wherever&#8230;like Posts if it&#8217;s post-specific). Because we&#8217;ll be using iconography in the collapsed menu state, plugins that create top-level menus can create an icon for use in the menu system. When there&#8217;s no icon associated with the plugin, a default will be used (kind of the way some blogs show default avatars when no Gravatar is associated with a commenter on your blog). Hopefully, though, most plugins will fit within existing section headers, since our &#8220;top level&#8221; is not actually made up of menu items, but section headers that open to reveal the real menu items that have screens associated with them. Plugins can also put themselves into the Shortcuts/Favorites menu in the header. </p>
<p><strong>Recent Comments</strong><br />
This module, as in 2.6, displays the most recent comments. However, you now can moderate comments directly from this Dashboard module, including the new Comment Reply feature. For now it will show only the last x number of comments, as it does currently, though in 2.8 we hope to add more configurability to this, or roll it into the Inbox concept.</p>
<p><strong>Bye-Bye Inbox</strong><br />
For those who were at WordCamp SF or who were using the nightly builds while there was still an Inbox placeholder, sorry, no Inbox in 2.7. It turned out to be far more complex than anticipated, and rather than including something rushed and clunky, we&#8217;re holding off until a later version. We added the comment moderation to the Comments module to make up for it, so you don&#8217;t have to wait for that, at least.</p>
<p>So that&#8217;s the new Dashboard. A little more usable, a little prettier, a little more you, a little cooler. Or maybe a lot of all those things. We&#8217;ll let you be the judge.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:67:"http://wordpress.org/development/2008/10/the-new-27-dashboard/feed/";}s:7:"summary";s:335:"First, I&#8217;d like to say that I&#8217;m glad the majority response to the screenshots we posted last week was so positive. With a community as vocal as this one, it&#8217;s always a little nerve-wracking to introduce change, but this time it seems like the change was welcomed, which has been great. I&#8217;m hopeful that as [...]";s:12:"atom_content";s:8846:"<p>First, I&#8217;d like to say that I&#8217;m glad the majority response to the <a title="The Visual Design of 2.7" href="http://wordpress.org/development/2008/10/the-visual-design-of-27/">screenshots we posted last week</a> was so positive. With a community as vocal as this one, it&#8217;s always a little nerve-wracking to introduce change, but this time it seems like the change was welcomed, which has been great. I&#8217;m hopeful that as we introduce the new features of 2.7 over the coming weeks, the good feelings will continue. As promised, here&#8217;s a rundown of what&#8217;s going to happen to the Dashboard over the next couple of weeks before launch.</p>
<p><strong>Menus</strong><br />
I described the menu functions last week, but I forgot to mention something. By default, when you arrive at your Dashboard the first time, two sections of the navigation will be expanded: the Dashboard section (because it is active, so it will have the color highlight) and the Posts section (because it has often-accessed screens in it, and will serve as a cue that you can view other section menus without loading new screens). Once you start clicking menus open and closed, your browser will cookie you, and will remember your menu state. So if you open Posts and Comments, when you come back the next time, Posts and Comments will be open. If you click into your Settings, Posts and Comments will still be open. You&#8217;ll need to manually close nav sections. We went back and forth on this, and there was community discussion about perhaps only allowing two sections to be open at a time, but ultimately those approaches would have removed control from the user. And since the mantra of 2.7 is to give the user control over his/her admin interface, we chose to keeps things open if the user had opened them.</p>
<p><strong>Contextual Access Tabs</strong><br />
In the upper right, drop-tabs provide access to contextual features displayed in a layer that appears between the header and the main working area. Screen Options will allow you to choose which modules to display on the current screen. Don&#8217;t like seeing the Incoming Links module because no one links to you? A simple checkbox in the Options tab will remove the module from your Dashboard until you decide to reinstate it. Help will highlight some of the changes since the previous version, and provide links to help resources such as FAQ/Forums/Contact Support for .com and Documentation/Support Forums for .org.</p>
<p><strong>Module Layout</strong><br />
In addition to using the Options tab to decide which modules to display on the Dashboard, all the modules on the Dashboard may be moved up or down or between columns using drag and drop. Modules also may be collapsed or expanded by clicking the title bar, allowing another level of screen customization. In 2.8, we also hope to make every single module configurable in terms of what content it displays&#8230; we ran out of time for this in 2.7, so for now only the newsfeed modules will be configurable. When you hover over the module, a link will appear in the module header  allowing access to the configuration view.</p>
<p><strong>Right Now</strong><br />
The Right Now module contains the same data as before, but it&#8217;s been rearranged to provide a clearer display. This list style, as opposed to the previous sentence style, will also make translation for non-English sites easier. Color cues help to highlight things that are not good (red), things that are pending (yellow/orange), and things that are good to go (green).</p>
<p><strong>Stats</strong><br />
I&#8217;d like to apologize for having a non-core piece of functionality on the Dashboard comp. It&#8217;s my fault&#8230; when we were working on the comps, we used my wireframes and my live 2.7 Dashboard to assemble our elements, and I forgot that I had the <a title="WordPress.com stats plugin" href="http://wordpress.org/extend/plugins/stats/">WordPress.com stats plugin</a> installed and a module on my Dashboard. So even though it&#8217;s not in core and it turns out the WordPress.com stats plugin is undergoing some reworking of its own, we made the Dashboard stats module easier to scan than the one I currently see when I log in. For those of you on .org who got excited when you saw the Dashboard comp with stats, again, I apologize for the oversight on my part. If you want the candy-like stats goodness we comped up you&#8217;d need to install the plugin (or another stats plugin with candy-like elements). There should be a fine-looking Dashboard module as part of the update they release. </p>
<p><strong>QuickPress</strong><br />
QuickPress is a new feature that provides the ability to start (or publish) a simple post from the Dashboard when you don&#8217;t need the full feature set of the Add New Post screen. Currently, these posts can contain title, text, media and tags. In 2.8 we hope to make the module configurable, so that each user can decide which few fields make the most sense to display. If you Save as Draft, you will see the new draft appear in the Recent Drafts module right away. Clicking Cancel will clear the form. Publish publishes the post. Posts made using QuickPress are the same as other posts and may be editing by going to Posts &gt; Edit and selecting the post in question. One last thing: both in this module and on the Add New post screen, we&#8217;ve put as much space as possible between the Save Draft and Publish buttons, so for all of you who&#8217;ve asked at WordCamps or emailed or posted somewhere to request this, ta da! Hopefully this will reduce accidental publications.</p>
<p><strong>Recent Drafts</strong><br />
During the summer testing, one thing we heard over and over was the desire to access recent drafts more easily, preferably with one click from the Dashboard (as opposed to clicking on Drafts from the Right Now module, waiting for page to load, then clicking on a specific draft title and waiting for a second page load). The Recent Drafts module is meant to address that need, displaying the five most recent drafts with the date they were created. In a future version, this module will be configurable as well. In the meantime, if you&#8217;re a crosswords-in-pen kind of person and you don&#8217;t write drafts, just use the Options tab at the top to hide the Drafts module, and it won&#8217;t take up space on your Dashboard.</p>
<p><strong>Feeds</strong><br />
News feeds of WordPress-related news will function largely the same as they did in 2.6 in terms of configurability, and will simply have a new look. You can still specify the URL of the feed, how many items to display, whether to show headline vs excerpt, author, date, etc.</p>
<p><strong>Incoming Links</strong><br />
Just getting a face lift. Or maybe not a face lift, more like a visit to the Clinique counter.</p>
<p><strong>Hooks</strong><br />
Plugins can still add modules to the Dashboard. They also still can add top-level menu items if necessary (as opposed to having them in Tools, Plugins, Settings or wherever&#8230;like Posts if it&#8217;s post-specific). Because we&#8217;ll be using iconography in the collapsed menu state, plugins that create top-level menus can create an icon for use in the menu system. When there&#8217;s no icon associated with the plugin, a default will be used (kind of the way some blogs show default avatars when no Gravatar is associated with a commenter on your blog). Hopefully, though, most plugins will fit within existing section headers, since our &#8220;top level&#8221; is not actually made up of menu items, but section headers that open to reveal the real menu items that have screens associated with them. Plugins can also put themselves into the Shortcuts/Favorites menu in the header. </p>
<p><strong>Recent Comments</strong><br />
This module, as in 2.6, displays the most recent comments. However, you now can moderate comments directly from this Dashboard module, including the new Comment Reply feature. For now it will show only the last x number of comments, as it does currently, though in 2.8 we hope to add more configurability to this, or roll it into the Inbox concept.</p>
<p><strong>Bye-Bye Inbox</strong><br />
For those who were at WordCamp SF or who were using the nightly builds while there was still an Inbox placeholder, sorry, no Inbox in 2.7. It turned out to be far more complex than anticipated, and rather than including something rushed and clunky, we&#8217;re holding off until a later version. We added the comment moderation to the Comments module to make up for it, so you don&#8217;t have to wait for that, at least.</p>
<p>So that&#8217;s the new Dashboard. A little more usable, a little prettier, a little more you, a little cooler. Or maybe a lot of all those things. We&#8217;ll let you be the judge.</p>
";}i:8;a:12:{s:5:"title";s:24:"The Visual Design of 2.7";s:4:"link";s:65:"http://wordpress.org/development/2008/10/the-visual-design-of-27/";s:8:"comments";s:74:"http://wordpress.org/development/2008/10/the-visual-design-of-27/#comments";s:7:"pubdate";s:31:"Fri, 17 Oct 2008 15:31:22 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:55:"User Interface2.7crazyhorsedashboarddesignnewpostscreen";s:4:"guid";s:39:"http://wordpress.org/development/?p=342";s:11:"description";s:357:"It&#8217;s finally here, the moment you&#8217;ve all been waiting for! The long months of your tolerance and forbearance as you suffered through the inelegance of our hacked-together, leftover  Crazyhorse interface are almost at an end. (Was it really that painful?)
The visuals you have been craving are finally finished enough to show, and have been [...]";s:7:"content";a:1:{s:7:"encoded";s:3869:"<p>It&#8217;s finally here, the moment you&#8217;ve all been waiting for! The long months of your tolerance and forbearance as you suffered through the inelegance of our hacked-together, leftover  Crazyhorse interface are almost at an end. (Was it really that painful?)</p>
<p>The visuals you have been craving are finally finished enough to show, and have been approved by the lead developers. We hope you like them. Mad props to Matt Thomas and Andy Peatling for their visual talents. You can expect these designs to be extended to the rest of the 2.7 screens and implemented over the coming weeks.</p>
<p>So now that we finally nailed down the look, how&#8217;s it going to work? The menu system in particular has been the topic of discussion on the hackers and testers lists, so I thought I would take this opportunity to explain how we plan for it to work. As you know, one of the goals of 2.7 was to reduce the necessity to load new screens just to access sub-navigation menus; we wanted the most-used screens to be within a click or two at most. If you&#8217;ve been using the nightly builds, you got used to the arrow controls that allowed you to expand and contract the menus. Then you got used to the box-style with icons that not only opened and closed vertically, but could be minimized horizontally as well, leaving a remnant of icons to provide a kind of &#8220;advanced mode,&#8221; though you don&#8217;t need to be particularly advanced to use it. Now that we have real button styles (the icons are still placeholders, and we hope to have some new ones soonish), we&#8217;ve nailed down the menu functionality.</p>
<div class="wp-caption aligncenter" style="width: 607px"><img title="2.7 New Post Screen, Unfinished" src="http://wpdotorg.files.wordpress.com/2008/10/newpost.png" alt="2.7 New Post Screen, Unfinished" width="597" height="402" /><p class="wp-caption-text">2.7 New Post Screen, Unfinished</p></div>
<p>Each section header has three parts: the icon on the left, the blue link text, and the area to the right where an expansion arrow appears on hover or in expanded state. You can see that the arrow is contained in a small segment of the header, similar to the way the favorites menu is structured. If you click on this segment, the menu will expand to show the choices in that section.  Click again to close the menu. Click on the blue link text and you will go directly to the screen for the first choice in that section, where the section menu will be opened to show you the other section choices. Double-click on the section icon and the menu will close horizontally, leaving the icon list visible. In this state, hovering over the icons will display the menus for each section, so you&#8217;re still only a click away from most screens. Double-click on an icon when the menu is closed this way and it will take you to the first screen in that section. The small arrows attached to the dividing lines between menu groups will also act as open/close toggles for using the horizontal collapse/expand function.</p>
<p>This variety of ways of using the menu system aims to accommodate both power user and novice alike. Clicking on blue link text like normal will bring the expected result for the novice, while the advanced user has more options for navigation that allow a more customized experience. We hope you like this result as much as we do, and you can expect to see it implemented in Trunk soon.</p>
<p>The image below is the new Dashboard style, for which I&#8217;ll save the explanations until early next week, but hopefully the preview will get you excited for the new design.</p>
<div class="wp-caption aligncenter" style="width: 607px"><img title="2.7 Dashboard" src="http://wpdotorg.files.wordpress.com/2008/10/dashboard.png" alt="2.7 Dashboard" width="597" height="753" /><p class="wp-caption-text">2.7 Dashboard</p></div>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:70:"http://wordpress.org/development/2008/10/the-visual-design-of-27/feed/";}s:7:"summary";s:357:"It&#8217;s finally here, the moment you&#8217;ve all been waiting for! The long months of your tolerance and forbearance as you suffered through the inelegance of our hacked-together, leftover  Crazyhorse interface are almost at an end. (Was it really that painful?)
The visuals you have been craving are finally finished enough to show, and have been [...]";s:12:"atom_content";s:3869:"<p>It&#8217;s finally here, the moment you&#8217;ve all been waiting for! The long months of your tolerance and forbearance as you suffered through the inelegance of our hacked-together, leftover  Crazyhorse interface are almost at an end. (Was it really that painful?)</p>
<p>The visuals you have been craving are finally finished enough to show, and have been approved by the lead developers. We hope you like them. Mad props to Matt Thomas and Andy Peatling for their visual talents. You can expect these designs to be extended to the rest of the 2.7 screens and implemented over the coming weeks.</p>
<p>So now that we finally nailed down the look, how&#8217;s it going to work? The menu system in particular has been the topic of discussion on the hackers and testers lists, so I thought I would take this opportunity to explain how we plan for it to work. As you know, one of the goals of 2.7 was to reduce the necessity to load new screens just to access sub-navigation menus; we wanted the most-used screens to be within a click or two at most. If you&#8217;ve been using the nightly builds, you got used to the arrow controls that allowed you to expand and contract the menus. Then you got used to the box-style with icons that not only opened and closed vertically, but could be minimized horizontally as well, leaving a remnant of icons to provide a kind of &#8220;advanced mode,&#8221; though you don&#8217;t need to be particularly advanced to use it. Now that we have real button styles (the icons are still placeholders, and we hope to have some new ones soonish), we&#8217;ve nailed down the menu functionality.</p>
<div class="wp-caption aligncenter" style="width: 607px"><img title="2.7 New Post Screen, Unfinished" src="http://wpdotorg.files.wordpress.com/2008/10/newpost.png" alt="2.7 New Post Screen, Unfinished" width="597" height="402" /><p class="wp-caption-text">2.7 New Post Screen, Unfinished</p></div>
<p>Each section header has three parts: the icon on the left, the blue link text, and the area to the right where an expansion arrow appears on hover or in expanded state. You can see that the arrow is contained in a small segment of the header, similar to the way the favorites menu is structured. If you click on this segment, the menu will expand to show the choices in that section.  Click again to close the menu. Click on the blue link text and you will go directly to the screen for the first choice in that section, where the section menu will be opened to show you the other section choices. Double-click on the section icon and the menu will close horizontally, leaving the icon list visible. In this state, hovering over the icons will display the menus for each section, so you&#8217;re still only a click away from most screens. Double-click on an icon when the menu is closed this way and it will take you to the first screen in that section. The small arrows attached to the dividing lines between menu groups will also act as open/close toggles for using the horizontal collapse/expand function.</p>
<p>This variety of ways of using the menu system aims to accommodate both power user and novice alike. Clicking on blue link text like normal will bring the expected result for the novice, while the advanced user has more options for navigation that allow a more customized experience. We hope you like this result as much as we do, and you can expect to see it implemented in Trunk soon.</p>
<p>The image below is the new Dashboard style, for which I&#8217;ll save the explanations until early next week, but hopefully the preview will get you excited for the new design.</p>
<div class="wp-caption aligncenter" style="width: 607px"><img title="2.7 Dashboard" src="http://wpdotorg.files.wordpress.com/2008/10/dashboard.png" alt="2.7 Dashboard" width="597" height="753" /><p class="wp-caption-text">2.7 Dashboard</p></div>
";}i:9;a:12:{s:5:"title";s:24:"WordPress 2.7 Wireframes";s:4:"link";s:65:"http://wordpress.org/development/2008/10/wordpress-27-wireframes/";s:8:"comments";s:74:"http://wordpress.org/development/2008/10/wordpress-27-wireframes/#comments";s:7:"pubdate";s:31:"Wed, 01 Oct 2008 19:52:44 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:27:"User Interface2.7wireframes";s:4:"guid";s:39:"http://wordpress.org/development/?p=333";s:11:"description";s:349:"For those of you who have been downloading the nightly builds or contributing code to 2.7, you&#8217;ve noticed how quickly features are being added, small layout changes are gradually being implemented, and the application is morphing before your very eyes. For the most part, the response has been extremely positive, but even the people who [...]";s:7:"content";a:1:{s:7:"encoded";s:3970:"<p><a href="http://wpdotorg.files.wordpress.com/2008/10/wf-dashboard_v002_093008jw.pdf"><img src="http://wpdotorg.files.wordpress.com/2008/10/2-7-wf-badgenew3.gif" align="left"/></a>For those of you who have been downloading the nightly builds or contributing code to 2.7, you&#8217;ve noticed how quickly features are being added, small layout changes are gradually being implemented, and the application is morphing before your very eyes. For the most part, the response has been extremely positive, but even the people who love 2.7 have been wondering what it&#8217;s going to end up looking like. Though 2.7 is still a work in progress, we&#8217;ve put together <a href="http://wpdotorg.files.wordpress.com/2008/10/wf-dashboard_v002_093008jw.pdf">a set of wireframes</a> to illustrate how we think it will all turn out, so you can take a look under the hood of the design process, so to speak.</p>
<p>The PDF attached to this post outlines the navigation model, header elements, and important screens such as the dashboard, the new post screen, and list screens for posts, comments, and media.</p>
<p>Some things to bear in mind if you&#8217;re not used to looking at wireframes:</p>
<p>1. These are a guide, not a dictate. Changes may be made by developers and designers as needed for technical, aesthetic and/or usability reasons. When you have a team of superfast developers like we do, sometimes wireframes can become out of date quickly. In the two hours since these wireframes were approved, for example, already there are a few things that have moved and a menu change or two. Tweaks will continue to be made over the next week or two before freeze. This is Alpha software, not Beta, and it&#8217;s not static. That&#8217;s part of what makes it exciting, that every time it&#8217;s updated there&#8217;s something new.</p>
<p>2. These are all black/grey/white. That&#8217;s because we have a designer hard at work on visual styles for the new admin panel, including color palette, fonts, graphic elements, etc. When we have a new look to show off, we will. For now, the wireframes are &#8220;lookless&#8221; on purpose.</p>
<p>3. Not every screen is wireframed. We focused on creating wireframes for those screens that are undergoing the most change. For screens retaining largely the same functionality and layout, we have not included wireframes. In some cases, we&#8217;ll be updating screens but haven&#8217;t decided how to do it yet, so those aren&#8217;t included either.</p>
<p>4. Some elements apply directly to wordpress.com or wordpress.org, so don&#8217;t be alarmed if you see something that doesn&#8217;t seem to apply (like multiple dashboards).</p>
<p>One of the things I love best about WordPress is the vibrant community full of talented developers and designers who care about the application and want it to be the best it can be. Despite the overwhelmingly positive response we&#8217;ve gotten when showing 2.7 at WordCamps and from the majority of the community, there will always be people who would prefer it to be structured another way, which is why we love plugins! The decisions that went into 2.7 were based on a combination of usability testing results from 2.5 and Crazyhorse (both including laser eye tracking, official report to be released soon, but <a href="http://www.slideshare.net/edanzico/riding-the-crazyhorse-future-generation-wordpress-presentation">slides from WordCamp SF</a> available in meantime), community feedback, personal and professional opinions, and some thinking about where the next couple of versions will be going in terms of new features, so that we will have a design that scales to accommodate some the features we hope to incorporate in the future.</p>
<p>So, I hope you enjoy getting an inside look at how we&#8217;ve been organizing our thoughts around 2.7, and that when the community feedback starts flowing everyone remembers that we all want the same thing: the best WordPress possible.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:70:"http://wordpress.org/development/2008/10/wordpress-27-wireframes/feed/";}s:7:"summary";s:349:"For those of you who have been downloading the nightly builds or contributing code to 2.7, you&#8217;ve noticed how quickly features are being added, small layout changes are gradually being implemented, and the application is morphing before your very eyes. For the most part, the response has been extremely positive, but even the people who [...]";s:12:"atom_content";s:3970:"<p><a href="http://wpdotorg.files.wordpress.com/2008/10/wf-dashboard_v002_093008jw.pdf"><img src="http://wpdotorg.files.wordpress.com/2008/10/2-7-wf-badgenew3.gif" align="left"/></a>For those of you who have been downloading the nightly builds or contributing code to 2.7, you&#8217;ve noticed how quickly features are being added, small layout changes are gradually being implemented, and the application is morphing before your very eyes. For the most part, the response has been extremely positive, but even the people who love 2.7 have been wondering what it&#8217;s going to end up looking like. Though 2.7 is still a work in progress, we&#8217;ve put together <a href="http://wpdotorg.files.wordpress.com/2008/10/wf-dashboard_v002_093008jw.pdf">a set of wireframes</a> to illustrate how we think it will all turn out, so you can take a look under the hood of the design process, so to speak.</p>
<p>The PDF attached to this post outlines the navigation model, header elements, and important screens such as the dashboard, the new post screen, and list screens for posts, comments, and media.</p>
<p>Some things to bear in mind if you&#8217;re not used to looking at wireframes:</p>
<p>1. These are a guide, not a dictate. Changes may be made by developers and designers as needed for technical, aesthetic and/or usability reasons. When you have a team of superfast developers like we do, sometimes wireframes can become out of date quickly. In the two hours since these wireframes were approved, for example, already there are a few things that have moved and a menu change or two. Tweaks will continue to be made over the next week or two before freeze. This is Alpha software, not Beta, and it&#8217;s not static. That&#8217;s part of what makes it exciting, that every time it&#8217;s updated there&#8217;s something new.</p>
<p>2. These are all black/grey/white. That&#8217;s because we have a designer hard at work on visual styles for the new admin panel, including color palette, fonts, graphic elements, etc. When we have a new look to show off, we will. For now, the wireframes are &#8220;lookless&#8221; on purpose.</p>
<p>3. Not every screen is wireframed. We focused on creating wireframes for those screens that are undergoing the most change. For screens retaining largely the same functionality and layout, we have not included wireframes. In some cases, we&#8217;ll be updating screens but haven&#8217;t decided how to do it yet, so those aren&#8217;t included either.</p>
<p>4. Some elements apply directly to wordpress.com or wordpress.org, so don&#8217;t be alarmed if you see something that doesn&#8217;t seem to apply (like multiple dashboards).</p>
<p>One of the things I love best about WordPress is the vibrant community full of talented developers and designers who care about the application and want it to be the best it can be. Despite the overwhelmingly positive response we&#8217;ve gotten when showing 2.7 at WordCamps and from the majority of the community, there will always be people who would prefer it to be structured another way, which is why we love plugins! The decisions that went into 2.7 were based on a combination of usability testing results from 2.5 and Crazyhorse (both including laser eye tracking, official report to be released soon, but <a href="http://www.slideshare.net/edanzico/riding-the-crazyhorse-future-generation-wordpress-presentation">slides from WordCamp SF</a> available in meantime), community feedback, personal and professional opinions, and some thinking about where the next couple of versions will be going in terms of new features, so that we will have a design that scales to accommodate some the features we hope to incorporate in the future.</p>
<p>So, I hope you enjoy getting an inside look at how we&#8217;ve been organizing our thoughts around 2.7, and that when the community feedback starts flowing everyone remembers that we all want the same thing: the best WordPress possible.</p>
";}}s:7:"channel";a:8:{s:5:"title";s:26:"WordPress Development Blog";s:4:"link";s:32:"http://wordpress.org/development";s:11:"description";s:33:"WordPress development and updates";s:7:"pubdate";s:31:"Thu, 06 Nov 2008 09:03:57 +0000";s:9:"generator";s:33:"http://wordpress.org/?v=2.7-beta2";s:8:"language";s:2:"en";s:2:"sy";a:2:{s:12:"updateperiod";s:6:"hourly";s:15:"updatefrequency";s:1:"1";}s:7:"tagline";s:33:"WordPress development and updates";}s:9:"textinput";a:0:{}s:5:"image";a:0:{}s:9:"feed_type";s:3:"RSS";s:12:"feed_version";s:3:"2.0";s:5:"stack";a:0:{}s:9:"inchannel";b:0;s:6:"initem";b:0;s:9:"incontent";b:0;s:11:"intextinput";b:0;s:7:"inimage";b:0;s:13:"current_field";s:0:"";s:17:"current_namespace";b:0;s:19:"_CONTENT_CONSTRUCTS";a:6:{i:0;s:7:"content";i:1;s:7:"summary";i:2;s:4:"info";i:3;s:5:"title";i:4;s:7:"tagline";i:5;s:9:"copyright";}s:13:"last_modified";s:31:"Thu, 06 Nov 2008 09:03:57 GMT
";s:4:"etag";s:36:""30dfb34709931bfe6e44d628a3794fbd"
";}