Uploaded byBlend Interactive
"Making things real: Content strategy for realistic content management" - Confab Intensive 2017
The document outlines a workshop by Corey Vilhauer focused on content strategy and content management systems, emphasizing the need for realistic expectations and effective communication within teams. It discusses the balance between structured content models and creative processes, while addressing the challenges of content creation and management. Key quotes and concepts highlight the importance of understanding user experience, editorial concerns, and the integration of technology in content management.
More Related Content
Similar to "Making things real: Content strategy for realistic content management" - Confab Intensive 2017
"Making things real: Content strategy for realistic content management" - Confab Intensive 2017
- 1. MAKING THINGS REAL A very professionalworkshop by Corey Vilhauer about content strategy and content management systems
- 2.
- 3.
- 4.
- 6.
- 7.
- 8.
- 9. CONTENT MANAGEMENT SYSTEMS ARE NOTTHE PROBLEM WE ARE
- 10.
- 11.
- 12. WE ARE HUMANS. ITIS ROBOTS.
- 13. “There’s a murkyspace between the idea of content and the hard reality of a content management system.” - Deane Barker author, Web Content Management
- 14.
- 15. THE EXPECTATION BARRIER: OR,OUR DREAMS ARE ALREADY DEAD How do we help teams understand the reality of content management, and set expectations accordingly?
- 16.
- 17.
- 18. Content Strategy User Experience/IA Development & Deployment Low Tech/ HighNeed High Tech/ Low Need Marketing/ Communications Executive Stakeholders Editors & Creators
- 19. CONTENT STRATEGY CONTENT CREATION CONTENTMAINTENANCE THESE ARE ALL CONTENT MANAGEMENT
- 20. Article Category Ad Banner TitleShort Title Meta Title Preview Title Header Image Preview Image Image Caption Image Maintenance Body Copy Category Feed Content Break Points Alternate Tags Opengraph Another Ad Banner Editorial Categories Byline Name Date
- 21.
- 22.
- 23. WE STILL KINDOF SUCK AT MAKING OUR WORK SOUND HUMAN
- 24. “…developers should watch forambiguity or inconsistency that will trip up design.” - Eric Evans author, Domain-Driven Design
- 25. When we say: ContentModel We mean: A conceptual term for the collection of content types, attributes, relationships and datatypes in place to accurately describe a logical domain of content. In other words: How pages, blocks, and other content are shaped and work together within the CMS.
- 26. use ur wordspls The Balance of Message and Structure The Priority of the Machine Permanence vs. Flexibility Communicate the Purpose
- 27. THE BALANCING ACT: OR,THE DIFFERENCE BETWEEN “WE CAN” AND “WE SHOULD” How do we balance the rigidity of a content model with the creative flow of a marketing team?
- 28. “If we havelearned anything at all in this century, it is that all new technologies will be put to use, sooner or later, for better or worse, as it is in our nature to do.” - Lewis Thomas author, “Autonomy”
- 29.
- 30.
- 31. “Content modeling isan editorial issue.” - Sara Wachter-Boettcher author, Content Everywhere
- 32.
- 33.
- 34.
- 35.
- 36.
- 37. Pages Home Page Section HomePage Components General Text Page Program Search Undergraduate Graduate School Program Major Directory Directory Bio Faculty Listing Story Stories Student Media Map Home Calendar Event Image Block Video Block Link List Block Program Block Directory Listing Story Media Type Event Accordion Table Carousel Promo Block Academics Block School Listing Faculty Listing Major List Course Catalog Search Results
- 38.
- 39.
- 40.
- 41. MEASURED RESTRICTION: OR, NOTDOING EVERYTHING, ALL THE TIME, EVERY TIME Understanding the budgets we all have to live within - from time, to money, to attention.
- 42. MEASURED RESTRICTION (a thing Imade up)
- 43. STRUCTURED OR OPEN? Howsimilar is this from page to page? What integrations do I need to use? How often does this content change? How many will we create?
- 44. THE SITE MAP CMS-DRIVENVISUAL 1.0- About USD 1.1 - Why USD? 1.2 - Quick Facts 1.3 - Campus 1.4 - Office of the President 1.5 - Mission and History 1.6 - Art and Culture 1.7- Campus Policies 1.8 - Consumer Information 1.9 - Emergency Information 1.3.1 - Visit 1.3.2 - Map and Directions 1.3.3 - About Vermillion 1.3.4 - The Future Campus 1.3.5 - University Police 1.4.1 - Executive Leadership 1.4.2 - Strategic Plan 1.4.3 - Accreditation 1.5.1 - Past Presidents 1.7.1 - Policies 1.7.2 - New Policies & Rev. 1.7.3 - Student Rights/Respons. 1.7.4 - Student Handbook 1.6.1 - Museums and Galleries
- 47.
- 49. EXAMPLE: News Feed Press ReleaseFeed Case Study Feed Article Press Release Case Study +categories +components
- 50. THE BASE SITE (iknow!)
- 51. THE BASE SITE (iknow!)
- 52. The Base Layer TheComponent Layer The Specialized Exceptions
- 53.
- 54. Do we suppress? Dowe require? Do we ignore?
- 55.
- 56. Manual entry? Categorical aggregation? Amix of both?
- 57.
- 58. Category assigned toboth? Explicit relationship? Manual entry?
- 59.
- 60. Can a machinelearn it? Will it make the job easier? Is there an editorial reason to do it?
- 61. BUDGET Entry Development Maintenance Training Highly Structured OpenWYSIWYG High Medium Low Low Low High Medium Low
- 63.
- 64. THE TRANSLATION POINT: OR,WELCOME TO THE MACHINE How do we take our ideas and turn them into a usable web implementation?
- 65. WHAT I LEARNED QAingWEBSITES
- 66. “Editors will circumvent poortools” - Rahel Ann Bailie author, Bridging UX & Web Development
- 67.
- 68. Meta Title Page Title MenuTitle Content Title
- 69. Meta Title Page Title MenuTitle Content Title URL Slug
- 70.
- 71. Set blank alttext field as <img alt=“”>
- 72. Set a headingtag and a heading class in the WYSIWYG.
- 73.
- 74. Meta Title Page Title MenuTitle Content Title URL Slug
- 75.
- 76.
- 78.
- 83. WRITING IS EASY WRITINGFOR THE CMS IS HARD
- 89.
- 90. AND IN CONCLUSION: OR,MY TIME IS NEARLY GONE Does any of this apply to me, and why the you-know-what should I care?
- 91. CONTENT IS NOTART IT REQUIRES STRUCTURE
- 92. “Broken gets fixed. Shoddylasts forever” - Jack Moffett author, Bridging UX & Web Development
- 93. “There’s no APIcall for makeShitUpHere()” - Deane Barker author, Web Content Management
- 94. THANK YOU for making thingsreal The notes and slide deck will be ready SOON, at: www.eatingelephant.com/intensive17