Hi all I’ve made a list of all…

Hi all!

I’ve made a list of all of the things in the codex that I think need to be updated for WordPress 3.5: https://make.wordpress.org/docs/2012/11/27/if-all-goes-to-plan-wordpress-3-5-will/

It’s in progress so please feel free to add to it.

But what’s most relevant, is that some of the updates will be relevant to the user manual too. We’re already aware of the updates to media, but there have been a number of changes to the Settings as well. I’m not sure if they were considered when we created the manual.


3.5 Master List Post

What follows this is the boilerplate I use for the ZOMG! WordPress Upgrades Broke me!

What I’d like is if you guys can think up quirks with 3.5 (plugins and themes you know won’t work, or have to be handled special) or other massive changes, that we collect them all here. Then I’ll craft the ‘final’ release.

Continue reading

No Meetup Tomorrow

If everyone wants to meet and hang out, they can, but the US folks (hi) will be off eating turkey. 😀

For next week, since 3.5 RC should be coming out soon, everyone should think about putting the RCs on their site and helping us test 😉 After all, you’re support! You gotta know what’s coming. Also I’ll be putting up the OMGWTFBBQ! post for review, and suggestions, early next week, and I’d love it if everyone came up with a list of weird things in 3.5.

Oh and don’t forget to update your plugin readmes with ‘compatible up to…’ if they are.

Per discussions at the community summit Documentation is…

Per discussions at the community summit, Documentation is now a separate official contributor group. @raggedrobins will be the acting team rep. Have at it, folks!


#documentation, #teams

3.5 Help Text Needs Our Help!

From @drewapicture:

Hi folks,

It’s that time of the cycle again to audit the Help text. The trac ticket for 3.5 is here: #22451 – https://core.trac.wordpress.org/ticket/22451

I’ve already combed through every single-site Dashboard page and submitted grouped patches last week. But now I need your help! If anybody is willing and able to go through and review some or all of them, I’d be grateful for the collaboration and extra eyes.

So please, hop in and while you’re at it, start thinking about what goes weird in 3.5 🙂 More on that later!

Handbooks: Teams and Templates

Over the past few weeks I’ve been getting in touch with people who I’d like to see involved with the handbooks. I’m going to continue to do this over the next few weeks as we get started on working. I just wanted to give you an update on teams and templates.


Here’s who we’ve got so far:

[update: am adding more people to teams as they contact me]


Daniel Bachuber
Japh Thomson

Andrea Rennick
Scott Basgaard
Christine Rondeau
Dean Robinson
Phil Erb
Mika Epstein

Plugin Dev
Pippin Williamson
Dougal Campbell
Tom McFarlin
Thomas Griffin
Maor Chasen
Justin Sainton

Theme Dev
Chris Reynolds
Tammie Lister
Rachel Baker
Jay Hoffman

Theme Review
(no one so far 🙁 )


Brandon Dove
Ryan Imel
Aaron Jorbin
Sara Rosso

(no one so far 🙁 ) Except Isaac?
Abhishek Ghosh


Zé Fontainhas


Andrea Rennick
Christine Rondeau
Dean Robinson

These things span all of the handbooks:

General help

Kari Leigh Marucchi
Abbie Sanderson

Shane Pearlman
@helenyhou or other person from UI
Mel Choyce


We definitely need more people so if you know of anyone please send them this post. Or drop me an email: siobhan at wordsforwp dot com and I’ll get in touch with them personally.


After having chats with different people in different contributor groups and reviewing the material that we have already, I’ve come up with a very loose schema that I think will work across the handbooks.


All of the things you need to start contributing to this area

Useful tools to get started

The different ways that you can get involved in this area

Tutorials & Guides
Practical guides to doing what you need to do

Glossaries etc (maybe useful email addresses etc?)

Best Practice
Coding Standards, Best Practices, UI Guidelines, UX Guidelines, Accessibility

Lists the contributors to that manual.

This is a starting point, so please do make suggestions based on your own experience. There’s always a danger when you’re creating something generic that you lose the specific, which is why I’ve tried to keep the schema as loose as possible.

Some other things

I have a chat with Brad and Pippin about the plugin development handbook. They had some great ideas to keep in mind:

  1. We should use practical examples of code that will help people to learn
  2. We need a syntax highlighter of some description. We did discuss using Gists but then our docs are reliant on Github and that not something we want

I think there may have been other things so Brad and Pippin if I’ve forgotten something please chime in. Soon we’ll get into discussions about the particularities of specific handbooks I’m sure, but I wanted to note these here for the record

Next Steps?

Next steps are as follows:

  1. Come up with schedule and workflow – I’ve got some stuff written down on this but will save for another post! Let’s aim for long term – we don’t want to burn ourselves out.
  2. Schedule some google hangouts with contributor groups and volunteers to discuss best practices
  3. Develop table of contents

Okay, phew! That was a long post again. Let me know if I’ve missed anything, please do add any suggestions or tell me where things can be improved.

Most importantly, spread the word. This is an exciting project in its beginning stages and over the next year we’ll be able to create something we’re genuinely proud of and that gets more people contributing to WordPress.

Is your Forum ID a company rep account?

When you use the forums, are you doing so as your company?

Let me know your forum ID and I’ll make your Title “Company Rep.” (or anything else officialish you want). This way folks in the forums can see you’re legit 🙂 And yes, I’ll check on you guys first 😉

Meetup Recap – Nov 15

Apparently DST is hard for more than me!

Thursdays, 2100 UTC, location #wordpress-sfd

  • 9pm London
  • 4pm US Eastern
  • 1pm US Pacific
  • 2:30am (Friday) Bangalore

Items of note?

https://make.wordpress.org/training is live!

That’s kinda all we have this week. It’s a status quo, however since 3.5 is getting near, I’m going to draft my OMGWTFBBQ forum post here later this week or next week, so we can all write it 😀

Cross posting this link cause people asked Wanna…

Cross posting this link, cause people asked.

Wanna help with videos?


Codex chat

During our regular meeting in IRC we discussed some changes to the codex, based on the roundtable discussion at the WordPress Community Summit.

Before we started ripping things apart, I thought it would be good to look at some stats, if possible, and also to get community input. Because it’s one thing to come up with a good idea, but it’s another to make sure that’s what is needed based on numbers and user feedback.

So this is basically our gut check. 😉

To that end, here are the top 40 visited Codex pages in the last month or so:


And for perspective, the top page (function reference) got over 1.9 million hits, while the second page was hit only 280,000 times.

To me this backs up our earlier conclusion of a divide between users and devs and where they go and what they look for. So the user handbook will likely be well received. Ipstenu made us a shortcode for the Codex so we can start marking pages that will considered for removal and send users to the user manual instead.

The other thing we talked about, before we go too far, is to create a poll to get feedback on codex reorganization.

Some suggested poll items:

  • I like the codex just as it is, it need some love!
  • separate user docs from dev docs
  • something else

Your suggestions for poll options are welcome! Without it turning into an actual poll here… 😉

#chat, #codex