Content-First Content Management
•
2 likes•1,164 views
This document summarizes the key stages in content management: 1. Wrangling - Discovery of user needs, content audits, cleanup and organizing existing content. 2. Adapting - Designing content templates, workflows, and migration plans to structure content for a new system. This requires designing for content editors as users. 3. Governing - Ongoing governance of content, including training, buy-in, and tools to manage content over time preventing the "Day 2 problem" of content accumulating without management. The overall message is that content requires planning and design throughout the project lifecycle and beyond launch.
Recommended
More Related Content
Similar to Content-First Content Management
Similar to Content-First Content Management (20)
Recently uploaded
Recently uploaded (20)
Content-First Content Management
- 1. Content-First Content Management WordCamp Vancouver 2015 @mandiwise
- 2. CMS
- 3. C
- 4. –Erin Kissane “Hoping that a content management system will replace this kind of human care and attention is about as effective as pointing a barn full of agricultural machinery at a field, going on vacation, and hoping it all works out.”
- 5. Content Is hard • Content takes time • Content is expensive • Content is political • Content often has a legacy
- 6. –Kristina Halvorson “Planning for the creation, delivery, and governance of useful, usable content.”
- 7. External User Needs Access information on starting, growing, or exiting a business Get one-on-one support and expert advice Connect with other local entrepreneurs and opportunities Generate self-sustaining revenue Position itself as a trusted authority and go-to resource for entrepreneurs Fulfill commitments to external funders, partners, and sponsors Business Objectives
- 8. Kick-off IA CS Design Coding Launch Internal interviews Stakeholder meetings Secondary research Project scoping Card sort Data analysis Tree test Sitemap Inventory & audit Content clean-up Metadata clean-up Content templates Workflow design Migration plan Navigation design Wireframes Comp design HTML prototypes Basic theme build Advanced features 3rd-party integrations Cross-browser QA testing Content migration Went live! January 2014 February 2015
- 9. Photo Credit: Dennis Jarvis
- 10. 1. Wrangling 2. Adapting 3. Governing
- 11. Wrangling
- 12. Discovery Tools • Stakeholder meetings • Content inventory / quantitative audit • Qualitative audit • Analytics review
- 15. Messages!
- 19. Adapting
- 20. Work to be done • Content templates • Content and metadata clean-up • Database and admin input structures • Workflow design • Migration plan
- 23. Photo Credit: Jon Worth
- 24. Blobs vs. Chunks
- 25. ≠
- 27. Modularity FTW! • Full-meal deal website realignments are painful and expensive • Modularity helps people take care of their content ecosystem over time • Structured content is re-purposable content
- 31. Photo Credit: Sarah Severson
- 32. Energy Efficiency Energy conservation Energy Saving Save Energy
- 33. Energy Efficiency Energy conservation Energy Saving Save Energy
- 37. Content Editors are Users Too.
- 39. Designing Workflows • User roles • Post statuses • Revisions • Dashboard widgets • Admin columns
- 42. Forget the page. It’s time to C.O.P.E.
- 43. much api WOW very mccue such json so rest
- 44. Governing
- 45. Photo Credit: k rupp
- 46. The “Day 2” Problem
- 47. –Gerry McGovern “A typical CMS is like a digestive system with no capacity to poop.”
- 48. Photo Credit: Walter Parenteau
- 49. Why This Happens • No post-launch plan! • Lack of buy-in and training • Inadequately structured content fields • Tools mismatched to workflow and needs
- 55. Take-Aways • Plans are not strategies • Content first, because it informs all other things • Content requires design • Content editors are users too
- 56. Questions?! Twitter or GitHub: @mandiwise