Collaborating with Craft

Dotall October 2017

Transcript

1. Collaborating with Craft Linda Gorman 10/23/17
6. Internal External Designer Developer Creative Director Technical Director Project Manager Illustrator Copywriter End-User(s) Client Stakeholders Contractors
7. Upstatement Yale E360 Roger EIC Kat WEB EDITOR Matt YALE IT Linda DEVELOPER James DESIGNER/FRONT-END DEV Keri DESIGNER/FRONT-END DEV Scott CREATIVE DIRECTOR Cameron PRODUCER
8. Risk -> Consequence -> Mitigations
9. 1. Collaborators are working in disparate environments. RISK
10. Code conflicts, duplication, bugs. LEADS TO
12. Keep settings consistent. MITIGATION
13. • Make changes on production and pull • Store settings in version control • Craft 3 Migrations Keep settings consistent.
14. • Make changes on production and pull • Store settings in version control • Craft 3 Migrations Keep settings consistent.
17. Deployment Task (via Capistrano)
18. Keep content consistent (where it makes sense).
20. 2. Collaborators don’t know everything going on in the codebase. RISK
21. Unintended side effects, aka bugs. LEADS TO
23. Establish a git workflow. MITIGATION
25. master develop basic-article pull-quote photo-slideshow fullbleed-header release 0.7
26. Be faithful to task tracking. MITIGATION
28. Document early and often. MITIGATION
30. • Descriptive field labels • Comments in code • Detailed pull request descriptions • Clear error messaging/feedback Documentation could look like…
31. Testing. MITIGATION
32. Visual regression testing.
34. PHPUnit (if you need it).
35. 3. Setup/Updating local environments is high- touch and laborious. RISK
36. Inefficiency and frustration. LEADS TO
37. Tailor setup processes to your audience. How technical are they? MITIGTION
38. Scripting (responsibly).
39. 4. Feedback comes too late. RISK
40. Inflexibility, unhappy client. LEADS TO
41. Expose in-progress work early and often. MITIGATION
43. (But make sure to set expectations).
44. Be transparent; allow the client to prioritize revisions vs new features. MITIGATION
46. 5. Misaligned Assumptions. RISK
47. Perceived bugs. LEADS TO
48. Assign “homework.” MITIGATION
50. Show them how to Craft!
52. Find ways to make the CMS better serve the content.
56. An extra layer of QA
57. some unrelated thoughts:
58. flexibility custom design
60. content migration!
62. linda.gorman@upstatement.com