I wanna be a WP dev

First steps to become a WordPress developer.

Transcript

1. I wanna be a WP dev
2. Who I am Filippo Gangi Dino @ weLaika
3. Torino Coding Society - torinocodingsociety.it Every 2 weeks free and opened coding speechs (with food and beverage). If you love coding
4. I wanna be a WP dev
5. You are not alone
7. think about other developers search better solutions avoid 'developer lock-in' use conventions
8. whether you are using php (Haml, Slim), CSS (Sass, Scss) or javascript (coffescript) there are lot of style guides.
9. Example http://cssguidelin.es/ multiple files data-hook naming conventions
10. Editor
11. The editor is your better collegue. Choose it. Customize it.
13. Sublime Text Sublime Text http://www.sublimetext.com/ packages: Wordpress - packagecontrol.io/packages/WordPress Emmet - packagecontrol.io/packages/Emmet Foundation Snippets - packagecontrol.io/packages/Foundation%205%20Snippets
14. Dev env
15. You need it. Don't work live in production.
16. CLI use the! Use the CLI!
17. wp-cli - wp-cli.org wp plugin install hello-dolly wp plugin activate hello-dolly wp user import-csv /path/to/users.csv
18. wp-server - github.com/wp-cli/server-command $ w p s e r v e r P H P 5 . 5 . 2 4 D e v e l o p m e n t S e r v e r s t a r t e d a t J u l 1 4 1 9 : 1 0 : 0 0 2 0 1 5 L i s t e n i n g o n h t t p : / / l o c a l h o s t : 8 0 8 0
19. Plugins
21. few is better that many Never change a winning team suspect about swiss army knife plugins
22. Cons slowdown uncontrolled growth why ask to make something to a plugin when you can make yourself better? conflicts
23. Theme
24. Make your own theme. Is the only perfect solution for your needs.
25. There is only what you need.
27. Read the official WP themes (twentyfifteen, twentyfourteen, ....)
28. functions.php
30. Don't let functions.php do everything. You need to use it (or debug it)!
31. Conventions i n c / Put here your php logic.
32. flame also twentyfifteen have 355 lines of code and twentyfourteen 519 lines code is poetry
33. Enqueue
35. Use WordPress to manages queues of scripts and stylesheets.
36. < ? p h p w p _ e n q u e u e _ s c r i p t ( $ h a n d l e , $ s r c , $ d e p s , $ v e r , $ i n _ f o o t e r ) ; ? > < ? p h p w p _ e n q u e u e _ s t y l e ( $ h a n d l e , $ s r c , $ d e p s , $ v e r , $ m e d i a ) ; ? >
37. Versioning
39. Remember everything you've done Make teamwork possible Isolated introduction of features Help you to find the bug
40. Security
42. WordPress is the most used CMS in the world. This is the problem.
43. Basically follow the official instructions: Hardening Wordpress - codex.wordpress.org/Hardening_WordPress
44. Deploy
45. Automate recurring tasks to avoid errors.
46. Example, simple, manual deploy sequence Open FileZilla. Connect. Search local theme folder. Select modified files. Push to production. Verify. Select forgotten files. Push to production. Change directory to plugins folder. Select new plugins. Push to production. Make a db dump. Launch s e d changing domain. Visit production phpmyadmin. Import dump. Go to backend. Make manually changes for serialized arrays settings.
48. Wordmove - github.com/welaika/wordmove $ w o r d m o v e p u s h - t p d
49. Maintenance
51. Also with automat(t)ic updates your site needs maintenance. Make your customers conscious.
52. Thanks to all Questions? @mukkoo - twitter.com/mukkoo filippo.gangidino@welaika.com dev.welaika.com