WhiteShark5
commented
9 years ago Author: Jeff Cram Blog Post 07/22/2008
Let’s look at some of the essential content building blocks. Web Pages: While we’ve certainly moved to dynamic content delivery, most sites still require a traditional site map with individual pages defined. This is where most CMS content planning starts (and sometimes ends). It’s a critical part of planning, but just the tip of the iceberg. Templates & Layouts: Each page needs a defined template and layout. It’s important to standardize the templates and layouts and map them back to individual page types. This makes the deployment easier, provides consistency in the user experience and allows for a more scalable architecture. There will always be those one-off pages that need custom designs, but they should be just that – one offs. Content Objects: The most critical part of the content planning is modeling your content into what we call content objects. A content object is best defined as a piece of content that has a set structure. Common objects include news releases or events. Defining the attributes and meta data of these objects will increase reuse and provide more flexibility in how they are delivered. Unstructured Content: Content that can’t be organized into objects fall into the unstructured bucket. This is content that would typically be managed directly in a WYSIWYG editor. There’s nothing wrong with having unstructured content, but you do lose a certain amount of flexibility in how it gets repurposed and managed. What’s important is looking for unstructured content that should be structured. Getting it right the first time makes all the difference. Widgets: There’s a lot of talk about widgets these days. For the purpose of CMS planning, we’re defining widgets as discrete pieces of functionality delivered on individual pages. Widgets typically require some custom programming. They may include a sidebar element that pulls the top three related news stories, or one that pulls a featured white paper. A typical website has dozens of them. By defining all the widgets you can re-use them across the site and make them available to other content owners. No need to reinvent the wheel. Applications: Most sites have specific needs that require custom application development or third party integration. There are in-depth functional and technical considerations involved here, but for the sake of our content architecture it’s important to identify them all and understand how they will fit into the site and CMS. In addition to custom application development, this also includes third party tools and services such as analytics, search and CRM. Forms: While every CMS handles form management differently, it’s important to define all of the form types and field attributes. Even smaller websites can have dozens of forms. Standardizing them can eliminate the sprawl and provide sanity down the road. Media Assets: Media includes items such as images, videos and flash assets. These typically get managed in a central media library, but will need to be clearly defined and categorized so the content authors can find and use them. Taxonomy & Meta Data: A taxonomy is a classification system that provides a standard way of organizing, defining and relating content across your site. They can range from extremely simple to very complex depending on the website and organization. However, it’s a business-critical part of the CMS planning to get right. A good taxonomy properly integrated with the CMS can create a site that scales and provides a more relevant user experience for end users.
http://www.cmsmyth.com/2008/07/the-content-building-blocks-of-web-content-management/