In: , , , ,
On: 2010 / 09 / 14
Shorter URL for this post:

… where "making an UI" means coding the plugin option page, making it understandable, carefully pick some wording, don't overwhelm with unneeded explanations but make sure everything is crystal clear, throw a bit of jQuery to make the page more functional.

… and sometimes I'm a bit fed up with this pattern. Note that it's probably because I lack UI design skills.

NB: If you found this post title to be deceivingly catchy and overselling, you're right.

Shorter URL

Want to share or tweet this post? Please use this short URL:


This entry "Infographics: The Process To Make WordPress Plugins" was posted on 14/09/2010 at 4:30 pm and is tagged with , , , ,
Watch this discussion : Comments RSS 2.0.

4 Blablas

  1. You forgot the big chunk of coding that should be labled "Error Checking". This is usually a significant percentage. Though, some of that can overlap into UI, as well.

  2. Jeff Starr says:

    So true about the i18n – I'm so guilty of this ;)

  3. Ozh says:

    Jeff Starr » Heh :) Personally I skip the i18n step because that would add another 60% of boredom to the process :Þ

  4. Otto says:

    I generally spend about 80% on coding and debugging. Since I learned the Settings API and going for the "attempt to have no options" approach, I find I save a ton of time there.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>
Gravatars: Curious about the little images next to each commenter's name ? Go to Gravatar and sign for a free account
Spam: Various spam plugins may be activated. I'll put pins in a Voodoo doll if you spam me.

Read more ?