So You Want to Launch a Plugin/Theme?

An updated version of my WordCamp Buffalo 2013 talk.

Transcript

1. Hi!
2. chrisvanpatten.com
3. @ChrisVanPatten
4. vanpattenmedia.com
5. github.com/vanpattenmedia/
6. cvp.me/wordsesh2013
7. SO YOU WANT TO WRITE A
   PLUGIN
8. SO YOU WANT TO WRITE A
   THEME
9. Awesome!
10. So... I just start coding, right?
11. So... I just start coding, right? WRONG
12. Step back. Breathe.
    We’ll get through this together.
13. (1)
    Make sure you’re not doing work
    that someone else already did.
14. (1)
    Make sure you’re not doing work
    that someone else already did.
15. 2,000+ themes on .org
16. 5,000 themes on theme marketplaces
17. 28,000+ plugins on .org
18. (2)
    Have a business model (or not).
19. (2)
    Have a business model (or not).
20. Free vs. Paid
21. Freemium vs. Premium
22. Distribution
23. (3)
    Choose a license. Carefully.
24. (3)
    Choose a license. Carefully.
25. (3)
    Choose a license. Carefully.
26. I am not a lawyer.
27. Code must be GPLv2 compatible
28. MIT. Apache 2.0. Public Domain.
    ! ✓
29. MIT. Apache 2.0. Public Domain.
    ! ✓
30. Creative Commons.
    ! ✗
31. Creative Commons.
    ! ✗
32. What about non-code assets?
33. It’s complicated.
34. Other theme directories? It depends.
35. WordPress.org? Yes.
36. If you can, you should.
37. Good for the community
38. Good for the soul
39. People are good.
40. (4)
    Understand best practices.
41. (4)
    Understand best practices.
42. Theme Review
43. Theme Unit Testing
44. Theme-Check
45. Plugin Review
46. (5)
    Document
47. (5)
    Build it.
48. (6)
    Submit it.
49. (6)
    Submit it.
50. Readme.txt
51. Plugin vs. theme readmes
52. Plugin Banners
53. Screenshots
54. FAQs
55. SVN
56. (7)
    Support it.
57. (7)
    Support it.
58. Thank you!
59. cvp.me/wordsesh2013