CapitalCamp: Cooking with Content Strategy


Published on

Presented at CapitalCamp, the DrupalCamp for Washington, DC, in July 2011.

What does the burgeoning practice of content strategy mean for the Drupal community? Working with a content strategist can help make the development process smoother and prevent last-minute surprises and frustrations. (“Why aren’t the news stories displaying on the homepage?” “What news stories?” "Who's writing the news stories?")

Using examples including content types, taxonomies, metadata, and backend copy, we talked about how multidisciplinary web project teams can learn one anothers' languages and collaborate to build better Drupal websites.

This beginner-level session was designed to bring together Drupalistas and the people they work with, including clients, site administrators, and non-technical project team members.

Published in: Technology, Business
1 Comment
  • This is a an excellent overview of how content strategy and drupal intersect!
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Mise en place (pronounced [miz ɑ̃ plas], literally "putting in place") is a French phrase defined by the Culinary Institute of America as "everything in place", as in set up. It is used in professional kitchens to refer to organizing and arranging the ingredients (e.g., cuts of meat, relishes, sauces, par-cooked items, spices, freshly chopped vegetables, and other components) that a cook will require for the menu items that he or she expects to prepare during his/her shift.
  • And much more!
  • CapitalCamp: Cooking with Content Strategy

    1. 1. Cooking with Content Strategy<br />CapitalCamp | July 22, 2011<br />#capitalcontent<br />
    2. 2. Who are you guys?<br />Natalya Minkovsky, Senior Strategist & Content Strategy Lead (@hejhejnatalya)<br />John Serrao, Technology Manager (find me in real life)<br />2<br />#capitalcontent<br />
    3. 3. “Content strategy plans for the creation, publication, and governance of useful, usable content.” – Kristina Halvorson<br />3<br />#capitalcontent<br />
    4. 4. “Content strategy is the development of a repeatable process that manages content throughout the entire content lifecycle.”– Rahel Anne Bailie<br />4<br />#capitalcontent<br />
    5. 5. “Content strategy is to copywriting as information architecture is to design.” – Rachel Lovinger<br />5<br />#capitalcontent<br />
    6. 6. 6<br />#capitalcontent<br />
    7. 7. What goes into the strategy?<br />Content: <br />Substance<br />Structure<br />People: <br />Workflow<br />Governance<br />7<br />#capitalcontent<br />
    8. 8. What are we thinking about?<br />Discovery: What is this all about? What are the client’s objectives? What do the users expect? What content exists? What’s missing? What are the CMS requirements?<br />Strategy: How will the content be organized? Where will the content go? Who will develop the content? What is our metadata strategy?<br />Maintenance: How do we keep the content going? How do we ensure consistency? How are we measuring success? <br />8<br />#capitalcontent<br />
    9. 9. Deliverables<br />9<br />#capitalcontent<br />Get your content strategy ingredients in place.<br />Let’s look at a few examples.<br />
    10. 10. 10<br />#capitalcontent<br />Content Inventory (becomes your content migration plan)<br />
    11. 11. 11<br />#capitalcontent<br />Content Audit<br />
    12. 12. 12<br />#capitalcontent<br />User Personas<br />
    13. 13. 13<br />#capitalcontent<br />Content Strategy Brief<br />
    14. 14. 14<br />#capitalcontent<br />Blogging Guide<br />
    15. 15. What does all this have to do with development?<br />15<br />#capitalcontent<br />
    16. 16. 16<br />#capitalcontent<br />
    17. 17. Introducing!<br />17<br />#capitalcontent<br /> logo designed by Steve Fultz<br />
    18. 18. 18<br />#capitalcontent<br />
    19. 19. Card Sorting<br />Instructions: <br />Sort the cards into groupings that make sense to you<br />Aim for 3-5 groupings<br />After you’ve grouped the items, create a name for each grouping<br />19<br />#capitalcontent<br />
    20. 20. 20<br />#capitalcontent<br />
    21. 21. Bam! The Sitemap<br />21<br />#capitalcontent<br />
    22. 22. John Talks About Content Types<br />MAIN IDEA: Content types are really all about metadata.<br />22<br />#capitalcontent<br />
    23. 23. Card Sorting Themes Become Content Types…<br />Cheeses (title, overview, country, strength, hardness, source, price)<br />Beverage (title, overview, type, strength, country, alcoholic? y/n, price, cheeses (node-list))<br />Accompaniment (title, overview, food group, price, cheeses (node-list)) <br />Cheese Plates (title, overview, dietary considerations, cheeses (node-list),beverage (node-list)) <br />23<br />#capitalcontent<br />
    24. 24. Natalya Gets Excited About Content Templates (#wordnerd)<br />24<br />#capitalcontent<br />
    25. 25. Backend Wireframes<br />25<br />#capitalcontent<br />
    26. 26. Front-End Wireframes<br />26<br />#capitalcontent<br />
    27. 27. Wireframe  Spec<br />27<br />#capitalcontent<br />BIG IDEA: A successful front-end wireframe annotated with specs becomes the document of record for the development phase of your project.<br />
    28. 28. Oh, Boy, Taxonomies!<br />What’s the texture of this cheese? <br />What country is this cheese made in?<br />What kind of milk is it made out of? <br />Is it expensive?<br />What are the flavors like?<br />28<br />#capitalcontent<br />
    29. 29. Fun with<br />29<br />#capitalcontent<br />Made from<br />
    30. 30. Let’s Make a Tagging Taxonomy<br />30<br />#capitalcontent<br />
    31. 31. Cocktail Hour<br />It’s time for Q&A<br />And also to eat some cheese<br />Thanks for coming to our session!<br />31<br />#capitalcontent<br />
    32. 32. 32<br />#capitalcontent<br />photo credits: Flickr users wickenden, vissago, Skanska Matupplevelser & xiaming<br />