In version 2012, we released Structured Content which introduced a new way for our customers to manage content for websites by allowing them to separate content from presentation. This new feature not only benefits content authors, but developers and designers as well. Content strategy has become more important, allowing organization’s websites to be more content centric. The designers and developers can create complex and highly interactive designs without introducing complexity for the content authors. In SE2013, we added more features to improve the content strategy capabilities and continue to build highly interactive designs and simplified management of content.
To start, we have added multivalued fields. Prior to this enhancement, many content types included multiple fields to represent a multivalued field. Now one field can collect and store any number of a given field type. This made editing of the content less confusing by allowing a single field that can collect multiple values instead of having multiple fields such as field 1, field 2, field 3, etc...
A new link field type was added allowing content authors to select a link to content managed in SiteExecutive or an external URL. This uses our new link selector.
What is content without relationships? Less useful and less interactive! In version 2012, content strategists were able to leverage implicit relationships for relating one piece of content to another. Implicit relationships are very powerful, but sometimes are harder to define. In SE2013, we added explicit (manual) relationships from one content type to another content type. Explicit relationships in the upcoming release provide full relationship capabilities for your content strategy.
Finally, to make content strategy really effective, organizations need the ability for content reuse/integration. What do I mean by that? Content reuse or content integration is a way to build a new content type by leveraging data from another content type. For example: Let’s say you have a content type called “person”. The person content type has data about a person such as name, title, biography, etc... Now you also build a new content type called article and for the author field you are able to select one or more person(s) from the person content type. Now, every time an article is presented to the author (person data), it is also available to present allowing for two content types to be integrated into one. Finally, this content integration strategy is very important for content reuse. What if a person is an author for more than one article? Prior to SE2013, an article content type might have had specific author fields such as name, title, biography. When you create an article, the content author must rekey in the author information. You can see how time consuming this is and what happens if the author biography changes or their title? Again, prior to SE2013, you would have had to change it on each article. With SE2013, the process of linking a person to an article just requires selecting that person and when the person data is updated once it is now reflected on all articles that this person is an author. In relational database design terms, content strategists can now normalize the content for your site and allow for content reuse instead of duplicating content.
We cannot forget about our developers! With SE2013, our developer community can expend structured content presentation with a custom layout container. This means that developers can introduce custom logic that is executed during the layout rendering process and integrated with core content fields and a core container. We also added the ability for developers to introduce some custom management UI with custom tabs to content home.
To learn more about the new structured content enhancements in SE2013, be sure to join us for our upcoming webinar. Register now to reserve your spot.