Content Types: The Building Blocks of Your Content Model

Post on 08-May-2015

3691 Views

Category:

Technology

2 Downloads

Preview:

Click to see full reader

Transcript

Content TypesThe Building Blocks of Your

Content Model

Content management integration and consulting

Sioux Falls, South Dakotahttp://blendinteractive.com/

@gadgetopia

4 Evaluation Questions

For those of you implementing or managing a CMS-based Web site.

For those of you shopping for a CMS and comparing options.

3 Implementation Tips

7 Reasons…

…why content typing is important

Content Modeling

Definition

Content modeling is the process of converting logical content

concepts into content types, attributes, and datatypes.

Logical Content

This is the desired end result of a content management requirement.

It’s often represented as a design comp.

Content Object

An XML document

A database record

Content on most Web sites can be roughly categorized by type.

A type shares a common set of attributes and is meant to represent a single, logical boundary around content.

Content Item A is a page of text.Content Item B is an Executive Profile.Content Item C is a Press Release

Structuring your content requires you to identify

your content types.

Why care about content types?

Reason #1

Because different content types need to be STRUCTURED

differently.

Content Structure Between Types

Content Structure Between Types

Content types are made up of content attributes.

An attribute is a single, logical piece of information that, when combined

with other attributes, describes a type of content.

Content attributes have datatypes.

A datatype restricts the type of data the attribute may

hold. This enables validation and processing

Content ModelContent Types

Content Attributes (bound by Datatype)

My Web SiteStandard Text PagePress ReleaseExecutive Profile

My Web SiteExecutive Profile

First Name (simple string)Last Name (simple string)Hire Date (date)Image (file reference)Bio (formatted string)

Reason #2

Because different content types have to be EDITED and VALIDATED

differently.

Automatic Form Rendering

Content edit form in eZ publish

Input Form Validation

Canned and custom validation in Ektron.

Reason #3

Because different content types have to be DISPLAYED differently.

Display Template Assignment

Template assignment by Page Type in EPiServer

Reason #4

Because different content types have to be MANAGED differently.

Content types often act as functional boundaries for:

PermissionsWorkflowNavigationSearch

URL Pattern Assignments

URL pattern assignment based on Content Type in Drupal

Workflow Assignment

Automatic workflow initiation in EPiServer.

Reason #5

Because different content types need to be SEARCHED and

ORGANIZED differently.

Organization by Content Value

Content Type-specific Search

Parametric search based a content type in eZ publish

Reason #6

Because different content types are markers for integration

complexity.

The Ubiquitous “Standard Page”

A new content type often means…

A new editing interfaceNew validation rulesNew permissions rulesNew workflow requirementsNew display requirementsetc…

Reason #7

Problems due to inefficient and inaccurate content modeling will

often not surface until the project is complete.

By that point, it’s often too late….

Futureproofing

Designing your content model so it can be

adapted to new situations with a minimum of pain.

Evaluation Question #1

Does your CMS allow content modeling or structuring at all?

Evaluation Question #2

How flexible are its content modeling capabilities?

(Bring your own content, and ask for a demonstration of how it

would be modeled.)

Evaluation Question #3

What datatypes are available to structure your content?

Evaluation Question #4

Can you write your own datatypes or customize existing datatypes?

Implementation Tip #1

Think in terms of content types. Consider the ways different

content will need to be edited, validated, managed, searched and

organized.

Implementation Tip #2

Be careful in re-using content types for logically different

content.

Implementation Tip #3

To futureproof your content, speculate on and list scenarios in which the content might be used

now and in the future.

Blend Interactivehttp://blendinteractive.com

Gadgetopiahttp://gadgetopia.com

Twitter@gadgetopia

Emaildeane@blendinteractive.com

top related