Working with WordPress in a Team Environment

1,990 views

Published on

Working with WordPress in a Team Environment

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,990
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Working with WordPress in a Team Environment

  1. 1. Making the jump to GIT and IDE’s (aka, playing nicely with others)
  2. 2. What are we talking about? talking about?• Integrated Development Environments• GIT and Subversion• Working as a team• Coding Standards
  3. 3. Who is this for?• Intermediate developers;• Team players;• Public coding samples;
  4. 4. IDE’sMaking your job easier.
  5. 5. TextEdit is not an IDE
  6. 6. Example of an IDE
  7. 7. Common Features of an IDE• Code highlighting & variable identification• Debugging• Project Management• Deployment Tools• Function tips
  8. 8. Code highlighting
  9. 9. Debugging
  10. 10. Project Management
  11. 11. Function Helper
  12. 12. Function Helper
  13. 13. Deployment• FTP• Version Control Software
  14. 14. Version ControlWorking in a team environment.
  15. 15. SVNSubversive Tendencies.
  16. 16. Linux SVN
  17. 17. Visual SVN
  18. 18. Visual SVN with DIFF
  19. 19. GITA childish person with no manners.
  20. 20. SVN vs. GIT Why choose one?
  21. 21. SVN vs. GIT• GIT is localized, SVN is centralized;• SVN only stores files, GIT stores file data;• GIT is simply better;
  22. 22. Then why use SVN?• SVN is what WordPress.org uses;• SVN is what WordPress.com uses;• SVN is old school, no reason to change;
  23. 23. Working in a team. How to play well with others.
  24. 24. Working together• Agree on a versioning control solution;• Agree on an IDE preference;
  25. 25. Team EnvironmentsStep One: Developers Workspace
  26. 26. Developers Workspace• MAMP or LAMP setup as a local server;• IDE,Versioning Control, and environments;
  27. 27. The Process (Step 1) No. Does it work? Yes.
  28. 28. Team Environments Step Two: The Team Workspace
  29. 29. the i in team.
  30. 30. Developers Server• Secure working environment;• Version control access only;• Shares among developers;
  31. 31. The Process (Step 2) No. Does it work? Yes.
  32. 32. Team EnvironmentsStep Three: The Stakeholder Server
  33. 33. Developers Server• Secure working environment;• Version control access only;• Shared among the stakeholders;• Mimics the live server;
  34. 34. The Process (Step 3) Are you happy? Yes.
  35. 35. Team Environments Step Four: The Live Server
  36. 36. Live Server• Public environment;• Version control access only;
  37. 37. The Process (Step 4)
  38. 38. The ProcessDeveloper Dev Server Test Server Live Server
  39. 39. Coding StandardsHow to play well with others code.
  40. 40. Google the phrase: WordPress Coding Standards
  41. 41. WP Coding Standards• Single vs. Double Quotes• Indenting and Formatting Code• Brace Style & Spacing• Semantic Coding• Readability vs. Easy of Use• General Best Practices
  42. 42. WP Coding Standards• Single quotes are used when no variables are present in the string;• Double quotes process the contents;
  43. 43. WP Coding Standards• Single quotes are used when no variables are present in the string; $x = ‘Hello’.$name;• Double quotes process the contents; $x = “Hello $name”;
  44. 44. Formatting Code
  45. 45. Spacing Your Code
  46. 46. Capturing Errors
  47. 47. Semantic Naming
  48. 48. Standardizing

×