When NOT to use WordPress

In 2003, Wordpress launched. Ten years later it was used by 22% of the top 10 million websites. It's relatively hard to imagine a scenario of when not to use Wordpress. This talk explores the downsides of Wordpress based on extensive research.

Transcript

1. When NOT to use WordPress “The difficult questions, are the ones we should be asking” - some one smart
2. Leon Shelhamer web: 211j.com twitter: @francismhwhite1 facebook: leon.f.shelhamer github: twoelevenjay instagram: leon.shelhamer 211j.com/wp518
3. Some things I love!
4. Some things I love! • Dogs
5. Some things I love! • Dogs • Scary Movies
6. Some things I love! • Dogs • Scary Movies • Rollercoasters
7. Some things I love! • Dogs • Scary Movies • Rollercoasters • Running
8. Some things I love! • Dogs • Scary Movies • Rollercoasters • Running • Tattoos
9. Some things I love! • Dogs • Scary Movies • Rollercoasters • Running • Tattoos • WordPress
10. Pre - WordPress career
11. How I found WordPress career
12. Post - WordPress career
13. WordPress is so great! When should I NOT use it?
14. The good, the bad, and the unknown
15. Who me?
16. Every problem tends to look like a nail when all you carry is a hammer.
17. Never?
18. What is WordPress?
19. Pros
20. Popular Pros • open source (free)
21. Popular Pros • open source (free) • user friendly
22. Popular Pros • open source (free) • user friendly • large user base (community support)
23. Popular Pros • open source (free) • user friendly • large user base (community support) • very extendable
24. Popular Pros • open source (free) • user friendly • large user base (community support) • very extendable • always improving
25. Popular Pros • open source (free) • user friendly • large user base (community support) • very extendable • always improving • yet extremely backwards compatible
26. Cons
27. Popular Cons • Security vulnerabilities
28. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities
29. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities • Bloated stuff we don’t always need
30. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities • Bloated stuff we don’t always need • Written in PHP (not sure this is a con)
31. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities • Bloated stuff we don’t always need • Written in PHP • Slow
32. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities • Bloated stuff we don’t always need • Written in PHP • Slow • Cookie cutter
33. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities • Bloated stuff we don’t always need • Written in PHP • Slow • Cookie cutter • Easy to make a bad website.
34. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities • Bloated stuff we don’t always need • Written in PHP • Slow • Cookie cutter • Easy to make a bad website. • Database Structure
35. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities • Bloated stuff we don’t always need • Written in PHP • Slow • Cookie cutter • Easy to make a bad website. • Database Structure • “post” focused naming convention lol
36. Popular Cons • Security vulnerabilities • Popular target for exploiting these vulnerabilities • Bloated stuff we don’t always need • Written in PHP • Slow • Cookie cutter • Easy to make a bad website. • Database Structure • “post” focused naming convention lol • spam target
37. I think I know the answer.
38. The good, the bad, and the unknown
39. Leon Shelhamer web: 211j.com twitter: @francismhwhite1 facebook: leon.f.shelhamer github: twoelevenjay instagram: leon.shelhamer 211j.com/wp518