FYI: The Codex & Doc survey is live: http://wordpressdotorg.polldaddy.com/s/documentation-survey
Recent Updates Toggle Comment Threads | Keyboard Shortcuts
-
Siobhan
-
Drew Jaynes (DrewAPicture)
3.6 Master Codex changes list (in progress)
Since we’re revving up for the 3.6 release and a Codex Sprint, this post will serve as our “master changes list” for 3.6. This list is by no means complete, so leave a comment if you feel like something is missing. We’ll update it as we go. If you’ve completed a todo item, let us know and we’ll check it off for you.
Pages
(needed in time for release):
(anytime)
General
Version 3.6
Post Formats
Twenty Thirteen
oEmbeds
Media
Developers
‘needs-codex’ Trac tickets
>> Look for the Trac comment where needs-codex was added for more info
New Functions
Post Formats
Audio / Video
Media
Revisions
General
New Filters
Deprecated Functions
External Libraries
-
Siobhan
The folks at Balsamiq have kindly provided us with a free MyBalsamiq account for the WordPress project. If you want to create mockups let me know and I’ll add you to the account.
-
OC2PS
Super! Is it just for WordPress or can we use it for BuddyPress too?
-
Siobhan
Fine for BuddyPress too, provided it’s for the BuddyPress project and not third-party stuff.
-
-
@mercime
Count me in please for BP/bbP/WP
-
Siobhan
I’ve added @karmatosed to manage the BP side of things. Tammie, feel free to add anyone you like.
-
karmatosed
Will do thanks
-
-
-
-
Siobhan
In search of WordPress users
I am looking for WordPress users to feature in the introduction of the book.
By WordPress users I mean people using WordPress for their website, blog, etc. I don’t mean people using WordPress as a development tool, to build their business – i.e. people who are outside of the community, who are doing something interesting, and who use WordPress. They’re likely your clients, or your family members, or the people you’ve recommended WordPress to. They may know very little about WordPress – that’s not important, it’s the people that matter. Here’s some examples of people that I’d like to speak to:
- small business owners (e.g. picture framers, watch makers, grocers, restauranteurs, butchers, bakers, candlestick makers)
- political activists (particularly anyone who’s blogged from war zones, uprisings, revolutions, or world-significant events)
- non-profits & charities
- bloggers (mummy bloggers, fitness bloggers, cooking bloggers, knitting bloggers, fan blogs, gossip bloggers, etc etc )
- educational institutions (universities, schools, other educational units)
- governments and government agencies
- anyone who does something interesting and uses WordPress
I’m happy to chat with them on Skype or via email. I’ll be asking them what they do day to day, where they do it, and how they use WordPress.
I’m looking for people all over the world. If you know of someone who you think would be a good fit but they don’t speak English, it would be great if you could act as a translator.
Any help the community could give me on this would be massively appreciated. I realise that I rarely interact with WP users outside of the community anymore
. But since many of you have clients, friends, family etc, I was hoping you could point people in my direction.If you know of anyone who would be interested, please ask them to email siobhan at wordpress dot org.
Update: I need to be in touch with people by 27th May.
-
Eric Amundson
When are you needing responses by, Siobhan?
We’re sending an email newsletter to customers (who are largely WordPress users) and we’d be happy to include a solicitation for you.
We were aiming to send next Tuesday, May 14th, but I’ve got a few specific folks in mind that I’ll contact directly (wifey being one – she runs a staffing company site that’s WP-powered).-
Siobhan
Good point. I need to hear back before 27th May. I plan to have all of the interviews completed by Friday 31st May.
-
Eric Amundson
Terrific. I’ll do what I can. Good luck!
-
-
-
OC2PS
I’m a WordPress user. How can I help?
-
Siobhan
Can you drop me an email at siobhan at wordpress dot org with details about how you use WordPress?
-
-
Nuno Castelinho
My company uses WordPress as a CMS for our site, I can get you in touch with our marketing department, they’re the ones that edit the content and use it to promote and inform our customers (I’m a developer
).
send them an email to: relacoes.publicas@metrolisboa.pt and say I send you -
Siobhan
Thanks Nuno – can you drop me an email at siobhan at wordpress dot org with details about how you use WordPress?
-
-
Ana C.
Hi! You can count on us
We manage an hiperlocal news web. Send us your questions.-
Siobhan
Cool! Can you drop me an email at siobhan at wordpress dot org?
-
-
Scott
I made my first WP post in July of 2005 and have made my living with WordPress ever since. We’ve developed and SEO’d hundreds of sites, and released half a dozen plugins over the years… I’d be happy to be included – hit me up any time
@shendison-
Siobhan
Thanks for your interest Scott! For the time being I’m really looking for people who use WordPress as opposed to people running a WordPress-business. I’ll keep you in mind for the future though!
-
-
Cátia Kitahara
Hi Siobhan, I have a client who I think would be a very interesting person to interview. He works in this site: catracalivre.com.br. It’s a calendar of events for free or of low cost. It’s becoming very popular and it’s got between 50 and 100 thowsand visitors everyday. They started very small, but now they are growing very fast. Their project became a study case at Harvard Business School.
-
Siobhan
That’d be great – can you drop me an email with the details of the person?
-
-
Jon
I’m interested in your request. I am a writer for WPdaily and had an article published recently, http://wpdaily.co/15-wp-life/
I am a professional guitarist and use WordPress daily for my students as well as for my business.-
Siobhan
Hi Jon – can you drop me an email with links to your WordPress website and info about how you use WordPress? Email: siobhan at wordpress dot org
-
-
Grant Lewis
Give me a shout, struggling with learning more technically and adding content
-
Siobhan
If you need help with WordPress a great place to look is the WordPress Codex: http://codex.wordpress.org
-
-
omshivaprakash
Hey Slobhan, I have been a proud user of WordPress for years now and I run many sites for Free Knowledge in Kannada (language code: kn). I’m reachable at info at shivu.in
-
Siobhan
Cool! Can you drop me an email at siobhan at wordpress dot org?
-
-
bdthemes
Hi i want to translate Bengali language, i already 50% done in locally there anyway to import it in glotpress? or can i get the admin access to management Bengali language? now it’s not fulfill http://bn.wordpress.org/
-
Siobhan
Please put translation requests on the Polyglots blog: http://make.wordpress.org/polyglots/
-
Siobhan
Documentation Survey
I’m putting together a survey which we can get people to answer about WordPress’ documentation. I’ll get it online later this week, but I thought it would be worth seeing if you guys had any suggestions for questions that you think would be useful. The aim of the survey is to:
- help to create a new architecture of the documentation
- help us to discover pain points
- create a list of priorities for new documentation
Okay, here’s what I’ve come up with so far.
Are you:
1. WordPress user (I use WordPress to run my website/blog)
2. WordPress builder (I build and customize websites but I don’t write PHP)
3. Novice developer (learning to write my first plugins/themes)
4. Intermediate developer (I write plugins and themes and they’re pretty good)
5. Advanced developer (I dream in PHP)
What documentation do you currently use (select all that apply):
1. Codex – guides
2. Codex – API documentation
3. Tutorials and guides on blogs
4. Books
5. Breaking WordPress/plugins/themes and putting them back together
6. Premium services
7. Screencasts
8. PHP docs and inline documentation
9. Forums (like wp.org or stack exchange)
How useful do you find the WordPress Codex:
1-10
What types of documentation/learning do you prefer?
1. Tutorials
2. User Guides
3. Breaking stuff and putting it back together
4. Screencasts
5. Code references and API documentation
6. In-person training
7. PHP docs and inline documentation
What’s the first place you go when you have a question about how something in WordPress works?
Codex
Google
Other: [open]
What do you find most helpful about the Codex:
[open]
What problems do you face with the Codex (check all that apply):
Incomplete documentation
Out of date documentation
I can’t find what I need
Content isn’t clear
Content isn’t accurate
Difficult to navigate
Other:
What would you like to see more of:
Tutorials
Handbooks focused on specific tasks
Screencasts
Better code reference
Better inline help
????
Other:
What improvements to documentation would improve your experience of using or developing with WordPress:
[open field]
Have you ever contributed to the WordPress Codex:
Yes/No
Would you like to contribute to the WordPress Codex:
Yes/No
If you’ve never contributed to the Codex, can you please say why:
[open field]
-
John Saddington
First, since you have developers covered at the top (first section) did you want to include designers, just to get some more demographics? It would be interesting to see the overlap, if anything as designers use the codex too. Perhaps they would call themselves designers + beg/inter/advanced devs?
-
Cátia Kitahara
+1 and as for the documentation I think the phpdocs are missing
-
Kim Parsell
“PHPDocs and reading the source code” would be a good addition to the “What documentation do you currently use” question.
-
Siobhan
Added PHPdocs and source code – thanks!
-
-
-
Siobhan
Designers are covered by 3 – 5 in that list. If a designer is building themes then they are doing some development. I’m more interested in the person’s experience of code than what they do with that code.
-
John Saddington
good point.
-
-
-
Ulrich
For “What documentation do you currently use (select all that apply):”
I think support forums should be added too.-
Siobhan
Added
-
-
Daniel Bachhuber
Thanks @siobhan! A few points of critique:
- When you mention “documentation you use” or “types of documentation”, you might want to link to examples so the respondent knows what you’re talking about.
- Unless you need the data for statistical purposes, 1-10 answer types are generally not that useful.
- I would ask “What’s the first place you go when you have a question about how something in WordPress works?”
I think the survey will work well for identifying pain points and priorities, but I’m not sure how well it will work for creating a new documentation architecture.
-
Siobhan
Thanks for this
- I’ll add links to any that require clarification once I make the survey. Good suggestion.
- The 1-10 answer should give us some sort of idea of how well the Codex is fitting the needs of users of different levels of experience.
- nice question. Added.
Yes, you’re right about it not being particularly useful for creating the new documentation architecture. We’re using analytics to get a sense of what we currently have and to come up with the new architecture. I’m hoping that this survey will help us to prioritize what tasks we tackle first.
-
toscho
I use only two sources for documentation: wordpress.stackexchange.com and the source code. Might be worth to add.
-
Siobhan
added
-
-
esmi
Under “Are you:” (ie WP user type), can I suggest adding something like “WordPress support volunteer (I help out on the support forums regularly)”? Perhaps at position 3? Not all support regulars are PHP coders but their feedback on documentation could be especially useful.
-
Siobhan
I agree that WP support volunteers would have useful feedback, but this survey is to gauge the usefulness of the Codex to WP users of differing skill levels. The first question isn’t intended to identify everyone who uses the Codex, but the level of skill of people who use it.
However, this does make me think that what would be useful is a survey targeted at support forum volunteers on the usefulness of WP documentation. They will look at it from a different angle to users. I had thought a while back about extending a survey like this out to support people at commercial WP businesses to see what areas of WP documentation they are consistently sending customers to, and what areas are lacking.
-
-
rachel_mccollin
I would suggest adding a positive question in addition to the one asking what problems people experience with the Codex. Before asking them that (and putting them in a negative frame of mind), we can ask what they find helpful about the Codex, and list the opposite of those things listed for problems.
-
Siobhan
added that but left it open. Interested to see what people say
-
-
Vid Luther
I’d like to add “Systems Adminstrator” as a clause as well. How to build and configure performant systems should also be part of the Codex. I believe a few months ago, there was a call to adopt a part of the Codex, we’ve been thinking of adopting the Nginx side.
-
Siobhan
A Systems Admin handbook is definitely on my radar. I’ve been looking at the stats and current architecture and we do have an Nginx page which receives about 9,000 hits a month. I’d love to get in touch with you once we’re ready to move on that side of things to see if you guys have time to help out with it.
-
-
Eric Amundson
Yes, thanks @siobhan!
I agree with Daniel about the need for examples in the “What documentation do you currently use” section, especially point numbers 5 & 6. In fact, #5 really doesn’t seem like a form of documentation; more a style of learning. Usually when I break stuff, I end up referring to WP documentation to fix.
Maybe a bit picky, but under “What types of documentation/learning do you prefer?,” I’d clarify #1 to say something like “Written Tutorials” because there are tons of sites that provide lots of video tutorials. I understand the difference, but it could help clarify for someone for whom English is a second language.
If you were to add that, you might consider adding “(video)” after Screencasts, or list it as “Screencasts/Videos.”
Drew Jaynes (DrewAPicture)
Revisions help tab
Yesterday in DevChat, @ocean90 requested we write a help tab for the new revisions screen. I’ve uploaded a first-run patch and am looking for feedback and revisions (ha) on that text.
I’d just like to note that I think we can be succinct about this without leaving out important information.
The ticket and patch are on the #23899 ticket.
The following is the first-run text:
Tab: Overview:
This screen is used for managing your content revisions.
Revisions are saved copies of your post or page, which are periodically created as you update your content. Text highlighted in red shows what content was removed, highlighted in green shows what content was added.
From this screen you can review, compare, and restore revisions:
- To navigate between revisions, drag the slider arrow left or right or use the Previous or Next buttons.
- Compare two different revisions by selecting the ‘Compare two revisions’ box to the side.
- To restore a revision, click the Restore This Revision button.
Tab Sidebar:
For more information:
Side note: The Revisions Management page is slated for pre-sprint release, in other words, it’ll be done in time for the 3.6 release so forum folks have something to reference.
-
esmi
Text highlighted in red shows what content was removed, highlighted in green shows what content was added.
Shouldn’t there be an extra “text” in the second half of the sentence?
Can I suggest that we avoid using terms like “red” and “green” as the sole descriptions? Maybe use something like:
Text on the left (highlighted in red) shows what content was removed, text on the right (highlighted in green) shows what content was added.
-
Siobhan
Some changes (incorporating Esmi’s suggestions too:
Tab: Overview:
This screen is used for managing your content revisions.
Revisions are saved copies of your post or page, which are periodically created as you update your content. The red text on the left shows the content that was removed. The green text on the right shows the content that was added.
From this screen you can review, compare, and restore revisions:
- To navigate between revisions, drag the slider arrow left or right or use the Previous or Next buttons.
- To compare two revisions select the Compare two revisions box.
- To restore a revision, click the Restore This Revision button.
Tab Sidebar:
For more information:
Revisions Management
Support Forums
-
Siobhan
I got an email from Gary Jones about the CSS property ordering in the Core Contributor Handbooks. He says:
Currently the CCH says the CSS properties should be grouped as:
- Display
- Positioning
- Box model
- Colors and Typography
- Other
I don’t think this is prescriptive enough, and it’s certainly not easy for core contributors (or theme / plugin developers who also follow the WP standards) to go along through each property and decide which category it fits in to before having to manually move lines up and down.
As part of the Genesis 2.0 CSS reorganisation, I came across http://csscomb.com – it’s available as a plugin for most of the popular editors, but also as an online tool as well. It already comes with tests, but I also did some with multiple properties in a rule (i.e. padding using rem, then px fallback) and mis-ordered browser-prefixed properties, and it sorted them perfectly. It also keeps any whitespace between the : and value, to keep browser-prefixed values lines up, as per the CCH.
If you head to the online tool, then click on Settings, you’ll see it pops-out with a comprehensive list of CSS properties, including ones for CSS3 and prefixed properties, which WP might not have made a decision about if they don’t use them.
I think this tool can be used in one of two ways:
1) Amend the CCH so that Display comes after Positioning, so it then matches the CSScomb defaults and can be easily used by anyone online or in their editor without further set up, making it easy to automate the property ordering process.
or
2) Take the list of properties, and update it to reflect the order that WP prefers, and make this available as a list (Gist) that can be copied back into the online settings, and as an equivalent file for use in editors (Sublime Text 2 uses a JSON file), including a list of instructions for both.
Being more descriptive, by having someone else keep track of the full list of properties (including CSS4, CSS5 properties etc.), and having a tool that is available for those with and without compatible editors, means that the process can be automated, and a chunk of potential human error is removed.
I’d love to hear what the docs / CS folks have to say about it using this tool. Being able to open a .css file, select all, then hitting a keyboard shortcut to have it automagically match the WP standards has got to be worth investigating?
What do you guys think? Is this something we want to look into?
Gary Jones, and 1 other are discussing. -
Jason Hoffmann
I think that directing people to this tool is a great idea for beginners who are just getting into CSS and want to make sure that their code is neatly organized. I also think it would be bit silly to amend the rules, attach that to a gist, and a bunch of steps for people to even use the tool. It would be much much easier, and to my mind preferable, to amend the CCH to place display after positioning.
The order of CSS Properties is mostly a matter of taste, and does not effect specificity or the cascade so there are no functional drawbacks.
For those that are seasoned front-end devs, they will have their own way of organizing properties and a tool like CSS comb may not be necessary to them. If it is, they will have the knowhow to tailor it to their needs. Beginners, on the other hand, should have access to a tool that is simple to use without extra steps.
-
Gary Jones
For simplicity, suggestion 1 would be my favourite as well, for the reasons you’ve suggested (too many extra steps), but I wanted both options to be considered (the implicit third option is that the tool isn’t recommended, and beginners are left to fend for themselves). It then comes down to whose (collective?) taste decided on the order currently in the CCH in the first place, and whether they’re happy to have it amended to make using this tool so much easier.
Thanks for your feedback Jason
-
Kim Parsell
Gary, to my knowledge, Helen Hou-Sandi worked on the final CSS standards, and moved them from the Codex to the handbook. She should be able to shed some light on why the properties are ordered that way in the coding standards.
I have to agree with Jason’s suggestion as well (amend the CCH). You might talk to Helen about your other ideas, see what she thinks. There is a Related Links section (http://make.wordpress.org/core/handbook/coding-standards/css/#related-links) where this information could be included.
-
-
-
Eric Amundson
+1 for amending the CCH to place display after positioning; much easier all around.
Siobhan
Outline for WordPress Book!
Below is the outline of the WordPress biography that I’m working on! I’m hijacking the docs blog for this sits it’s sort of documentation. This is something I’ve been researching over the past few months, and am quite far along with the very early sections. We thought it would be a good idea to share it with the community to see if there are any glaring omissions, so if you’re interested in providing some feedback, read on!
Some things to note:
- this is a rough outline of the shape of the book.
- the people listed under “Key People” are not the only people who are relevant. They are those who have been or will be interviewed for that section of the book. There are people who are relevant to many of the sections (Mark Jaquith, Jen, Westi, to name just a few). See my other post on my interview list. Here is a full list of people on my radar to be interviewed so far.
Things to provide feedback on:
- are there any significant areas of WordPress that you feel are missing. Remember that we’re interested in things that had an impact on WordPress and the community, not when you set up your personal site.
- are there any people that I might not have thought of who are relevant to a specific section? Do you have something to say? Do you want to be included? Let me know.
Okay, here it is!
Introduction
Where WordPress is today.
Featuring WordPress users all over the world to create a snapshot of WordPress use 10 years after it was first launched.
Key people: WordPress users
Part 1: The Blogging Software Dilemma
This section deals with the very early days of WordPress, the state of blogging, b2 development, and the forking of b2.
Chapter 1
On the state of blogging in 2002, the founders of WordPress, and why they decided to get online.
This chapter will contain biographical information about the founders of WordPress – Matt Mullenweg and Mike Little. It will look at why they decided to set up their own blogs, and how they got into web development. The chapter will also contextualise blogging in 2002-2003. It will look at how blogging came about and evolved, and where it was in 2002.
Key people: Matt Mullenweg, Mike Little
Key Resources: ma.tt, zed1.com/journalized
Rebecca Blood: http://www.rebeccablood.net/essays/weblog_history.html
Steve Rosenburg: http://www.amazon.co.uk/Say-Everything-Blogging-Becoming-Matters/
Chapter 2
On the development of b2.
This chapter opens with Michel Valdrighi in Corsica in 2000. It looks at his experience of software development, why he wanted to develop his own blogging tool, and why he chose PHP/MySQL. It will cover the vision he had for it, the early functionality that went into the software, and the growth of the b2 community. It will look at why Michel ceased development on the software and the effect that this had on the community.
Key people: Michel Valdrighi
Key Resources: b2 forums on tikadada.com (possibly lost), zengun.org
Chapter 3
On forking WordPress, forks in general, early WordPress and the community
This chapter opens with Matt’s original post on “The Blogging Software” dilemma, and Mike’s comment about forking it. It looks at what it means to fork an open source project and the history of forks. It looks at why Matt decided to fork b2 and turn it into WordPress. This is followed by the early development of WordPress and the functionality that went into it. It will cover the development process and how decisions are made. It will also look at the growth of the WordPress community, and the significant changes made to WordPress during the first year (including the plugin system).
Key people: Matt Mullenweg, Mike Little, Alex King, Dougal Campbell, Ryan Boren, Christine Selleck, Craig Hartel + any other very early community members
Key resources: WP.org blog, ma.tt, WP.org support forums, early IRC logs (pending), early mailing lists (possibly lost)
Part 2: Freedom 0
This section covers WordPress’s license, the GPL, how it has affected WordPress and impacted its growth.
Chapter 4
On the GPL
This chapter will cover the history and background of the GPL. It will look at why Richard Stallman created the license, what it means, and why its is important to many software developers. It will look at how the GPL became the license used by WordPress and what that means for developers and users.
Key resources: Free Software Foundation, Richard Stallman: Free Software, Free Society, the GPL license, cafelog.com
Chapter 5
On the Movable Type Licensing Change
In May 2004, Movable Type changed their license. This precipitated a huge influx of people moving to WordPress. The writer, Mark Pilgrim, wrote an influential post that spurred people to move. This chapter will look at the effects of that licensing change, notable people who made the move to WordPress, the increase in WordPress users, and the effect that this had on the WordPress community.
Key People: Anil Dash, Mena Trott, Mark Pilgrim, Om Malik, Carthik Sharma, Panjak Kumar + other community members who helped people to move their sites.
Chapter 6
On the ways that the GPL continues to shape and effect the WordPress community
The GPL continues to affect the WordPress community. This will look at instances when discussions around the GPL have caused shifts in the community. It will look at how the discussion around GPL themes influenced the growing theme marketplace. It will look at the distinction between WordPress’s official stance on the GPL and the GPL followed to the letter of the law.
Key people: Matt Mullenweg, Chris Pearson, Brian Gardner + others (?)
Part 3: WordPress, Inc
This section will look at the difficulties around supporting open source software and commercialising it.
Chapter 7
On initial attempts to make money to support the growing project
The focus of this chapter will be early attempts to make money to support the WordPress project. It will explore the difficulties of supporting an independent open source project that isn’t intended as a commercial project. It will look at the circumstances around the search engine spam that appeared on WordPress.org. It will look at the announcement about WordPress Inc that was made at the 100K party.
Key people: Matt Mullenweg, Jonas Luster, Toni Schneider
Chapter 8
On Automattic
This chapter will look at the setting up of Automattic, early employees and investments that were made in the company. It will look at the ethos behind Automattic and how that works alongside the WordPress project. It will ask how a company can be commercially viable within an open source context. It will look at how WordPress.com and Automattic’s other services have effected WordPress’s growth.
Key people: Matt Mullenweg, Toni Schneider, Om Malik, Phil Black, Mike Hirschland
Chapter 9
On commercial themes
This chapter will look at the introduction of the theming system into WordPress and how this changes the user’s experience. It will look at the emergence of the commercial theme market. It will look at the founding of the major theme shops and the issues that they faced. It will look at the relationship, tensions, and synergies between the open source project and commercial businesses.
Key people: Brian Gardner, Adii Pienaar, Justin Tadlock, Ian Stewart, Cory Miller, Collis Ta’eed, other ppl running WP Theme Shops
Chapter 10
On the wider commercialisation of WordPress and the effects on the community
This chapter will look at the growth of the commercial economy around WordPress. It will look at how businesses can make money by building their businesses on top of free software. As the commercial theme market has become saturated, it will look at how other businesses emerged, how they evolved, and the effect that this had on the community.
Key people: Cory Miller, Lisa Sabin-Wilson, Ben Metcalfe, Alex King (other WP business folks)
Part 4: The next ten years
(better title needed – want to find a suitable blog post title)
This section will look at the challenges that WordPress faces in the coming ten years.
Chapter 11
On going mobile
This chapter will look at the growth of mobile technology and its effect on WordPress. It will look at how mobile technology has changed how people interact with the web, in terms of both browsing and creating content. It will look at how WordPress development has had to adapt and change to meet these needs. It will look at how WordPress plans to adapt further in the future.
Key people: Isaac Keyet, anyone on the mobile dev team, Matt Mullenweg
Chapter 12
On the “third phase of WordPress” – as an application framework
This chapter will look at current moves in WordPress to start using the platform as an application framework. It will look at some of the early developers and businesses who are using WordPress in this way. It will look at how community members are starting to push WordPress in new and different directions, and what this might mean for the future.
Key people: Noel Tock, Brad Williams – other application framework folks.
Conclusion
End stuff
- Appendices
- Glossary
- Biographies
-
valentmustamin
awesome project!
-
Jason Hoffmann
This is so awesome that you’re doing this.
You’ve managed to organize everything really well. To my mind, the only thing that is missing is some discussion in Part 1 of WordPress’s involvement with web standards. It was a standards compliant product from day one, and it was the reason that a lot of people (myself included) go out of Flash/table layouts and into standards. It was an important step forward for that movement. I’m sure this can be bundled into Chapter 3, but I would think it’s worth mentioning.
-
Siobhan
standards compliance is covered in chapter 3
-
-
Cátia Kitahara
Great job, Siobhan! Very good! As part of the international community, there’s a thing I missed: something dedicated to the internationalization process, like what was the first localized version and when. I guess it would go into the Part 1/Chapter 3. Also, maybe something about WordCamps and meetups history?
-
Siobhan
As you say, early internationalisation will be covered in C3. The first one seems to be in Hindi in May 2004: http://ma.tt/2004/05/wordpress-in-hindi/
Not sure how WordCamps and meetups will figure. They’ll appear in there somewhere, but i don’t think they’ll have a dedicated section.
-
Naoko Takano
I think that Hindi site refers to front-end translation. A couple of references…
http://weblogtoolscollection.com/archives/2009/06/21/matt-mullenweg-wordpress-community-interview/
http://wordpress.org/support/topic/localization-help-needed?replies=102 (18 Dec 2005)
Unfortunately Otsukare who created the first Japanese l10n version is no longer active in the community (I haven’t talked to him for 5 years) but the forum thread should answer some of your questions.-
Siobhan
Thanks Naoko – I’ve gotten in touch with the developer of the Hindi site to see if it’s a front-end translation or not. Will report back!
-
-
-
-
Austin Gunter (@austingunter)
Siobhan, this is fantastic. I’m really glad to see you doing this. If I can be of any help, please let me know.
-
Siobhan
Thanks Austin
Looking forward to seeing how it goes!
-
-
andrea_r
No mention of what was wpmu and merging that in?
-
Siobhan
WPMU is covered along with b2++. I’m waiting to talk to Donncha before deciding how to weave it in further.
-
-
@mercime
What a fun huge project! Can help with grunt work if needed, just ping
+1 on WPMU – Awesome work led by Donncha with friendly support from andrea_r, dsader, drmike and many more way back then
-
Siobhan
Cool! Will definitely let you know if I need help. The WPMU stuff is definitely on my radar, it’s just a matter of tying the technical side together with the wider narrative. It’s definitely a challenge!
-
-
Ian Stewart
Fantastic outline. I’m especially looking forward to reading the early history of B2 and WordPress. Seeing it all presented in one canonical place will be awesome. Not too sure about chapter 9 though. One of the people in your list is looks pretty sketchy.
-
Siobhan
There is one guy that’s super-sketchy. I wanted to avoid speaking to him but he ran some little blog called theme shaper so I guess I’d better talk to him :p
-
-
Paul
I can help translate it to French when it’s finished
-
Siobhan
I would love that. It would be great to have translations
-
swissspidy
I’m in for a German translation!
-
-
brasofilo
Suggestions to “The next ten years”:
- What’s next?
- The road(s) ahead
- And now what?
Jen Mylo
Gnome Outreach Program for Women
Hi all. I talked to Siobhan about including Documentation in our Gnome participation this summer. @siobhan: Head over to http://codex.wordpress.org/Gnome_Summer_Program_for_Women#Documentation and fill in project ideas and info on whoever from this team is willing/able to mentor an intern (ideally we put more than one mentor with each student). No idea yet how many student slots we’ll get. Feel free to edit the Documentation section as you see fit.
-
Siobhan
Thanks for this. I’ll ask for suggestions at the chat tonight and get some things added.
Siobhan
WPHistory: List of Interviewees
My list of people who have been/will be interviewed, and those that have been contacted. Some things to note:
- Mainly includes only people who were involved prior to 2006 (because that’s where I am)
- If you’re not on the list, and you want to be, leave a comment.
- If you notice someone missing, leave a comment
Developers
Interviewed
Matt Mullenweg
Dougal Campbell
Mike Little
Alex King
Scheduled
Ryan Boren
Contacted
Donncha O Caoimh
Michel Valdrighi
Jason Verber
Mike Tremoulet
To Contact
Mark Jaquith
Owen Winkler
Peter Westwood
Andrew Nacin
Community
Interviewed
Jayvie Canono
Craig Hartel
Carthik Sharma
Lorelle van Vossen
Michael Adams
Scheduled
Mark Ghosh
Cena Mayo (by email)
Contacted
Michael Heilemann
TechGnome
Christine Tremoulet
Michael Renzmann
Christoph Wimmer
Mark Riley
Scott Merril
Kaf Oseo
Kimmo Suominen
Nikolay Bachiyski
Michael H
To Contact
Joseph Scott
Scott Reilly
Hanni Ross
Kyle Neath
Michael Dale
James Huff
Matt Thomas
Otto
Mika Epstein
Jen Mylo
Andrea Rennick
Others
Contacted
Om Malik
Kathe Mullenweg
To Contact
Eric Meyer
Jonas Luster
Dean Allen
Anil Dash
Mena Trott
Phil Black
Mike Hirshland
John Saddington 11:59 pm on May 17, 2013 Permalink |
awesome!