Content Last: A Strategy for Success or Failure?
•Transferir como PPTX, PDF•
0 gostou•838 visualizações
The document discusses how content is often an afterthought in website development projects, with the site being built first and content added later. However, this approach usually leads to problems like design bugs, incorrect content structure, and delays. Instead, the document argues for a content-first approach where content creation is scheduled from the beginning of projects and sample content is developed during design phases. Developing real content throughout the process helps ensure the design and development work considers actual usage scenarios and avoids rework.
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (13)
Semelhante a Content Last: A Strategy for Success or Failure?
Semelhante a Content Last: A Strategy for Success or Failure? (20)
Mais de Brian McKeiver
Mais de Brian McKeiver (15)
Último
Último (20)
Content Last: A Strategy for Success or Failure?
- 1. Content Last: A Strategy for Success or Failure? Brian McKeiver
- 3. #404conference The Fundamental Issue Most organizations think the site can be built first, and then when ready, content can be slammed in at the end. It just can’t be that hard right?
- 7. #404conference RWE #1 Grids • Design looks great right? • Nice stacked columns • Uniform / Symmetrical
- 8. #404conference Real Content Happens • Too much / too little text • Missing icons • Incorrect height
- 9. #404conference RWE #2 - Articles • Reading Time • Audio Summary • Multiple Tags • Nice long headline
- 10. #404conference There’s a Bug! • Why wasn’t the design followed? • Way too much white space • Too many tags • Where is the Audio summary?
- 12. #404conference Fail Open Graph doesn’t like a 302 redirect
- 13. #404conference The Solution • When matters • How matters • And of course Quality matters
- 14. #404conference Have a Plan up Front • Before the Design phase starts, your content work starts. • Use real content always in all phases of your projects
- 15. #404conference Schedule Content Creation It helps to have real content from many perspectives: • Developers • Designers • PM, QA, Stakeholders We tell our clients we need 3 real pieces of content before a sprint starts
- 17. #404conference 0 2 Project Planning Sprint 2 - Product Category Landing 3 Sample Categories 3 Sample Products All Categories All Products Sample Schedule Sprint 1 - Product Detail 1
- 20. #404conference Structured Data for Social • Not an after thought • Use Smart Defaults • Make it smart not stupid
- 21. #404conference Use a Content Inventory Set due dates on content, otherwise it will not happen
- 22. #404conference Who wins Content First • Scheduled • Helps entire project team stay on the same page • Avoids project delays • Thoughtful content hierarchy / relationship Content Last • Causes development re-work • Last minute • Work effort always under estimated • Causes delays • Adds un-needed stress • Meta tags normally missed • Social is an after thought
- 23. #404conference One last thing to think about Content is part of the experience we deliver - It’s not separate. So why wait till the end?
- 25. #404conference Brian McKeiver Co-Owner, BizStream Phone: (616) 481-1631 Email: bmckeiver@bizstream.com @mcbeev www.linkedin.com/in/brianmckeiver www.mcbeev.com
Notas do Editor
- All content is not created equal Designs will change based on content Implementation will change based on content Content will change based on content
- We’ve all seen this Designers make it look pixel perfect, beautiful, fantastic, superb… It’s their job right?
- Stop waiting till the end!
- Just like development sprints are scheduled with features, Content should also be in that same schedule