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.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s