Published on February 15th, 2011 | by Rahel Bailie4
Content typing is, at its basic level, the attributes of specific chunks of content. The technical team may take responsibility for this, but you may end up having to make adjustments or to create re-use models. (It’s my experience that technologists make sweeping assumptions about content re-use that is not particularly appropriate.) My experience is that there is no set notation system, but the integrator will be comfortable with database object definitions, and likely comfortable using that notation.
Here is an example, a news release has standard attributes: a release status (for immediate release), a headline, a city, state, country, and month, day, year, body, organization name, contact information, and an “end” indicator. A content model for a news release could look something like this:
This gives instructions on how the integrators should create the content model, and how content flows. In this example, contact information is not created for each news release, but imported from the contact information in the repository. In that way, a changed phone number or address could be corrected all the way through the site with virtually no extra effort.
For product content, maintenance content, and other technical content, these content genres are quite mature, and have standard content models. It can prove very helpful to learn about the various types of content standards, to ensure that you’re not re-inventing the wheel, and that your content will be interoperable with other content of the same genre.