1.
Content Types<br />The Building Blocks of Your Content Model<br />

2.
Content management integration and consulting<br />Sioux Falls, South Dakota<br />http://blendinteractive.com/<br />

3.
@gadgetopia<br />

4.
7 Reasons…<br />…why content typing is important<br />4 Evaluation Questions<br />For those of you shopping for a CMS and comparing options.<br />3 Implementation Tips<br />For those of you implementing or managing a CMS-based Web site.<br />

5.
Content Modeling<br />

6.
Definition<br />Content modeling is the process of converting logical content concepts into content types, attributes, and datatypes.<br />

7.
Logical Content<br />This is the desired end result of a content management requirement.<br />It’s often represented as a design comp.<br />

8.
Content Object<br />An XML document<br />A database record<br />

9.
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.<br />

10.
Content Item A is a page of text.<br />Content Item B is an Executive Profile.<br />Content Item C is a Press Release<br />

11.

12.

13.
Structuring your content requires you to identify your content types.<br />

14.
Why care about content types?<br />

15.
Reason #1<br />Because different content types need to be STRUCTURED differently.<br />

16.
Content Structure Between Types<br />

17.
Content Structure Between Types<br />

18.
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.<br />

19.
Content attributes have datatypes.<br />A datatype restricts the type of data the attribute may hold. This enables validation and processing<br />

20.
Content Model<br />Content Types<br />Content Attributes (bound by Datatype)<br />

21.
My Web Site<br />Standard Text Page<br />Press Release<br />Executive Profile<br />

22.
My Web Site<br />Executive Profile<br />First Name (simple string)<br />Last Name (simple string)<br />Hire Date (date)<br />Image (file reference)<br />Bio (formatted string)<br />

23.
Reason #2<br />Because different content types have to be EDITED and VALIDATED differently.<br />

24.
Automatic Form Rendering<br />Content edit form in eZ publish<br />

25.
Input Form Validation<br />Canned and custom validation in Ektron.<br />

26.
Reason #3<br />Because different content types have to be DISPLAYED differently.<br />

27.
Display Template Assignment<br />Template assignment by Page Type in EPiServer<br />

28.
Reason #4<br />Because different content types have to be MANAGED differently.<br />

29.
Content types often act as functional boundaries for:<br />Permissions<br />Workflow<br />Navigation<br />Search<br />

30.
URL Pattern Assignments<br />URL pattern assignment based on Content Type in Drupal<br />

31.
Workflow Assignment<br />Automatic workflow initiation in EPiServer.<br />

32.
Reason #5<br />Because different content types need to be SEARCHED and ORGANIZED differently.<br />

33.
Organization by Content Value<br />

34.
Content Type-specific Search<br />Parametric search based a content type in eZ publish<br />

35.
Reason #6<br />Because different content types are markers for integration complexity.<br />

36.
The Ubiquitous “Standard Page”<br />

37.
A new content type often means…<br />A new editing interface<br />New validation rules<br />New permissions rules<br />New workflow requirements<br />New display requirements<br />etc…<br />

38.
Reason #7<br />Problems due to inefficient and inaccurate content modeling will often not surface until the project is complete.<br />By that point, it’s often too late….<br />

39.
Futureproofing<br />Designing your content model so it can be adapted to new situations with a minimum of pain.<br />

40.
Evaluation Question #1<br />Does your CMS allow content modeling or structuring at all?<br />

41.
Evaluation Question #2<br />How flexible are its content modeling capabilities?<br />(Bring your own content, and ask for a demonstration of how it would be modeled.)<br />

42.
Evaluation Question #3<br />What datatypes are available to structure your content?<br />

43.
Evaluation Question #4<br />Can you write your own datatypes or customize existing datatypes?<br />

44.
Implementation Tip #1<br />Think in terms of content types. Consider the ways different content will need to be edited, validated, managed, searched and organized.<br />

45.
Implementation Tip #2<br />Be careful in re-using content types for logically different content.<br />

46.
Implementation Tip #3<br />To futureproof your content, speculate on and list scenarios in which the content might be used now and in the future.<br />

47.
Blend Interactive<br /> http://blendinteractive.com<br />Gadgetopiahttp://gadgetopia.com<br />Twitter<br /> @gadgetopia<br />Email<br />deane@blendinteractive.com<br />