Overview
============
In practice, you will find that most CMSs are not usually devoted to managing only
application content or even a combination of information and application content. In most
cases, CMS software developers focus on information management only and let other
software developers build tools, such as source code management systems, to handle
the application content.
With that said, many high-end, high-priced, commercial CMSs support the allencompassing
definition of content. Vignette and Interwoven are two such CMS
systems. They both support practically any type of information content that can go on a
Web site, as well as deployment of any custom applications. An interesting note about
these CMSs is that they offer the application content management system as an add-on
package. So, it appears that even they see the distinction between the two types of
content.
Yet still, in light of all this, there is evidence that the industry is in the process of trying to
merge all niches of CMSs together, bringing both information and applications under the
same umbrella. The question is whether this merging will make CMSs all-encompassing
or just create a large, integrated tool that handles all aspects of Web page development
for which CMS is just one part.
I would hazard to guess that it is the latter because it would contradict the efforts of the
rest of the industry, which is trying hard to do the exact opposite (that is, keep
information and applications separate). Web site developers consciously make an effort
to try to separate applications and information whenever they build systems. In fact,
developers recommend that while using .NET, HTML (information) and the programmed
functionality (application) should be in separate source code files.
============
In practice, you will find that most CMSs are not usually devoted to managing only
application content or even a combination of information and application content. In most
cases, CMS software developers focus on information management only and let other
software developers build tools, such as source code management systems, to handle
the application content.
With that said, many high-end, high-priced, commercial CMSs support the allencompassing
definition of content. Vignette and Interwoven are two such CMS
systems. They both support practically any type of information content that can go on a
Web site, as well as deployment of any custom applications. An interesting note about
these CMSs is that they offer the application content management system as an add-on
package. So, it appears that even they see the distinction between the two types of
content.
Yet still, in light of all this, there is evidence that the industry is in the process of trying to
merge all niches of CMSs together, bringing both information and applications under the
same umbrella. The question is whether this merging will make CMSs all-encompassing
or just create a large, integrated tool that handles all aspects of Web page development
for which CMS is just one part.
I would hazard to guess that it is the latter because it would contradict the efforts of the
rest of the industry, which is trying hard to do the exact opposite (that is, keep
information and applications separate). Web site developers consciously make an effort
to try to separate applications and information whenever they build systems. In fact,
developers recommend that while using .NET, HTML (information) and the programmed
functionality (application) should be in separate source code files.
Reading this really helped. Hope you continue this gud works
ReplyDeleteThanks for explaning us about what is Content management system ?.However, we provide a customised Content management system in India.
ReplyDelete