What, Why, How

I’m thinking the #WordPress Codex and Theme Review guidelines would benefit from a “what, why, how” approach to documentation:

  • What: describes the function or requirement
  • Why: why is it this way? Best practice, performance, security concerns?
  • How: a simple and clear code example of how to use or implement what is being discussed

Published by

Kirk Wight

I am a WordPress developer working at Automattic (the makers of WordPress.com). Based in Vancouver, BC, Canada, I am easily distracted and very curious.