Hello! I had been back for a long time. Honestly, there is another assignment from my lecturer so I'll start to write some articles again. Now on, I'll give you some concepts of content management. I got them from some sources.
1. Source : Wikipedia
A content management system (CMS) allows publishing, editing, and modifying content as well as site maintenance from a central page. It provides a collection of procedures used to manage work flow in a collaborative environment. These procedures can be manual or computer-based.
Main features : Allow for a large number of people to share and contribute to stored data; Control access to data based on user role (i.e., define information users or user groups can view, edit, publish, etc.); Facilitate storage and retrieval of data; Control data validity and compliance; Reduce duplicate inputs; Simplify report writing; Improve communication among users.
In a component content management system (CCMS), content is stored and managed at the sub-document or sub-component level for greater content reuse. CCMS has five main functions: Maintaining Security, Managing Objects, Managing Servers, Managing Auditing, and Maintaining Reports.
2. Source : The Journal of Electronic Publishing (JEP)
The term Content Management System is the most straightforward of the various labels that attempt to describe a comprehensive solution. There are several components :
1. Data repository : also called a database, the data repository is the organization of the content to facilitate access, updating, and re-distribution.
2. User interface : the set of screens used to interact with the data make up the user interface.
3. Editorial tools : word processors and SGML editors are key components of most CMS solutions.
4. Workflow scheme : with a CMS, we always know what is happening with any given component of the content.
5. Output utilities : the output utilities are filters that take information in the data repository and format it for various publishing media.
3. Source : Intentional Design Inc.
Content Management is technology that controls content at various stages through the content lifecycle to support a business goal.Choosing a CMS from a basic framework, there are : Contextual choice, Meet requirements, and Strategic adoption. Role of publishing engine, download peripheral tasks: Font assignment, Pagination, Table of authorities, Formatting, and Graphics manipulation. Where do we fit in the content management picture?
1. CMS suitable for technical documentation is considered a nice market
• At last count, thousands of WCM vendors • About a dozen vendors for …
2. “Segment with no name”: XCMS
• Structured content software • Dynamic publishing software • Multi-channel publishing software • Globalization solutions software • Content component management
1. CMS suitable for technical documentation is considered a nice market
• At last count, thousands of WCM vendors • About a dozen vendors for …
2. “Segment with no name”: XCMS
• Structured content software • Dynamic publishing software • Multi-channel publishing software • Globalization solutions software • Content component management
4. Source : IBM Lotus
Content Management Concepts
You use Web Content Management to develop, manage and deliver Web content in the form of Web pages and portlets. To create and manage a Web content system you will need to understand the features and items that make up a Web content system and how they fit together.
Content administration functions : content administrator will need to maintain Web content libraries, user roles, syndication relationships and external feed configurations.
Web site design features : the initial design and creation of your Web content management system is built on a development server. Once your system is complete, the development system is then used to create and test updates to your system.
Item management features : Web Content Management includes a range of features that enable you manage the Web content items used in your system.
Web content creation features : After designing and building your Web Content Management item you can start creating content in the form of components and elements.
Web content authoring interface strategies : The primary role of a Web content authoring system is to allow your content creators to author content in the form of content items. There are various features you can use to customize the Web Content Management user interface to simplify the content authoring process for your content creators.
Web content delivery methods : The type of delivery method you use to delivery Web content you your viewers will depend on the type of content being delivered, and the type of viewers your Web site is intended for.
5. Source : Asilomar Institute for Information Architect
WHAT IS CONTENT MANAGEMENT ?
>>>>> start by entering content and metadata using an authoring template
Then the content ("Product Name" which is in yellow bar ) is published into the right spot in the publishing template )
6. Source : Kaveh Ahmadi
Content is the concept of : structured vs. unstructured data and Data vs. Content
Structured data fits neatly into well-defined buckets. “unstructured” data, which does not fit so predictably into welldefined buckets, has become known as “content”.
Content and Industry :
1. Commercial Airlines (aircraft maintenance manuals(
2. Automotive (dealer service manuals)
3. Insurance (insurance policies, insurance claims)
4. Public Utilities (utility contracts)
5. Banking and Financial Services (loan applications)
6. Healthcare (medical transcriptions, electronic patient records)
7. Telecommunications (network and wiring diagrams)
8. Pharmaceutical (new drug applications, clinical research data)
9. Legal Publishing (court records, legal briefs)
10. Government (birth certificates, public health records, committee reports, legislative transcripts and calendars)
7. Source : ACM Digital Library
Content delivery is rapidly emerging as a complex systems domains concerned with multi-channel, multi-format publication of information across user and application domains. a variety of content management solutions have been developed in response to these challenges based on, not only differing technologies, but also heterogeneous approaches. However, none of these present a solution that is both sufficient and consistent.
8. Source : Daisy (http://its.ucsf.edu/its-wiki/daisy/47-DSY.html)
What is a Content Management System?
A content management system is a computer software system for organizing and facilitating collaborative creation of documents and other content. The software manages content (text, graphics, links, etc.) for distribution on a web server. Usually the software provides tools where users with little or no knowledge of programming languages and markup languages (such as HTML) can create and manage content with relative ease of use. Most systems use a database to hold content, and provide templates for a presentation layer which displays the content to regular website visitors. Access to the CMS is typically made through a web browser, but some systems may be modified in other ways.
Content Management is used to refer to a range of technologies and techniques, including portal systems, wiki systems, and web-based groupware.
9. Source : OpenStructs (TechWiki)
Document Management Concept
Document management, most often based on a document management system (DMS), is the use of a computer system (or set of computer programs) to track and store electronic documents and/or images of paper documents. The term has some overlap with the concepts of content management systems. It is often viewed as a component of enterprise content management (ECM) systems and related to digital asset management, document imaging, workflow systems and records management systems.
10. Source : Contao Factory
General Content Management System Concepts
Static vs. Dynamic
To understand what a CMS is trying to achieve and why it kicks butt, you need to understand a little bit about what happens when you browse to a website and that site pops up in your browser. While there is a lot of complicated stuff that actually happens, it really boils down to some server sending your browser a text file that contains instructions on how it should look and act, written in a language called HTML (HyperText Markup Language). This file can contain text content, plus references to images, movies, stylesheets, Javascript, etc, and your browser reads the instructions in that file to generate a web page. This is what is referenced when you bring up a URL in your browser: http://www.mysite.com/myfile.html. Easy enough of a concept, right?
Now, someone has to write those HTML files. The most basic way to create them, and the way that most web designers/developers originally learned, is to simply code them all by hand, one by one. You would create one static file for each page on your website... one for your home page, one for your about page, etc. You can see how all those pages would add up with a 200-page website. It also becomes a nightmare to add something like a navigation menu item, or change the name of the page, because you would need to change every reference to that item/page on every single page on your site.
A static HTML file delivered to your browser.
One early solution to this (which is still used today in some cases) was to use what are called "server-side includes." This involves using a simple tag that "includes" another text file along with the current file you are using. So instead of having 200 instances of your navigation HTML you simply write one and "include" it in all your pages. So for example, if I wanted to contain my main navigation all in one file and simply include it in my other files so that I would only need to update one file instead of 200:
An HTML file delivered to your browser using server-side-includes (SSI).
This is start of the creation of "dynamic" websites rather than "static" HTML websites. It enables the updating of content in a source other than the file that is called, and the eventual HTML output takes place "server-side" before it gets to your browser. This means that the text file is delivered to your browser after having gone through some processing on the server end, all in the blink of an eye, and that by changing the content of your include files you can change the content on your entire website, rather than on each individual HTML page. You can see how by making the server do a little preprocessing of your files that it makes things easier for the developer.
However, there is an inherent problem with simply using SSI. There still needs to be a physical file created to represent each individual page on your site, and chances are that in order to do any sort of major layout update you are going to need to update every single one of those files. Also, while the pages are technically "dynamic" in the sense that they are the result of some server preprocessing, they are still very static. In order to make them truly dynamic, you need the server to be able to do a little more work than simply combine static files together. That's where dynamic scripting languages come into play.
However, there is an inherent problem with simply using SSI. There still needs to be a physical file created to represent each individual page on your site, and chances are that in order to do any sort of major layout update you are going to need to update every single one of those files. Also, while the pages are technically "dynamic" in the sense that they are the result of some server preprocessing, they are still very static. In order to make them truly dynamic, you need the server to be able to do a little more work than simply combine static files together. That's where dynamic scripting languages come into play.
Content & Layout
So the next step in the evolution of a true CMS is to separate the content from the layout itself. Why? Well, first of all, imagine the scenario described above, where you needed to do a major layout update to a site. There's a lot of individual pages to update and edit.
Finally, there are 10 concepts from 10 sources. Hope it will be useful for you. :)
