X All the Things: Total Content Control

  • 427 views
Uploaded on

Tim Cosgrove and Joe Turgeo

Tim Cosgrove and Joe Turgeo

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
427
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
5
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. THE LEADER IN DRUPAL PLATFORM DESIGN AND DEVELOPMENTSunday, November 4, 12
  • 2. X ALL THE THINGS TOTAL CONTENT CONTROL JOE TURGEON X TIM COSGROVESunday, November 4, 12
  • 3. WHO THIS IS FOR • Developers • Project Owners • Multilingual Site Creators • Content Developers • Site BuildersSunday, November 4, 12
  • 4. THE LEADER IN DRUPAL PLATFORM DESIGN AND DEVELOPMENTSunday, November 4, 12
  • 5. JOE TURGEON Solutions Architect jturgeon@phase2technology.com @arithmetric TIM COSGROVE Software Architect tcosgrove@phase2technology.com @timcosgroveSunday, November 4, 12
  • 6. THE CLIENTSunday, November 4, 12
  • 7. Sunday, November 4, 12
  • 8. “BRAND Z” • Large multinational consumer products company • $9.7 billion in sales annually • Nearly $1 billion in online sales • Operates in about 150 countries, about 50 online • Sites in about 30 languagesSunday, November 4, 12
  • 9. EXISTING WEB SOLUTION • Custom-written commerce engine • Also serves static content • No CMS of any kind • Non-commerce pages static HTMLSunday, November 4, 12
  • 10. BRAND Z WANTS ALL THE THINGS!Sunday, November 4, 12
  • 11. image: http://hyperboleandahalf.blogspot.com/2010/06/this-is-why-ill-never-be-adult.htmlSunday, November 4, 12
  • 12. DRUPAL-BASED PUBLISHING PLATFORM • Multi-market • Multi-lingual • Multiple brands • Interfaces with existing ecommerce systemSunday, November 4, 12
  • 13. En gli sh : bmSunday, November 4, 12 Sp wu an sa ish :b .c om mw us a .co m/ es BMW US site Ge rm an BRAND Z PLATFORM CONCEPT :b Fre mw nc .ch h :b mw Ita .ch lian /fr :b mw .ch /it BMW Switzerland site BMW brand sites En gli sh : mi Sp niu an sa ish .co :m m iniu sa .co m/ es Mini US site En gli sh : mi ni. Fre ca nc h: m ini. ca /fr Mini US site Mini brand sites
  • 14. PLATFORM OBJECTIVESSunday, November 4, 12
  • 15. ALL THE CONTENT! • Subject to workflow • Able to be translated • Able to be saved to multiple revisions, including draftsSunday, November 4, 12
  • 16. image: http://hyperboleandahalf.blogspot.com/2010/06/this-is-why-ill-never-be-adult.htmlSunday, November 4, 12
  • 17. screenshot:http://www.bmwusa.com/Sunday, November 4, 12
  • 18. screenshot:https://www.bmwusa.com/Secured/Content/Forms/Login.aspxSunday, November 4, 12
  • 19. BATCHED CONTENT MANAGEMENT • Preview whole groups of content updates together • Publish, unpublish, and manage the workflow state of whole groups of content en masseSunday, November 4, 12
  • 20. Sunday, November 4, 12
  • 21. FLEXIBLE LAYOUTS • Select different templates to use for the same content type • Allow users to define complex inputs for the output of structured content • Allow users to build basic templates themselves and to reuse themSunday, November 4, 12
  • 22. Sunday, November 4, 12
  • 23. CONSISTENT, INTUITIVE UI • CMS users with only basic training • CMS will be used worldwideSunday, November 4, 12
  • 24. Sunday, November 4, 12
  • 25. Sunday, November 4, 12
  • 26. Sunday, November 4, 12
  • 27. PLATFORM GOALS • Content layout is flexible • All content is translatable • Content is subject to workflow • The CMS UI is consistent and intuitiveSunday, November 4, 12
  • 28. image: http://hyperboleandahalf.blogspot.com/2010/06/this-is-why-ill-never-be-adult.htmlSunday, November 4, 12
  • 29. LAYOUT ALL THE THINGS!Sunday, November 4, 12
  • 30. OBJECTIVESSunday, November 4, 12
  • 31. MULTIPLE LAYOUTS IN CONTENT • Layouts are independent of content type • Multiple layouts can be used in one content type • Editors can define own layouts in CMSSunday, November 4, 12
  • 32. Sunday, November 4, 12
  • 33. SOLUTION: TEMPLATE FIELD • Allows a single field to contain many pieces of data • Each template has HTML, optional CSS & JS • Can be in code, or DB; can be overridden • Because it’s a field, can be revisionedSunday, November 4, 12
  • 34. Sunday, November 4, 12
  • 35. Sunday, November 4, 12
  • 36. Sunday, November 4, 12
  • 37. Sunday, November 4, 12
  • 38. Sunday, November 4, 12
  • 39. OTHER BENEFITS • Allows node-specific layouts, even within one content type • Layouts can be shared across content typesSunday, November 4, 12
  • 40. MULTIPLE LAYOUTS IN PAGES • Layout of a single content type may change significantly from node to node or even revision to revision • Layouts need to be attached to node for workflow, etc.Sunday, November 4, 12
  • 41. CONTROL OVER BLOCKS • Content editors need to create blocks freely • Need to be able to place blocks as part of page content • Need to be able to embed blocks in other contentSunday, November 4, 12
  • 42. SOLUTION: BLOCK REFERENCE • Insert blocks into nodes as field content • In combination with a content block solution, allows reusable block content to be laid out in arbitrary layoutsSunday, November 4, 12
  • 43. Sunday, November 4, 12
  • 44. Sunday, November 4, 12
  • 45. SOLUTION: EMBEDABBLES • Allows block content to be placed into rich text contexts • Effectively allows revisioning of block placement within that contextSunday, November 4, 12
  • 46. Sunday, November 4, 12
  • 47. Sunday, November 4, 12
  • 48. Sunday, November 4, 12
  • 49. Sunday, November 4, 12
  • 50. Sunday, November 4, 12
  • 51. Sunday, November 4, 12
  • 52. image: http://hyperboleandahalf.blogspot.com/2010/06/this-is-why-ill-never-be-adult.htmlSunday, November 4, 12
  • 53. TRANSLATE ALL THE THINGS!Sunday, November 4, 12
  • 54. OBJECTIVESSunday, November 4, 12
  • 55. ALL CONTENT IS TRANSLATABLE • Body content, block content, menu items, form labels, and any other visible text • Related translations grouped and accessible from the source nodeSunday, November 4, 12
  • 56. “SUBSCRIPTION” VS “LOCALIZATION” • Subscribed content adopts a specific piece of content from another language • Localized content begins as a copy from another language, but can be edited independently and divergeSunday, November 4, 12
  • 57. EACH TRANSLATION IS DISTINCT • Translations may not be literal • The version of content for a particular market/language should be managed separately from other markets/ languagesSunday, November 4, 12
  • 58. Sunday, November 4, 12
  • 59. Sunday, November 4, 12
  • 60. Sunday, November 4, 12
  • 61. SOLUTION: CONTENT TRANSLATION + I18NSunday, November 4, 12
  • 62. Sunday, November 4, 12
  • 63. SOLUTION: CUSTOM EXTENSION FOR SUBSCRIPTIONS + UI ENHANCEMENTSSunday, November 4, 12
  • 64. Sunday, November 4, 12
  • 65. SOLUTION: DOMAINSunday, November 4, 12
  • 66. Sunday, November 4, 12
  • 67. SOLUTION: DOMAIN CUSTOM EXTENSIONSunday, November 4, 12
  • 68. POTENTIAL DRUPAL 8 IMPROVEMENTS • Integrate more functionality from i18n in core • Make entities translatable • Simplify UI for managing content translationsSunday, November 4, 12
  • 69. image: http://hyperboleandahalf.blogspot.com/2010/06/this-is-why-ill-never-be-adult.htmlSunday, November 4, 12
  • 70. REVISION ALL THE THINGS!Sunday, November 4, 12
  • 71. REVISIONS? • More like “versions” • Keep old copies of content • Ideally, work on multiple versions of content at onceSunday, November 4, 12
  • 72. WORKFLOW? • Drupal has “unpublished” and “published” • Add more states, like “approved” or “needs edits” • Control access to each of those statesSunday, November 4, 12
  • 73. CORE DRUPAL REVISIONS • Only saves previous copies • Can’t edit two copies independently • No working drafts • Only applies to nodes • Only core ‘workflow’ statesSunday, November 4, 12
  • 74. ALL THE THINGS? • Nodes • Menus • Block Content • Block PlacementSunday, November 4, 12
  • 75. NODE ALL THE THINGS! • Can be translated • Drupal takes care of basic revisions • Basic workflow needs metSunday, November 4, 12
  • 76. MENUS • Drupal Menus are not strictly content • No publishing, unpublishing • Behavior can be unpredictable and confusing for content editorsSunday, November 4, 12
  • 77. SOLUTION: MENU FIELD • Menu-like content as a field • Translatable, revisionable • Mirrors Drupal native menus • Flexible menu content - rich textSunday, November 4, 12
  • 78. Sunday, November 4, 12
  • 79. Sunday, November 4, 12
  • 80. SOLUTION: NODEBLOCKSunday, November 4, 12
  • 81. SOLUTION: STATE FLOW • Highly configurable workflow solution • API-driven, developer-friendlySunday, November 4, 12
  • 82. haSunday, November 4, 12
  • 83. REVISION TAGGING • Label each revision • All content with that tag can be acted on • Preview site with different tagsSunday, November 4, 12
  • 84. Sunday, November 4, 12
  • 85. Sunday, November 4, 12
  • 86. Sunday, November 4, 12
  • 87. Sunday, November 4, 12
  • 88. POTENTIAL DRUPAL 8 IMPROVEMENTS • Entities Everywhere • Content Staging Intiative and Site Preview SystemSunday, November 4, 12
  • 89. LESSONSSunday, November 4, 12
  • 90. RESOURCES • Template Field http://drupal.org/project/template_field • Formatter Field http://drupal.org/project/formatter_field • Block Reference http://drupal.org/project/blockreferenceSunday, November 4, 12
  • 91. RESOURCES • Embeddables http://drupal.org/project/embeddable • i18n http://drupal.org/project/i18n • Domain http://drupal.org/project/domainSunday, November 4, 12
  • 92. RESOURCES • State Machine http://drupal.org/project/state_machine • Nodeblock http://drupal.org/project/nodeblock • Menu Field http://drupal.org/project/menu_fieldSunday, November 4, 12
  • 93. THANKS.Sunday, November 4, 12
  • 94. QUESTIONS? JOE TURGEON TIM COSGROVE Solutions Architect Software Architect jturgeon@phase2technology.com tcosgrove@phase2technology.com @arithmetric @timcosgroveSunday, November 4, 12
  • 95. phase2technology.com @phase2techSunday, November 4, 12