O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Not a Place of Honor Learning the Right Lessons
 From Terrible Content Models Jeff Eaton of Lullabot Presented by Drupal4G...
I work for Lullabot. We content stuff. I’m @eaton.
Legacy Content Model
The Case ofthe Vegan Mp3
Title Description EventDate RegCost IsVegan…
The Case ofthe 50 Article Types
Article …IL article …NYarticle …TX article …FL article
The Case ofthe
 Team Mailing List
We add the announcement, but it’s sent in raw HTML…
We add the announcement, but it’s sent in raw HTML…
The Case ofthe
 5-Minute Edit Form
We have a content type for everydesign pattern!
Why Does Evil Exist?
‣ Malicious co-workers are trying to drive us mad to win a contest ‣ Ourworld is the test suite for a multiverse that actu...
‣ When we started, allwe had was an events management system… ‣ We didn’t have a developerforthe prototype, and it had to ...
“It works for now…” “This is how it’s
 supposed to be.”
The Case ofthe
 Pile of Uranium
✓ Store tons of radioactive waste ✓ Last 10,000 years ✓ Warn future humans ✓ Must not look too cool
ProbablyTreasure,right?
This place is not a place of honor. No highly esteemed deed is commemorated here. What is here is dangerous and repulsive ...
How Can We Tellthe Difference?
Common
 Patterns
‣ Modeling pages, not content ‣ Exceptions are the rule ‣ Lava flow content models ‣ Cargo cult workflow
Modeling Pages, Not Content Content types that map to visual chunks of a page, ratherthan meaningful messages.
Exceptions Are the Rule Most content lives in “generic page” or “flexible” content types
Lava Flow Content Model Waves of content types created, then abandoned for new ones.
Cargo Cult Workflow No one knows whywe make things this way, but it’s how it must be done…
Forensic Empathy
Constraints Goals and Aspirations Choices
Hunt forthe Original Intent ‣ Can you find documentation? ‣ Can you talk to people who worked on it? ‣ Do you knowwhy it’s ...
Examine the
 Past Constraints ‣ Limited budget (financial ortemporal) ‣ Team knowledge, experience ‣ Outdated technology ‣ ...
What’s the Same?
 What’s Changed? ‣ Technology maturity ‣ Political pressures ‣ Understanding ofthe problem
Understand Why To Improve How
Document It Forthe Future
makes terriblecontent sometimes
Thanks for Coming! ‣ Heckle me: twitter.com/eaton ‣ Talk shop: eaton@lullabot.com ‣ Read more: lb.cm/eaton ‣ Work with us:...
Thanks for Coming! ‣ Heckle me: twitter.com/eaton ‣ Talk shop: eaton@lullabot.com ‣ Read more: lb.cm/eaton ‣ Work with us:...
This Is not a Place of Honor
Próximos SlideShares
Carregando em…5
×

This Is not a Place of Honor

307 visualizações

Publicada em

Anyone who's worked on a web project has stumbled across the horror of "legacy content" that makes no sense, or is held together with duck tape and dreams. In this talk, we'll look at some noteworthy content disasters, learn to spot problem areas in the future, and remember to be kind: the disasters of the past were built be people just like us, working with constraints we may not understand.

Publicada em: Negócios
Licença: CC Attribution-ShareAlike License
no profile picture user

  • Entre para ver os comentários

This Is not a Place of Honor

  1. 1. Not a Place of Honor Learning the Right Lessons
 From Terrible Content Models Jeff Eaton of Lullabot Presented by Drupal4Gov
  2. 2. I work for Lullabot. We content stuff. I’m @eaton.
  3. 3. Legacy Content Model
  4. 4. The Case ofthe Vegan Mp3
  5. 5. Title Description EventDate RegCost IsVegan…
  6. 6. The Case ofthe 50 Article Types
  7. 7. Article …IL article …NYarticle …TX article …FL article
  8. 8. The Case ofthe
 Team Mailing List
  9. 9. We add the announcement, but it’s sent in raw HTML…
  10. 10. We add the announcement, but it’s sent in raw HTML…
  11. 11. The Case ofthe
 5-Minute Edit Form
  12. 12. We have a content type for everydesign pattern!
  13. 13. Why Does Evil Exist?
  14. 14. ‣ Malicious co-workers are trying to drive us mad to win a contest ‣ Ourworld is the test suite for a multiverse that actuallyworks well ‣ We do our best, under pressure,
 with imperfect knowledge.
  15. 15. ‣ When we started, allwe had was an events management system… ‣ We didn’t have a developerforthe prototype, and it had to launch… ‣ It was the simplest way to migrate subscriptions from the CEO’s blog… ‣ The ten-page prototype worked great…
  16. 16. “It works for now…” “This is how it’s
 supposed to be.”
  17. 17. The Case ofthe
 Pile of Uranium
  18. 18. ✓ Store tons of radioactive waste ✓ Last 10,000 years ✓ Warn future humans ✓ Must not look too cool
  19. 19. ProbablyTreasure,right?
  20. 20. This place is not a place of honor. No highly esteemed deed is commemorated here. What is here is dangerous and repulsive to us. This message is a warning. “ ”
  21. 21. How Can We Tellthe Difference?
  22. 22. Common
 Patterns
  23. 23. ‣ Modeling pages, not content ‣ Exceptions are the rule ‣ Lava flow content models ‣ Cargo cult workflow
  24. 24. Modeling Pages, Not Content Content types that map to visual chunks of a page, ratherthan meaningful messages.
  25. 25. Exceptions Are the Rule Most content lives in “generic page” or “flexible” content types
  26. 26. Lava Flow Content Model Waves of content types created, then abandoned for new ones.
  27. 27. Cargo Cult Workflow No one knows whywe make things this way, but it’s how it must be done…
  28. 28. Forensic Empathy
  29. 29. Constraints Goals and Aspirations Choices
  30. 30. Hunt forthe Original Intent ‣ Can you find documentation? ‣ Can you talk to people who worked on it? ‣ Do you knowwhy it’s being changed?
  31. 31. Examine the
 Past Constraints ‣ Limited budget (financial ortemporal) ‣ Team knowledge, experience ‣ Outdated technology ‣ Political pressures
  32. 32. What’s the Same?
 What’s Changed? ‣ Technology maturity ‣ Political pressures ‣ Understanding ofthe problem
  33. 33. Understand Why To Improve How
  34. 34. Document It Forthe Future
  35. 35. makes terriblecontent sometimes
  36. 36. Thanks for Coming! ‣ Heckle me: twitter.com/eaton ‣ Talk shop: eaton@lullabot.com ‣ Read more: lb.cm/eaton ‣ Work with us: lullabot.com/services
  37. 37. Thanks for Coming! ‣ Heckle me: twitter.com/eaton ‣ Talk shop: eaton@lullabot.com ‣ Read more: lb.cm/eaton ‣ Work with us: lullabot.com/services …Any Questions?

×