In reply to Justin Tadlock.

Ummmm....

I hope the WP.Core realizes that one of the BIGGEST reasons that Wordpress got a significant leg up on Jooml'r is documentation. I cannot BEGIN to tell you how many Jooml'r developers "jumped ship" because the people writing code were not documenting and I dont mean PHPDoc. In industry its pretty much mandatory.

I'd got in a significant blowout with J!.Core abut this. I am a experienced programmer, 35+ years of it. Many (many) folks in their forums were asking about documentation months and months after J! MVC came to be. Mostly they heard silence back. We were doing some work, asked about some documentation. They then turned around and asked me if I wanted to document their code. I went, "Uhhh... Are you guys serious?" and they were.

Imagine working at Microsoft and not documenting work. Visual studio function is METICULOUSLY documented. This is PART of writing software when other developers are to use it. Imagine if PHP were not documented or mySQL or Apache or Linux. This is simply not optional stuff. I dont like it any more than any other software engineer. I prefer to be writing code and not documenting my work. But, thats not optional.

Standards. Hmmm...

So, we want standardization of theme's using Customizer but the folks that author it dont do their standard work in creating it? I would HIGHLY encourage WP.Core to let any developers know that are working on WP.Core function that they simply MUST document their work or they MUST have someone in place as they produce production code to do so or it wont become production code.

I mean really... Adobe never documented Flash? Acrobat? Google never documented Android? Or Apples iOS? This is part of writing code. Its not just PHPDOC'n parameters in /output out and brief function. Its not fun but its the deal.

Imagine people using DOVY's framework and him saying, "Well... I wrote it but I expect all of you using it to document it". I mean, what are we saying here, a guy that makes a theme framework is being more responsible than those making the application functions?

While I appreciate the fact a new customizer documentation is now in place thats due to "chineese fire drill" apparently. "How can developers port themes into customizer if they have no good documentation, so we better make that happen".

Uhhh... maybe theme developers would not have had any of this happen at all or the TMT be deluged with themes not using customizer if proper documentation were in place from word go.

If WP wants secure plugins, secure themes, best practices, all these things to be a reality then documentation is how that occurs and the responsibility to product it is the programmers. Thats basic college software engineering.

Lets go to Microsoft or eBay or Adobe or Google and say, "I want a programmers job. I am a good programmer. But, I dont do documentation".

I could be the best programmer on the planet and I'd be shown the door.