A discussion of content modeling capabilities and practices across different Web content management systems.

1. “Just put that in the zip code field…” The Ins and Outs of Content Modeling

2. Content management integration and consulting Social networking integration Custom design Sioux Falls, South Dakota http://blendinteractive.com/

3. 6 Evaluation Questions For those of you shopping for a CMS and comparing options. 5 Implementation Tips For those of you implementing or managing a CMS-based Web site.

4. Content Modeling Definition #1 The process of converting logical content concepts into editable, storable, manageable, searchable content objects by breaking them down into smaller pieces and describing their data to your CMS.

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

6. Content Object An XML document A database record

9. Content Fidelity How closely does the content in your CMS resemble the logical content you planned on?

10. Different systems have vastly different content modeling capabilities.Never assume that system X can accurately model your content.

11. Evaluation Question #1 Does your CMS allow content modeling or structuring at all?

12. Why model content at all?

13. Reason #1 Because different content types need to be STRUCTURED differently.

14. Content Structure Between Types

15. Content Structure Between Types

16. Reason #2 Because different content types have to be EDITED and VALIDATED differently.

17. Automatic Form Rendering Content edit form in eZ publish

18. Input Form Validation Canned and custom validation in Ektron.

19. Reason #3 Because different content types have to be DISPLAYED differently.

20. Display Template Assignment Template assignment by Page Type in EPiServer

21. Reason #4 Because different content types have to be MANAGED differently.

22. Content types often act as functional boundaries for: Permissions Workflow Navigation Search

23. URL Pattern Assignments URL pattern assignment based on Content Type in Drupal

24. Permission Assignment Permission assignments by content type in eZ publish

25. Reason #5 Because different content types need to be SEARCHED and ORGANIZED differently.

26. Organization by Content Value

27. Content Type-specific Search Parametric search based a content type in eZ publish

28. Content modeling has its roots in two disciplines: Relational database design Object oriented programming

29. Relational Database Roots Content Type = Table Content Attribute = Field Attribute Datatype = Field Datatype

30. OO Programming Roots Content Type = Class Content Attribute = Field, Property, Attribute Attribute Datatype = Programming Datatype Content Type Inheritance = Class Inheritance

31. Is content management reinventing the wheel?

32. 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….

33. Types, Attributes, and Datatypes

34. 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.

35. Nomenclature Content Type Content Class SmartForm Page Type

36. Content Types Content types in Drupal

37. 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.

38. Nomenclature Attribute Property Field Element

39. Content Attributes Content attributes in eZ publish.

40. Content attributes have datatypes. A datatype restricts the type of data the attribute may hold. This enables validation and processing

41. Datatypes provide: Validation Editing interfaces Computation

42. Attribute Datatypes Content class attributes in eZ publish.

43. Attribute Datatypes Page Type Properties in EPiServer

44. Generic Custom Fields Custom fields in WordPress.

45. Datatypes and Sorting Datatypes tell the system how to treat values while sorting.

46. Common Validation Needs String is required String is numeric String matches a "canned pattern" (email address, SSN, etc.) String matches a regular expression String falls within a list of valid values drawn from somewhere else String is unique to other content Date is in the past/future Date is in a specific range File is of a specific type File is within a specific size range Value X is conditional on Value Y (if one is filled in, the other can’t be blank, etc.)

47. Content Modeling Definition #2 Content modeling is the process of converting logical content concepts into content types, attributes, and datatypes.

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

49. Evaluation Question #2 Does it allow you to structure content through configuration or does it require you to write code or modules?

50. Code vs. Configuration New Content Type in Plone New Page Type in EPiServer

51. Implementation Tip #2 Be careful in re-using content types for logically different content.

52. Futureproofing is the process of designing your content model in such a way that it can be adapted to new situations with a minimum of pain.

53. Implementation Tip #3 To futureproof your content, speculate on and list scenarios in which the content might be used now and in the future.

55. Author

56. Categories

57. Location

59. Implementation Tip #5 Find the right balance. Don’t overstructure your content.

60. Datatypes

61. Evaluation Question #3 What datatypes are available to structure your content?

62. Datatypes are the building blocks of your content.

63. Strings Simple and formatted strings in WordPress

64. Dates Date entry interface in Ektron.

65. Binary Files Binary file upload in Drupal (top) and eZ publish (bottom)

66. Repeating Properties A repeating data table within an Ektron content object. A one-column Matrix datatype in eZ publish.

67. Evaluation Question #4 Can you write your own datatypes or customize existing datatypes?

68. Custom Datatypes Custom datatype in eZ publish

69. Evaluation Question #5 How well does it manage relational content modeling?

70. DISCRETE content modeling is structuring content within a single content object.

71. RELATIONAL content modeling is structuring a content object in relation to other content.Requires a linking datatype or a content tree.

72. Relational Content Modeling Page Link attribute in EPIServer

73. Relational Content Modeling Multiple content selection in EPiServer and Ektron

74. Articles Title Body Author […] Articles Title Body Author […] Content Composition Article Title Body Author […] Articles Title Body Author […] is related to Author First Name Last Name […] Bureau Name […] was written by works for

75. Evaluation Question #6 How well does it handle hierarchical content?

76. Hierarchical Content Publication Issue Section Article Article

77. Content Trees The content folder structure in Ektron A pure content tree in eZ publish

78. Evaluation Question #6 Does it allow any inheritance of content types or values?

79. Content Type Inheritance Movie Review Page Title Body META Keywords META Description URL Studio Director Cast Running Time Star Rating Music Review Page Title Body META Keywords META Description URL Number of Tracks Genre Star Rating

80. Content Type Inheritance Movie Review Page Studio Director Cast Running Time Star Rating Web Page Title Body META Keywords META Description URL Music Review Page Number of Tracks Genre Star Rating

81. Content Value Inheritance With a pure content tree, setting a value at a specific point will cause content “below” that point to inherit the value until overridden by a new value. These content objects will inherit the value applied to “News,” unless they specifically override it.

82. Evaluation Questions Does it allow the structuring of content? Is it via code or configuration? What datatypes are available? Can you write or customize your own datatypes? How well does it handle relational content modeling? How well does it handle hierarchical content?

83. Implementation Tips Think in terms of content types Avoid reusing content types Speculate on the future uses of content Do not combine logical attributes into the same implemented attribute Don’t overstructure your content

84. Blend Interactive http://blendinteractive.com Gadgetopiahttp://gadgetopia.com Content Management and IA Writing http://blendinteractive.com/services/cm/ Twitter “gadgetopia” Email deane@blendinteractive.com