Archive for the ‘CMS’ Category
Content Management Systems - allows more people to contribute contents and manages web site without having to deal with the technical aspects of web design.
Generally CMS is classified as ECMS & WCMS.
- Enterprise content management systems - manage the content/documents related to the organization.
- Web content management systems - manage and publish the content to website or mobile devices.
I’ve not worked much on enterprise content management systems. So I’m listing the details of only WCMS.
Web Content Management System
- Presentation layer displays the content based on templates.
- Provides browser-based interfaces
- Even non-technical users can manage contents
- Automated templates
- Easily editable content
- Workflow management
- Content Targeting
- Document management
- Content syndication
- Scalable feature sets
- Database driven
- Separate design and content.
- Use CSS to control site
- Access from anywhere
- Web site management panel
- Schedule content updates
- HTML knowledge not required
- Create automatic RSS Feeds.
- Storage Volume
- Limited flexibility in design
- Limited SEO of web pages
- Performance Issues
- Maintenance costs
All these details are taken from various web links.
My colleage adviced me to get better understanding about the content lifecycle if we want to become CMS professional. To be honest, I’ve been searching some materials about all phases but finally I end up with not much clarity. So many people are suggesting variuos phases.
Finally I understand all are pointing similar things but categoried into granular levels. As I’m working in Tridion project, I could compare each phases with their definitions and I agreed with following 7 phases.
I didn’t detail each phase as I don’t know to elaborate these things :). Please refer CMS Seven Stages to know more details.
Here are other references for better understanding…
Process of managing the contents through its lifecycle -from creation, review, storage and publish to expiration. Here the content could be of plain text or any file types (such as doc, jpg etc.) which needs to be managed.
Mostly, the content will exist as an independent component from the presentation.
Why Content Management
Before we step into further, we need to understand why we need content management. There are many but I’m taking only the very basic reason for the need of Content Management.
In traditional applications, developers will create user interfaces and business users will provide the contents. But the problem is that Business users can not add or edit their contents directly as they are integrated with user interface. This will require them to have technical knowledge to edit their contents. Hence the contents will be provided to developers and they will put it on the pages for publishing.
There is a complete dependency over content publishing. Due to this process, there will also be a delay in content updates on the websites.
In CM, since the contents are not integrated with user interface, Business users can directly add the contents without having much technical skills. Also they can publish their contents directly for approval. So the dependency can be avoided and content updates also can be faster.
The advantage of content management is each action its lifecycle can be performed by one or more users, which are independent from each other.
Content Management is useful,
1) If you are changing the website content frequently
2) If you need a workflow process for approvals
3) If you need to schedule a content to publish/archive/expire
4) If you need to get your older version of contents.
The below are the basic roles of CM process. These can be classified to further according to business requirements like US Content Creator, UK Content Creator.
Creates and Edits the content
Manages the contents like formatting, adding hyperlinks.
Reviews the contents
Reads the contents after they are published.
Administrates all contents like managing access controls to files and folders.