Creating Sustainable Website Processes
•
1 gostou•390 visualizações
DPM Summit 2016 Breakout Workshop, San Antonio TX
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Creating Sustainable Website Processes
Semelhante a Creating Sustainable Website Processes (20)
Mais de Natalie Semczuk
Mais de Natalie Semczuk (7)
Último
Último (20)
Creating Sustainable Website Processes
- 1. CREATING SUSTAINABLE WEBSITE PROCESSES DPM Summit 2016 Natalie Semczuk @talkanatalka #dpmsummit2016
- 2. Hello
- 4. SUSTAINABLE WEBSITE PROCESSES • Considers the content manager • Makes scaling the site easier • Helps your team provide support • Provides a better foundation for post- launch site maintenance, growth and usage
- 5. SO, WHY DO WE NEED TO CARE?
- 7. FOR YOUR CLIENT, THE SITE ONLY BEGINS TO EXIST AFTER LAUNCH
- 8. WEBSITES EVOLVE Website changes and maintenance are inevitable. Why not make it as easy, consistent, and valuable as you can for both yourself and your clients?
- 12. HOW DO OUR CLIENTS UPDATE THEIR SITES?
- 13. THESE VARIATIONS LEAD TO MANY DIFFERENCES IN SITE MANAGEMENT
- 15. HOW?
- 16. HOW? (We’re getting to that)
- 17. BUT FIRST:
- 18. CONTENT DEBT
- 19. SUZANNE CHAPMAN csffct.co/uslib “…Organizations with large websites have a growing problem with…“content debt.” And like with “deferred maintenance” of buildings (the practice of postponing repairs to save costs), allowing too much…content debt will result in costing you much more in the long run.”
- 20. SUZANNE CHAPMAN csffct.co/uslib “…Organizations with large websites have a growing problem with…“content debt.” And like with “deferred maintenance” of buildings (the practice of postponing repairs to save costs), allowing too much…content debt will result in costing you much more in the long run.”
- 21. SUZANNE CHAPMAN csffct.co/uslib “…Organizations with large websites have a growing problem with…“content debt.” And like with “deferred maintenance” of buildings (the practice of postponing repairs to save costs), allowing too much…content debt will result in costing you much more in the long run.”
- 22. MELODY KRAMER csffct.co/18fcdb “Buildup of content debt may not be as apparent as technical debt, because it’s unlikely to initially cause software to break. Still, it could easily result in confusion…a greater need for customer support, slower progress, the need for more meetings, more external and internal complaints, and wasted time getting people on-boarded…”
- 23. MELODY KRAMER csffct.co/18fcdb “Buildup of content debt may not be as apparent as technical debt, because it’s unlikely to initially cause software to break. Still, it could easily result in confusion…a greater need for customer support, slower progress, the need for more meetings, more external and internal complaints, and wasted time getting people on-boarded…”
- 24. MELODY KRAMER csffct.co/18fcdb “Buildup of content debt may not be as apparent as technical debt, because it’s unlikely to initially cause software to break. Still, it could easily result in confusion…a greater need for customer support, slower progress, the need for more meetings, more external and internal complaints, and wasted time getting people on-boarded…”
- 26. CONTENT DEBT CAN TAKE THE FORM OF:
- 27. CONTENT DEBT CAN TAKE THE FORM OF: Outdated content
- 28. CONTENT DEBT CAN TAKE THE FORM OF:
- 29. CONTENT DEBT CAN TAKE THE FORM OF: Outdated content Difficult to find content
- 30. CONTENT DEBT CAN TAKE THE FORM OF:
- 31. CONTENT DEBT CAN TAKE THE FORM OF: Outdated content Difficult to find content Bloated upload directories
- 32. CONTENT DEBT CAN TAKE THE FORM OF:
- 33. CONTENT DEBT CAN TAKE THE FORM OF: Outdated content Difficult to find content Bloated upload directories Broken links
- 34. CONTENT DEBT CAN TAKE THE FORM OF:
- 35. CONTENT DEBT CAN TAKE THE FORM OF: Outdated content Difficult to find content Bloated upload directories Broken links Content styling & display errors
- 36. CONTENT DEBT CAN TAKE THE FORM OF:
- 39. CONTENT DEBT STARTS WITH US (Our teams, our work, our projects)
- 42. LET’S DO AWAY WITH: Hard-coded content Poorly defined formatting options
- 44. LET’S DO AWAY WITH: Hard-coded content Poorly defined formatting options Intensive image requirements
- 46. LET’S DO AWAY WITH: Hard-coded content Poorly defined formatting options Intensive image requirements Lack of documentation
- 48. Outdated content Difficult to find content Bloated upload directories Broken links Content styling & display errors HARD-CODED CONTENT POORLY DEFINED FORMATTING OPTIONS INTENSIVE IMAGE REQUIREMENTS LACK OF DOCUMENTATION
- 49. Outdated content Difficult to find content Bloated upload directories Broken links Content styling & display errors HARD-CODED CONTENT POORLY DEFINED FORMATTING OPTIONS INTENSIVE IMAGE REQUIREMENTS LACK OF DOCUMENTATION
- 50. Outdated content Difficult to find content Bloated upload directories Broken links Content styling & display errors HARD-CODED CONTENT POORLY DEFINED FORMATTING OPTIONS INTENSIVE IMAGE REQUIREMENTS LACK OF DOCUMENTATION
- 51. Outdated content Difficult to find content Bloated upload directories Broken links Content styling & display errors HARD-CODED CONTENT POORLY DEFINED FORMATTING OPTIONS INTENSIVE IMAGE REQUIREMENTS LACK OF DOCUMENTATION
- 52. Outdated content Difficult to find content Bloated upload directories Broken links Content styling & display errors HARD-CODED CONTENT POORLY DEFINED FORMATTING OPTIONS INTENSIVE IMAGE REQUIREMENTS LACK OF DOCUMENTATION
- 53. Outdated content Difficult to find content Bloated upload directories Broken links Content styling & display errors HARD-CODED CONTENT POORLY DEFINED FORMATTING OPTIONS INTENSIVE IMAGE REQUIREMENTS LACK OF DOCUMENTATION = FRUSTRATION
- 54. GIVING OUR CLIENTS THE TOOLS TO MANAGE THEIR SITES MAKES FOR BETTER USER EXPERIENCE
- 55. WE CAN REVERSE ENGINEER OUR PROCESSES TO INCLUDE EDUCATION + EXPECTATIONS
- 59. GOAL: IDENTIFY YOUR CLIENT’S CONTENT MANAGEMENT WORKFLOW Who manages the content?
- 60. GOAL: IDENTIFY YOUR CLIENT’S CONTENT MANAGEMENT WORKFLOW Who manages the content? Tools: 1. Questions & the 5 Whys 2. Content Workflow and Responsibilities map
- 61. CREATE A POOL OF QUESTIONS YOU MIGHT ASK YOUR CLIENT ABOUT CONTENT MANAGEMENT Activity
- 62. CREATE A POOL OF QUESTIONS YOU MIGHT ASK YOUR CLIENT ABOUT CONTENT MANAGEMENT Activity Hint: Use “the 5 whys” to dig into the root of your questions.
- 63. DISCUSS: What questions did everyone come up with? What sort of questions did you end up needing to break down? Did these lead to further questions? What is a common unclear area that might be resolved with questions?
- 64. SORT YOUR QUESTIONS INTO A CHRONOLOGICAL CHART: WHERE IN THE CONTENT PROCESS DO THESE QUESTIONS FIT? Activity
- 65. SORT YOUR QUESTIONS INTO A CHRONOLOGICAL CHART: WHERE IN THE CONTENT PROCESS DO THESE QUESTIONS FIT? Activity 1. Needs discovered 2. Creation 3. Approval 4. Publication
- 66. DISCUSS: Where you able to see these distinct stages of content creation in your questions? Did you identify gaps in your questions?
- 67. WE CAN USE THESE TECHNIQUES TO CREATE A CONTENT WORKFLOW & RESPONSIBILITIES MAP
- 69. OR IT COULD BE MUCH MORE COMPLEX: csffct.co/RGfGOu
- 70. OVERALL GOALS: • Educate ourselves and our clients about their content management workflow • Get clients thinking about their own process • Manage expectations from the start • Provide value prior to final launched product
- 71. DESIGN PHASE
- 73. DESIGNERS THINK IN PATTERNS TO CREATE MODULAR SYSTEMS Style guides Pattern libraries Front-end frameworks Atomic design
- 78. WE CAN THINK OF DESIGN + CONTENT AS PATTERNS AS WELL
- 79. RECOGNIZE CONTENT BLOCKS THAT ARE USED IN THE SAME WAY WHEN WE REVIEW DESIGN
- 80. BY THINKING IN CONTENT PATTERNS, WE CAN CONNECT FRONT-END USABILITY WITH BACK-END SUSTAINABILITY
- 81. HOW DO WE IDENTIFY THESE PATTERNS? Discussion/Activity
- 82. HOW DO WE IDENTIFY THESE PATTERNS? Discussion/Activity (and what do they look like?)
- 85. FEATURE PAGES
- 87. WHAT CAN WE INFER FROM THESE SIMILARITIES?
- 88. WE CAN UNDERSTAND HOW THIS MIGHT BE CODED MODULARLY
- 89. WE CAN ALSO SEE WHERE CONTENT IS USED CONSISTENTLY IN THE SAME MANNER
- 90. HOMEPAGE
- 91. ENTERPRISE PAGE
- 92. TAKE THESE PATTERNS AND MAP THEM
- 104. SO, WHAT ARE WE ACTUALLY DOING HERE WITH THIS?
- 106. DEVELOPMENT PROCESS
- 107. BY IDENTIFYING THOSE CONTENT PATTERNS IN THE DESIGN, WE: Define content with existing design and front-end patterns
- 108. BY IDENTIFYING THOSE CONTENT PATTERNS IN THE DESIGN, WE: Define content with existing design and front-end patterns Flag content that does not fit well within patterns
- 109. BY IDENTIFYING THOSE CONTENT PATTERNS IN THE DESIGN, WE: Define content with existing design and front-end patterns Flag content that does not fit well within patterns Identify content that will be used and updated similarly
- 110. BY IDENTIFYING THOSE CONTENT PATTERNS IN THE DESIGN, WE: Define content with existing design and front-end patterns Flag content that does not fit well within patterns Identify content that will be used and updated similarly Create specs for content field and entry types
- 111. BY IDENTIFYING THOSE CONTENT PATTERNS IN THE DESIGN, WE: Define content with existing design and front-end patterns Flag content that does not fit well within patterns Identify content that will be used and updated similarly Create specs for content field and entry types
- 112. IDENTIFYING COMMONLY-USED DESIGN + CONTENT BLOCKS HELPS INFORM MODULAR DEVELOPMENT OF CONTENT BLOCKS
- 113. CONTENT WORKFLOW MAPS + PATTERNS Helps prioritize development needs
- 114. THIS HELPS CREATE LESS MAINTENANCE OVERHEAD FOR OUR CLIENTS
- 115. WHICH ENSURES A MORE USABLE SITE POST- LAUNCH
- 117. Planning —> Research —> Design —> Development —> Launch —> Maintenance
- 118. Planning —> Research —> Design —> Development —> Launch —> Maintenance
- 119. Planning —> Research —> Design —> Development —> Launch —> Maintenance
- 120. THANK YOU! Natalie Semczuk @talkanatalka natalie@causeeffect.co causeeffect.co talkanatalka.com
- 121. A CASE STUDY
- 122. A LARGE PRODUCT STARTUP NEEDED A MARKETING SITE FOR CLOUD- BASED PRODUCT OFFERINGS
- 123. SITE CONSIDERATIONS AND DISCOVERIES: • Uses Craft CMS • Has strong, clear company branding guidelines • Creates many one-off marketing landing pages • Uses CTA, product marketing, and resource messaging repeatedly throughout the site • Has a content-heavy site, but with new content offerings and a growing marketing plan • Relies on a small team & tight deadlines to administer the site
- 125. WHAT WE STARTED WITH: • Individual pages with specialized fields and elements
- 126. WHAT WE STARTED WITH: • Individual pages with specialized fields and elements • Elements defined per page or channel
- 131. INITIAL IMPRESSIONS
- 133. WE BEGAN CONCEPTUALIZING CONTENT AS A SERIES OF REPEATABLE, FLEXIBLE BLOCKS
- 138. THIS WAS AN ONGOING, AGILE- LIKE PROCESS
- 139. WHY THIS WORKED
- 140. THE RESULT
- 141. SITE IS FLEXIBLE, CUSTOMIZABLE TO ALMOST ALL CONTENT MANAGEMENT NEEDS
- 142. CMS IS BEING EXTENDED WITH ADVANCED DEVELOPMENT TO FURTHER CONTROL CONTENT MANAGEMENT EXPERIENCE AND ORGANIZATION OF CONTENT
- 143. CONTENT MANAGER IS ABLE TO GROW PAGES AND CONTENT WITH COMPANY’S NEEDS
- 144. CONTENT MANAGER CAN SUPPORT MANY NEW MARKETING INITIATIVES
- 145. THE SITE IS NOW SCALABLE FOR ALL OF THE COMPANY’S NEEDS IN THE FORESEEABLE FUTURE
- 146. THIS MEANS THE CONTENT MANAGER IS HAPPY, THE CONTENT MANAGER’S COMPANY IS HAPPY, AND THE WEB DEVELOPMENT TEAM IS HAPPY
- 147. EVERYONE WINS!