A Content Management System allows for the ultimate flexibility for publishing your content. Content Architecture Document is the specification to help make that happen.

1. CAD!
Content Architecture Document
By: Dara Pressley
May 5, 2017

2. Page 2/25
What is a CAD
1.
Content
Architecture
Design (CAD)

3. Page 3/25
The CAD
• is how the database is developed
• describes how to create shareable content
• provides content specifications

4. A Content Management System
allows for the ultimate flexibility for
publishing your content. Content
Architecture Document is the
specification to help make that
happen.
Page 4/25

5. The task of creating
the CAD cannot
happen in a Silo.
Teams should
collaborate together
to assure that the
architecture is strong.
Page 5/25

6. A recipe for a database
• A recipe fits into nice recognizable parts:
title, description, ingredients, prep and
cook time.
• Parsing the information correctly into the
CMS can create a rich experience on the
site
⁃ Grocery list can be created from the
ingredients
⁃ Titles and images can be used to create
modules on other pages to drive traffic
⁃ Layouts can be changed for printing or
device optimization
Page 6/25

7. Adding the meta-data
• Tags can be created to drive faceted search
• Categories help to create related recipe links
Page 7/25

8. Properly structured
content allows content to
be shared easily with
other pages and tools
included in meal plan
search results
twitter
Sharable content
Page 8/25

9. Authored
Sta+c
Dynamic
Information architecture
The Architect has to think about
how the information moves
through the site
• What content is authored on the page
• Where dynamic content comes from
• What content is static to the template
Page 9/25

10. Style: Fun
Character: 40
Type: H1
Style: Fun
Character: 180
Type: Text
Content specifications
Specfications
indicate voice and
tone as well as
governace rules
Page 10/25

11. What is this?
The CAD lets us agree
on the nomenclature
that we will use
• Feature
• Hero
• Banner
• Spotlight
• Oasis
Is it a:
Nomenclature
Page 11/25

12. Preparing for
the CAD
2.
Page 12/25

13. Before you begin building
Audience Is it Living?
Ideally, both developers and
content authors will share the
document. However, be
prepared to create a “light”
version that can be used for
just for authors.
Using an online tool, like a wiki,
will allow for easier
collaboration, updating, and
linking between items than a
static PDF.
Page 13/25

14. The example I will be showing
on in the next section shows
the base requirements for the
CAD, and is designed to be CMS
generic.
Page 14/25

15. Building the
CAD
3.
Page 15/25

16. The CAD is divided into sections
• Wireframes
• Page Layouts
• Components
• Global Schema
• Glossary
Page 16/25

17. What do you need to capture
Page 17/25
Different projects have different needs for the type of information
they need to capture.
The type of CMS used may also require different information.
Also, functional specifications can be added so that the CAD is the
only deliverable — instead of both CAD and Specs.
However, if content author’s are part of the audience, that can be
overwhelming.

18. Wireframes
Wireframes define the structure or regions of
the CMS template.
The CAD contents both an index page of
wireframe thumbnails and a detail page.
It’s good list list the page
layouts that use this
template.
01- Home
04 - Right Rail 05 - Left Rail 06- Blog
03 - Fullwidth B02 - Fullwidth A
A - Header
1 - Hero
2 - Page Body
3 - Sidebar
5 - Footer
Blog
Gallery
Meal Plans
Regions Page Layouts
A
1
2 3
B
A
1
2
3
B
Page 18/25

19. Page Layouts
The page layout shows an
example of a page and the
components that would be used
in each region.
Any page level properties or
custom logic would show here as
well.
Layout Name:
Template:
Jira Ticket:
Blog
Template 06
ES - 300
1
2 3
ID
1
2
3
Region
Hero
Page Body
Sidebar
Component
Hero Image
Hero Text
Gallery
Shopping Link
Social Sharing
Featured Chef
Paired Drinks
Linking to your ticketing
system can help with
development tracking
Page 19/25

20. Components
The component section identifies
field level information for each
component.
• Annotated image with markers
for each field.
• Component level meta data
• Field level properties
⁃ (next slide)
1
2
Component Name Gallery
Template Template 06
Jira Ticket ES-304
Page 20/25

21. Components (Gallery)
ID Field Name Field Type Authored Required Content Specs Container/Schema Is Searchable Comments
A Gallery Gallery ItemMulti-valued Dynamic Yes
ID Field Name Field Type Authored Required Content Specs Container/Schema Is Searchable Comments
1
2
Gallery
Image
Gallery
Text
Recipe: Image
Recipe: Title
Recipe URL
Link Schema
Image
Link Text
Dynamic
Dynamic
Yes
Yes
Gallery
Gallery Item
Page 21/25

22. Components (Recipe)
ID Field Name Field Type Authored Required Content Specs Container/Schema Is Searchable Comments
1 Title Character: 160H1 Authored Yes Yes
3 Description Rich Text Authored Yes Yes
6 Save “Save this recipe” Recipe: Title
Schema: Link Text
Text Link Dynamic Yes
7 Add to List “Add recipe to
shopping list”
Recipe: Ingredients
Schema: Link Text
Text Link Dynamic Yes
8 Prep Time Input in minutesInteger Authored Yes
9 Cook Time Input in minutesInteger Authored Yes
10 Serving Size Integer Authored Yes
11 Ingredients
Label
“Ingredients”Text Static Yes
12 Ingredients Array Authored Yes List needs to be written in a
way that information can be
parsed for shopping list.
Also, links to other recipes
needs to be available
13 Directions Rich Text Authored Yes
14 Category Multi-valued Authored Yes Schema: Categories Author selects from list
15 Tags Multi-valued Authored Yes Schema: Tags
Author selects from list.
Author can add new.
16 Short Description Text Authored Yes Character: 120 Used for social sharing
2 Image Image Authored Yes image fits to
100% of
container
4 Allergens
Label
“Free of:”Text Static No If there aren’t any
allergens, field does not
display
5 Allergens Schema: AllergensMulti-valued Authored No Author selects from listYes
Page 22/25

23. Schemas
Schemas are created for often
used field groups. For
example, link text or
categories.
Using the schema assures that the author is
including the right information each time they
use one of these fields.
All global schemas can be listed on one page in
the CAD
Schema Name Link Text
Description Used to create links
Root element name link_name
Schema Type
Field Name Description Field Type Required Multi-value
url URL link Text Yes No
text Text of link Text Yes No
alt Alternative text Text Yes No
Content Schema
Schema Name Allergen
Description Used to show whether an allergen is in or is absent
Root element name allergens
Schema Type
Field Name Description Field Type Required Multi-value
id Number of allergen Integer Yes No
name Name to display Text Yes No
icon Icon to display Icon Yes No
include Indicates that
allergen is present
Toggle Yes No
Taxonomy Schema
Page 23/25

24. Glossary
The last section of the CAD is
the glossary.
There are two types of glossaries:
1. The CAD glossary identifies the meaning of the CAD based terminology.
2. The glossary of terms specifies nomenclature for the particular project.
Page 24/25

25. Thanks!
Any questions?
You can find me on twitter: @uxdiva