Challenges of Designing for a CMS

Transcript

1. Damn you CMS! Challenges of designing for a CMS
2. Front-End Developer @duncanjimbo
5. “Programming is a design activity” Jack W. Reeves
6. What challenges?
7. 1. Content 2. Technology 3. People 4. Visual Design
8. Content first.
9. …a program that enables a company to collaboratively edit and publish content.
10. “Content precedes design. Design in the absence of content is not design, it’s decoration” Jeffrey Zeldman
11. “…a plan for adding unique, expert, and indexable content to your site on a regular basis.” Mark O’Brien
12. • You need real content to know how long certain fields should be • You need real content to see how tables expand or contract • You need real content to know what your app truly looks like
15. Choosing a CMS.
16. It is not about features.
17. 1. Derive a content model from your content strategy 2. Determine publishing tasks
18. 1. Can this tool handle our content model? 2. Can it do so natively or will it need customization? 3. How much customization will be required to implement our task flow? 4. How long will that take given the available technical resources?
19. Identifying users.
20. Who are we designing for?
21. “…a great, flexible and easy to use CMS is only one person away from being transformed into a completely unusable and frustrating or empowering and strategic CMS.” Seth Giammanco
24. Visual design.
25. Get to know the tool you are designing for!
28. Think in terms of components
29. “…A full comp often requires ideas to be fully realized… An element collage allows me to document a thought at any state and move on to the next.” Dan Mall
31. The future of CMSes.
32. Instant Articles
34. Create One Publish Everywhere http://goo.gl/VcW8NN
35. 1. Build content management systems (CMS), not web publishing tools (WPT) 2. Separate content from display 3. Ensure content modularity 4. Ensure content portability
36. Thank you. @duncanjimbo