Save 37% off PRO during our Black Friday Sale! »

Collaborating with Craft

Collaborating with Craft

Dotall October 2017

6b13cd71fc46f401ca69c3733144d370?s=128

Linda Gorman

October 27, 2017
Tweet

Transcript

  1. Collaborating with Craft Linda Gorman 10/23/17

  2. None
  3. None
  4. None
  5. None
  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

  11. None
  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.
  15. None
  16. None
  17. Deployment Task (via Capistrano)

  18. Keep content consistent (where it makes sense).

  19. None
  20. 2. Collaborators don’t know everything going on in the codebase.

    RISK
  21. Unintended side effects, aka bugs. LEADS TO

  22. None
  23. Establish a git workflow. MITIGATION

  24. None
  25. master develop basic-article pull-quote photo-slideshow fullbleed-header release 0.7

  26. Be faithful to task tracking. MITIGATION

  27. None
  28. Document early and often. MITIGATION

  29. None
  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.

  33. None
  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

  42. None
  43. (But make sure to set expectations).

  44. Be transparent; allow the client to prioritize revisions vs new

    features. MITIGATION
  45. None
  46. 5. Misaligned Assumptions. RISK

  47. Perceived bugs. LEADS TO

  48. Assign “homework.” MITIGATION

  49. None
  50. Show them how to Craft!

  51. None
  52. Find ways to make the CMS better serve the content.

  53. None
  54. None
  55. None
  56. An extra layer of QA

  57. some unrelated thoughts:

  58. flexibility custom design

  59. None
  60. content migration!

  61. None
  62. linda.gorman@upstatement.com