IA Summit 2015 presentation Audio available via IA Summit Library: http://library.iasummit.org/speakers/lacey-kruger/ With the rise of responsive design, a content model and a CMS are necessities for any content-rich web presence. Once you’ve designed the front-end user experience, it’s important to consider the content structure that will support your design. Content models define: the underlying structure of each type of content the user experience for content authors and editors within the CMS Luckily, designing a content model is a natural extension of IA for a front-end user experience. In this talk, we'll get into the details of HOW to content model. We'll dissect the content model for a single content type for a nonprofit website. The goals for this content model were: to be adaptive and portable for any device or context to contain a lot of content, yet display it in a simple way a successful user experience for administrators creating and editing the content a delightful user experience for end users of the content In content modeling, there are often multiple approaches you could take so I’ll also cover the alternate models we explored and describe the process that led us to our end result. Session Takeaways Define a content model Evaluate a content item and create a content model based on that item Learn best practices for adaptive content models

1. The Anatomy of a
Content Model
By: Lacey Kruger

2. What is a Content Model?
• A document defining the structureof each content type
and the user experience for content authors and
editors within a CMS

3. Why Content Model?

4. Why Content Model?

5. Why Content Model?

6. Why Content Model?

7. Case Study
The Project
The Design
The Content Model

8. Case Study
The Project
The Design
The Content Model

9. Background
Website Redesign for National Military Family Association
• Moved to a new CMS
• Responsive Design
• Client responsible for developing Sitemap

10. Case Study
The Project
The Design
The Content Model

12. Proposed Solutions
Grandparent
Parent
Child

13. Proposed Solutions
Parent
Child

14. Proposed Solutions
Options Pros Cons
1. Three Content Types
• Grandparent:
Tabbed Content Page
• Parent:
Sectioned Content Page
• Child:
Section
• Simpler authoring
form
• More flexibility
within each
“section”
• Many content items
to manage =
difficult to update
2. Two Content Types
• Parent:
Tabbed Content Page
• Child:
Sectioned Content Page
• Fewer content
items to manage =
easier to update
• Complex authoring
form
• Longer load times
for authors

15. Case Study
The Project
The Design
The Content Model

16. Child Title
Section Title
Parent Title
Section Image
Section Text 1
Parent
Description

22. The Challenges
1. 4,000 character (~500 word) limit on Rich Text fields
2. Request to add 2 additional sections
3. Ability to insert Videos
4. Tabs within Tabs (yikes!)
5. Page with 8 Tabs

23. The Result
The feedback from our staff, volunteers, and users has been
great. It definitely was a learning curve the first week, but
overall has been a major improvement to the organization of
our content.
-NMFA Web Team
“

24. The End!
Rate Me:
http://spkr8.com/s/159231
Contact Me:
lacey.kruger@blackbaud.com
http://www.slideshare.net/LaceyKruger

25. Want More?
• Karen McGrane
– Presentations:
• Adapting Ourselves to Adaptive Content
• Content Strategy for Mobile
– Book: Content Strategy for Mobile
• Sara Wachter-Boettcher
– Book: Content Everywhere