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
440
Collaborating with Craft
Dotall October 2017
Linda Gorman
October 27, 2017
Tweet
Share
Other Decks in Technology
See All in Technology
マルチモーダル理解と生成の統合 DeepSeek Janus, etc... / Multimodal Understanding and Generation Integration
hiroga
0
360
事業継続を支える自動テストの考え方
tsuemura
0
300
10分で紹介するAmazon Bedrock利用時のセキュリティ対策 / 10-minutes introduction to security measures when using Amazon Bedrock
hideakiaoyagi
0
170
Data-centric AI入門第6章:Data-centric AIの実践例
x_ttyszk
1
370
地方拠点で エンジニアリングマネージャーってできるの? 〜地方という制約を楽しむオーナーシップとコミュニティ作り〜
1coin
1
130
エンジニアの育成を支える爆速フィードバック文化
sansantech
PRO
3
660
トラシューアニマルになろう ~開発者だからこそできる、安定したサービス作りの秘訣~
jacopen
2
1.5k
Moved to https://speakerdeck.com/toshihue/presales-engineer-career-bridging-tech-biz-ja
toshihue
2
550
家電アプリ共通PF "Linova" のAPI利用とPostman活用事例ご紹介
yukiogawa
0
130
データの品質が低いと何が困るのか
kzykmyzw
6
1k
偶然 × 行動で人生の可能性を広げよう / Serendipity × Action: Discover Your Possibilities
ar_tama
1
740
『衛星データ利用の方々にとって近いようで触れる機会のなさそうな小話 ~ 衛星搭載ソフトウェアと衛星運用ソフトウェア (実物) を動かしながらわいわいする編 ~』 @日本衛星データコミニティ勉強会
meltingrabbit
0
120
Featured
See All Featured
A Philosophy of Restraint
colly
203
16k
Statistics for Hackers
jakevdp
797
220k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
40
2k
Building Better People: How to give real-time feedback that sticks.
wjessup
366
19k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
33
2.8k
The Art of Programming - Codeland 2020
erikaheidi
53
13k
How STYLIGHT went responsive
nonsquared
98
5.3k
[RailsConf 2023] Rails as a piece of cake
palkan
53
5.2k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
How GitHub (no longer) Works
holman
313
140k
Fontdeck: Realign not Redesign
paulrobertlloyd
82
5.4k
Embracing the Ebb and Flow
colly
84
4.6k
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]