1. 2. Agenda 12:00 Introduction 12:10 The Drupal Design Phase Practical Guidelines And Crucial Questions Damien Dewitte - Head of Business Consulting 13:00 The Drupal Build Phase Best Practices And Tools Jan Lemmens Sr. Drupal Consultant 13:20 The Drupal Run Phase Things You May Need And Want To Do Peter De Rudder Service Delivery Manager 14:00 Seminar Wrap-Up

2. 3. Introduction Amplexor Fact Sheet Founded February 2001 Lifecycle Enterprise Content Management projects Digital Experience Management Document centric applications Enterprise collaboration Offices in Leuven, Ghent and Romania Today: ~100 ECM Consultants ~11,5 M turnover 3 YR CAGR > 20% Part of euroscript group since 2013 Founded by Saarbrucker ZeitungVerlag und Druckerei GmbH in 1987 Present in 18 countries 32 offices worldwide 1560 employees +100M turnover 3. 4. Lifecycle Enterprise Content Management Solutions 4. 5. The Best Products Drupal is an open source content management platform powering millions of websites and applications. Its built, used, and supported by an active and diverse community of people around the world. Engaging your customers: anywhere, anytime, any channel. SDL Tridion is Web Content Management (WCM) that makes a global impact. Adobe Software's Adobe Experience Manager (WCM) is a platform for delivering engaging, multi- channel customer experiences to drive online business success. 5. 6. The Best People (Expertise) Interdisciplinary team Understanding both the business and the software Combining expertise, experience and creativity with a strong focus on the essentials making valuable knowledge available exactly where it is needed at the time 6. 7. Relevant Experience 7. 8. Agenda 12:00 Introduction 12:10 The Drupal Design Phase Practical Guidelines And Crucial Questions Damien Dewitte - Head of Business Consulting 13:00 The Drupal Build Phase Best Practices And Tools Jan Lemmens Sr. Drupal Consultant 13:20 The Drupal Run Phase Things You May Need And Want To Do Peter De Rudder Service Delivery Manager 14:00 Seminar Wrap-Up 8. 9. Design 9. 10. The Design phase consists of Business Analysis Vision, Marketing/Communication Strategy, KPIs High-level concept & Prototyping Functional Analysis & Information Architecture Graphic Design (Solution Architecture / Technology) Functional Design 10. 11. 11. 12. The deliverables of the design phase Wireframes / Clickable mockups in order to align between stakeholders and teams Information architecture in order to prepare for content creation Functional Analysis in order to align between what the website should do for the business and how it is implemented by the technical people Annexes to functional analysis: SEO Guidelines, Guidelines for Metrics, Web Style guide, Functional Design in order to make sure that the Drupal platform: is effective for content creators Is implemented as much as possible out-of-the-box . Refined input for scoping and prioritization for the Build phase 12. 13. 13. 14. 14. 15. Non-functional Requirements Anticipating the run phase Volumes Performance requirements Speed of Publishing Security Browser/Device support in the front-end Supported Operating systems and browsers for people working on the back-end Remote access Making sure the system can be easily supported afterwards 15. 16. Web Design (STYLE) Functional Analysis (INTERAC TION) Information Architecture (NAVIGATIO N & CONTENT) 16. 17. Web design challenges 1) Be content proof E.g. Design Navigation which can be extended E.g. Allow content blocks to size correctly 17. 18. Web design challenges 2) Support all content types E.g. Foresee tables Support the requirements of the information architecture (navigation levels, Sub- headings, ...) 18. 19. Web design challenges 3) Be consistent E.g. If buttons need to be generated by the CMS, make them consistent 19. 20. WCM Tool Selection Content granularity Multi-linguality Multi-site Decentralized Content Editing User Generated Content Usability for Content Editors Performance Technical Company Guidelines 20. 21. Functional Design challenges 1) Optimize content granularity Field Remarks Input format Mandator y? 1 or n? Article Title Is rendered as H1 (Page Title) txt 1 row No 1 Article Intro Text Introduces the page and chapters. Formatted Text No 1 Image Will be displayed on Fixed position in page Intro No 1 Links Embedded Schema No n Link CompLink -->all content types Yes 1 Link text 0txt 1 row Yes 1 Link Target Default: Current Select (current, new, , popup) No 1 Link Popup Dimensions works only with option "pop-up" selected txt 1 row (format: ####x####). If blank, foresee default dimensions) No 1 Paragraph Embedded No n Paragraph - Title Is rendered as H2 txt 1 row No 1 Paragraph - Body inline links, images, H3, H4, table Formatted Text No 1 Paragraph - Image Will be displayed on Fixed position in paragraph No 1 Paragraph Links Embedded Schema No n Link CompLink -->all content types Yes 1 Link text 0txt 1 row Yes 1 Link Target Default: Current Select (current, new, , popup) No 1 Link Popup Dimensions works only with option "pop-up" selected txt 1 row (format: ####x####). If blank, foresee default dimensions) No 1 Field Remarks Input format Mandator y? 1 or n? Title txt & row Yes 1 Body Feel free .... Formatted text 21. 22. Functional Design challenges 2) Minimize Content editor mistakes Reduce number of templates where possible Describe good practices for naming and storing of content objects Automate tasks in the background Simplify the user interface where possible Hide what may not be touched 22. 23. Functional Design challenges 3) Understand the tool Use Out-of-the-box functionality Do not re-invent the wheel 23. 24. Functional Design challenges 4) Be exhaustive and precise E.g. The News and Events paradigm Event Event Detail Events Overview (incl Calendar) Event Widget Show 5 upcoming events, which are targeted to logged in user, but hide if user has already registered Show all upcoming events, order by date Show link to registration form 24. 25. Cloud Social Mobile Context Subscribe Conversion Web Analytics User Preferences Digital Experience Management 25. 26. Content is King 26. 27. Content or Navigation? 27. 28. Content or Navigation? Navigation (Banners, related information, Widgets, ) Page Dressing Content 28. 29. Content Publishing Actors Webmasters & Marketeers Copywriters, Content Editors & Content Owners 29. 30. The only way to create content that meets changing customer needs is to adopt a unified content strategy. Such a strategy allows you to develop adaptive content that can be efficiently manufactured into a variety of information products for multiple devices. (Managing enterprise content: A unified content strategy, Ann Rockley & Charles Cooper) 30. 31. Defining Content Types 31. 32. What are the most common content types? 32. 33. 33. 34. Title/Body Content Typing Common practice on Blogs and Wikis 34. 35. Highly Structured Content Typing Common Practice in Enterprise WCM 35. 36. Factors impacting decisions on content types Site Search & Search Results SEO Mobile (and multi-channel in general) Usability for Content Editors & Webmasters Flexibility Automate Presentation and Enforce consistency Matching with External Content / Migrated Content 36. 37. Automate Presentation & Enforce Consistency 37. 38. Flexibility Sometimes, generating automatic listings of Content is not what you want. You want to be in control. 38. 39. Tips while defining Content Types Do not add presentation logic to content types 39. 40. Tips while defining Content Types Show on homepage can be tricky if the content is re-used on multiple sites/channels 40. 41. Tips while defining Content Types When to use in-line images? 41. 42. Tips while defining Content Types How do you define Related Content? It can be based on an algorithm (tagging alone is not enough) Linking articles together can be an editorial decision/action 42. 43. Tips while defining Content Types Tables Can be generated automatically if data is structured (and layout is predictable) Usually need flexibility and therefore rely on webmaster talent 43. 44. Drupal specific design? Know your modules !!!! 44. 45. Agenda 12:00 Introduction 12:10 The Drupal Design Phase Practical Guidelines And Crucial Questions Damien Dewitte - Head of Business Consulting 13:00 The Drupal Build Phase Best Practices And Tools Jan Lemmens Sr. Drupal Consultant 13:20 The Drupal Run Phase Things You May Need And Want To Do Peter De Rudder Service Delivery Manager 14:00 Seminar Wrap-Up 45. 46. Lifecycle Enterprise Content Management Solutions 46. 47. no licensing cost fast time to market 47. 48. 48. 49. Drupal is not an empty box 49. 50. 4 content model modules documentation tools 50. 51. content model 51. 52. not a page-based CMS 52. 53. very content centric objects with metadata 53. 54. summary CTA social related content properties 54. 55. introduction paragraph paragraph related content visual CTA table of contents (auto-generated) 55. 56. 56. 57. 57. 58. a scalable content infrastructure 58. 59. reduce rich text impedes reuse and migration low consistency low semantics no WYSIWYG 59. 60. minimal rich text editor controls which do not break layout 60. 61. flexibility structure depends on expertise at customer website profile (e.g. B2B vs. B2C) 61. 62. modules 62. 63. Drupal is not an empty box 63. 64. there is a module for that! -- average Drupal sales guy 64. 65. > 6000community modules for Drupal 7 65. 66. community modules quality greatly varies compatibility check strict curation is crucial whitelist increases predictability support upgradeability 66. 67. tools 67. 68. cool but what is the value for business? 68. 69. Jenkins CI quality assurance through automated testing fast deployments reduce time-to- market automation increases predictability 69. 70. Vagrant new developers can quickly enroll reduces suprises on go-live support team are quickly up-to- speed 70. 71. documentation 71. 72. documentation cross-team lessons learned server configuration go-live plan release plan knowledge sharing 72. 73. predictability risk 73. 74. Agenda 12:00 Introduction 12:10 The Drupal Design Phase Practical Guidelines And Crucial Questions Damien Dewitte - Head of Business Consulting 13:00 The Drupal Build Phase Best Practices And Tools Jan Lemmens Sr. Drupal Consultant 13:20 The Drupal Run Phase Things You May Need And Want To Do Peter De Rudder Service Delivery Manager 14:00 Seminar Wrap-Up 74. 75. Amplexor Service Delivery 75. 76. Running your application 76. 77. Monitoring your Drupal Website 77. 78. Is your website available? WHAT IS YOUR REQUIRED UPTIME? 78. 79. Is your website available? 79. 80. Is your website available? 98 99 100 201308 201309 201310 201311 201312 201401 201402 201403 201404 201405 201406 201407 201408 201409 201410 201411 201412 Availability Up me trend SLA Availability 80. 81. Monitoring your Drupal Website Basic monitoring via PingDom Advanced monitoring via NewRelic 81. 82. Monitoring your Drupal Website 82. 83. Performance monitoring Do you know your performance? Apdex(Application Performance Index) is an open standard developed by anallianceof companies. It defines a standard method for reporting andcomparing the performance of software applications in computing. Its purpose is to convert measurements into insightsabout user satisfaction,by specifying a uniform way to analyze and report on the degree to which measured performance meets user expectations. 83. 84. Performance monitoring 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 201308 201309 201310 201311 201312 201401 201402 201403 201404 201405 201406 201407 201408 201409 201410 201411 201412 Apdex Frustra ng Tolera ng Sa sfac on Apdex 84. 85. Performance monitoring 85. 86. Application monitoring 86. 87. Capacity monitoring Primary goal: monitor & act on system capacity Bandwidth Disks CPU Memory 87. 88. Keeping your website healthy 88. 89. Keeping your website healthy 89. 90. Drupal update manager 90. 91. Major & minor updates? Foresee budget for the necessary updates (security fixes), Core + modules Think before you begin: choose the stable contrib modules Major updates not part of the RUN phase (project) At the Amplexor Service Center we have reserved Drupal resources every month to check the security updates for our Drupal projects. 91. 92. Releasing updates 92. 93. Amplexor Service Delivery 93. 94. Service Delivery Offering 94. 95. Service Delivery Offering 95. 96. Reporting on monitoring & performance 96. 97. New Relic demo by Jan 97. 98. Agenda 12:00 Introduction 12:10 The Drupal Design Phase Practical Guidelines And Crucial Questions Damien Dewitte - Head of Business Consulting 13:00 The Drupal Build Phase Best Practices And Tools Jan Lemmens Sr. Drupal Consultant 13:20 The Drupal Run Phase Things You May Need And Want To Do Peter De Rudder Service Delivery Manager 14:00 Seminar Wrap-Up 98. 99. Whats next?