Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Building Themes and Plugins: Everything But Code

Building Themes and Plugins: Everything But Code

Developing themes and plugins is a common topic in the WordPress community, but the non-technical aspects are usually glossed over. In fact, many of these non-technical elements are more important than the code itself. In this talk, you’ll learn about software licenses, support strategies, and theme/plugin monetization, as well as tips and tricks for making your users happy.

Chris Van Patten

September 14, 2013
Tweet

More Decks by Chris Van Patten

Other Decks in Technology

Transcript

  1. Hi!

    View Slide

  2. Me.

    View Slide

  3. chrisvanpatten.com

    View Slide

  4. @ChrisVanPatten

    View Slide

  5. vanpattenmedia.com

    View Slide

  6. profiles.wordpress.org/vanpattenmedia/

    View Slide

  7. cvp.me/wcbuf2013

    View Slide

  8. SO YOU WANT TO WRITE A
    PLUGIN

    View Slide

  9. SO YOU WANT TO WRITE A
    THEME

    View Slide

  10. Awesome!

    View Slide

  11. So... I just start coding, right?

    View Slide

  12. So... I just start coding, right?
    WRONG

    View Slide

  13. Step back. Breathe.
    We’ll get through this together.

    View Slide

  14. (1)
    Make sure you’re not doing work
    that someone else already did.

    View Slide

  15. (1)
    Make sure you’re not doing work
    that someone else already did.

    View Slide

  16. 2,000 themes on .org

    View Slide

  17. 5,000 themes on theme marketplaces

    View Slide

  18. 27,000 plugins on .org

    View Slide

  19. (2)
    Have a business model (or not).

    View Slide

  20. (2)
    Have a business model (or not).

    View Slide

  21. Free vs. Paid

    View Slide

  22. Distribution

    View Slide

  23. (3)
    Choose a license. Carefully.

    View Slide

  24. (3)
    Choose a license. Carefully.

    View Slide

  25. (3)
    Choose a license. Carefully.

    View Slide

  26. I am not a lawyer.

    View Slide

  27. Code must be GPLv2 compatible

    View Slide

  28. MIT. Apache 2.0. Public Domain.

    View Slide

  29. MIT. Apache 2.0. Public Domain.

    View Slide

  30. Creative Commons.

    View Slide

  31. Creative Commons.

    View Slide

  32. What about non-code assets?

    View Slide

  33. It’s complicated.

    View Slide

  34. Other theme directories? It depends.

    View Slide

  35. WordPress.org? Yes.

    View Slide

  36. If you can, you should.

    View Slide

  37. Good for the community

    View Slide

  38. Good for the soul

    View Slide

  39. People are good.

    View Slide

  40. (4)
    Understand best practices.

    View Slide

  41. (4)
    Understand best practices.

    View Slide

  42. Theme Review

    View Slide

  43. Theme Unit Testing

    View Slide

  44. Theme-Check

    View Slide

  45. Plugin Review

    View Slide

  46. (5)
    Document

    View Slide

  47. (5)
    Build it.

    View Slide

  48. (6)
    Submit it.

    View Slide

  49. (6)
    Submit it.

    View Slide

  50. Readme.txt

    View Slide

  51. Plugin vs. theme readmes

    View Slide

  52. Plugin Banners

    View Slide

  53. Screenshots

    View Slide

  54. FAQs

    View Slide

  55. SVN

    View Slide

  56. (7)
    Support it.

    View Slide

  57. (7)
    Support it.

    View Slide

  58. Plugin Forums

    View Slide

  59. Custom Support

    View Slide

  60. Paid Support

    View Slide

  61. (8)
    Maintain it.

    View Slide

  62. (8)
    Maintain it.

    View Slide

  63. Thank you!

    View Slide

  64. cvp.me/wcbuf2013

    View Slide