Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Collaborating with Craft
Search
Linda Gorman
October 27, 2017
Technology
3
480
Collaborating with Craft
Dotall October 2017
Linda Gorman
October 27, 2017
Tweet
Share
Other Decks in Technology
See All in Technology
知られざるprops命名の慣習 アクション編
uhyo
11
2.8k
Postman MCP 関連機能アップデート / Postman MCP feature updates
yokawasa
1
210
進捗
ydah
1
200
実践アプリケーション設計 ②トランザクションスクリプトへの対応
recruitengineers
PRO
4
1.1k
退屈なことはDevinにやらせよう〜〜Devin APIを使ったVisual Regression Testの自動追加〜
kawamataryo
4
900
VPC Latticeのサービスエンドポイント機能を使用した複数VPCアクセス
duelist2020jp
0
330
トヨタ生産方式(TPS)入門
recruitengineers
PRO
5
1.2k
AIとTDDによるNext.js「隙間ツール」開発の実践
makotot
6
780
事業価値と Engineering
recruitengineers
PRO
6
4.6k
Goでマークダウンの独自記法を実装する
lag129
0
230
Kubernetes における cgroup v2 でのOut-Of-Memory 問題の解決
pfn
PRO
0
320
「AI2027」を紐解く ― AGI・ASI・シンギュラリティ
masayamoriofficial
0
140
Featured
See All Featured
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Writing Fast Ruby
sferik
628
62k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
9
790
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
2.5k
KATA
mclloyd
32
14k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3k
Why You Should Never Use an ORM
jnunemaker
PRO
59
9.5k
Building an army of robots
kneath
306
46k
Making Projects Easy
brettharned
117
6.3k
Intergalactic Javascript Robots from Outer Space
tanoku
272
27k
Why Our Code Smells
bkeepers
PRO
339
57k
Transcript
Collaborating with Craft Linda Gorman 10/23/17
None
None
None
None
Internal External Designer Developer Creative Director Technical Director Project Manager
Illustrator Copywriter End-User(s) Client Stakeholders Contractors
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
Risk -> Consequence -> Mitigations
1. Collaborators are working in disparate environments. RISK
Code conflicts, duplication, bugs. LEADS TO
None
Keep settings consistent. MITIGATION
• Make changes on production and pull • Store settings
in version control • Craft 3 Migrations Keep settings consistent.
• Make changes on production and pull • Store settings
in version control • Craft 3 Migrations Keep settings consistent.
None
None
Deployment Task (via Capistrano)
Keep content consistent (where it makes sense).
None
2. Collaborators don’t know everything going on in the codebase.
RISK
Unintended side effects, aka bugs. LEADS TO
None
Establish a git workflow. MITIGATION
None
master develop basic-article pull-quote photo-slideshow fullbleed-header release 0.7
Be faithful to task tracking. MITIGATION
None
Document early and often. MITIGATION
None
• Descriptive field labels • Comments in code • Detailed
pull request descriptions • Clear error messaging/feedback Documentation could look like…
Testing. MITIGATION
Visual regression testing.
None
PHPUnit (if you need it).
3. Setup/Updating local environments is high- touch and laborious. RISK
Inefficiency and frustration. LEADS TO
Tailor setup processes to your audience. How technical are they?
MITIGTION
Scripting (responsibly).
4. Feedback comes too late. RISK
Inflexibility, unhappy client. LEADS TO
Expose in-progress work early and often. MITIGATION
None
(But make sure to set expectations).
Be transparent; allow the client to prioritize revisions vs new
features. MITIGATION
None
5. Misaligned Assumptions. RISK
Perceived bugs. LEADS TO
Assign “homework.” MITIGATION
None
Show them how to Craft!
None
Find ways to make the CMS better serve the content.
None
None
None
An extra layer of QA
some unrelated thoughts:
flexibility custom design
None
content migration!
None
[email protected]