It Doesn't Have to Hurt: Bringing Modern Dev Best Practises to WordPress

It Doesn't Have to Hurt: Bringing Modern Dev Best Practises to WordPress

38bc9be7f4f140d1f719c1faeed29a6c?s=128

Chris Van Patten

May 27, 2017
Tweet

Transcript

  1. IT DOESN’T HAVE TO HURT (Bringing modern dev best practises

    to WordPress)
  2. CVP.ME/WCHFX2017

  3. None
  4. WHAT’S THE PROBLEM?

  5. SLOWER WORK

  6. LESS PRODUCTIVITY

  7. HARDER TO ATTRACT TALENTED DEVELOPERS

  8. MORE PRACTICALLY…

  9. VERSION CONTROL

  10. DEPENDENCY MANAGEMENT

  11. THEMING

  12. CREDENTIAL MANAGEMENT AND WP-CONFIG

  13. WORKFLOW

  14. GREAT! LET’S TALK SOLUTIONS.

  15. PROJECT STRUCTURE

  16. DEFAULT

  17. #GOALS

  18. None
  19. HTTPS://DOMAIN.COM /WP/ WP-ADMIN/

  20. COMPOSER

  21. None
  22. None
  23. None
  24. None
  25. None
  26. None
  27. None
  28. TIMBER

  29. None
  30. None
  31. None
  32. #GOALS (WITH TIMBER)

  33. CREDENTIAL MANAGEMENT

  34. YAML, JSON, DOTENV

  35. None
  36. None
  37. STARTER REPO

  38. BONUS LEVEL

  39. None