What can CMS contain?
A content management system usually has the following elements:
-H4c. U/N; @ & U-_ (L document template, script language or markup language, integration with database tech.techweb.com.cn + T % {1G $ D9]
The content inclusion is controlled by the special mark of the inner embedded page. These tags are usually unique to a content management system. These systems generally have support for languages with complex operations, such as Python, Perl, or Java.
5p8 ^-o "'' z r ,? The 8e content management system is good for site management and creation and editing. The biggest benefit of this is the ability to use templates and general design elements to ensure the coordination of the entire website. The authors only need to use a small amount of template code in their documents, and then they can focus on the content above the design. To change the appearance of a website, the Administrator only needs to modify templates instead of individual pages.
-C "i0d1 ~ 3 ~. The R. y4' content management system also simplifies website content supply and content management responsibility delegation. Many content management systems allow different levels of access permissions to users at different levels of the website, so that they do not have to study the operating system-level permission settings, but simply use browser interfaces.
'Z5u9v, X; p7k. l0b5x other features, such as search engines, calendars, and Web emails, are also placed in the Content Management System CMS, or can be integrated as third-party plug-ins. Techweb-Technical Community & I1/1t' r5i7g/V) j
How to Develop CMS: The content management system is a general concept: from the commercial portal website's news system to the personal weblog, it can be called a publishing system. Tech.techweb.com.cn % r2t5b8j % ?. {
Framework: it does not contain any application implementation. It only provides the underlying framework. A specific application requires secondary development, such as cocoon and vignette;
. _ 5q2t "W (K! U % C $ p8t. P. | application: it is an application implementation oriented to specific types. It already contains subsystems such as news/Comment management, voting, forum, and Wiki. For example: PostNuke xoops; 4b7d U) f8u) H4}
However, in any case, before selecting a release system, it is most important to first understand your actual needs: it is very undesirable to try to copy your needs from the ready-made system. Access volume, permission control, and various functional requirements. After each module and function is clearer, you can find a similar implementation on the Internet: you will find that every step has been developed and developed, it is still in progress and development. If you do not have: Your requirements are too special, or you can try to break them down into smaller system combinations for implementation.
+ A * l (Z-/+ s '~ 1y0b! T
The content management system is separated into the following layers: different levels have different priorities.
. Q, t0b2 _; A * J5 P tech.techweb.com. cn8n; k, ["j5u
1. Background business Subsystem Management (Management first: Content Management): News entry system, BBS Forum subsystem, full-text retrieval subsystem, etc. It is convenient for managers to enter content in different systems: WYSIWYG editing management interface and clear business logic: Permission control mechanisms of various subsystems;
2R) Z2? "N, N! Ytech.techweb.com. cn2, portal system (performance first: Template management): Most of the final output pages are website homepage, subchannel/topic page, and the news details page is generally a combination of various background subsystem modules, this combination of publishing logic is very rich. The portal system is responsible for managing the combined performance of these background subsystems; program development, operating systems, servers, source code downloads, Linux, UNIX, BSD, PHP, Apach, ASP, download, source code, hacker, security, technical community, Technical Forum 't,] 6q/k7p7w5y
3. frontend release (Efficiency First: release management): cache release for end users, and URL Design for search engine spider ...... Program Development, operating system, server, source code download, Linux, UNIX, BSD, PHP, Apach, ASP, download, source code, hacker, security, technical community, Technical Forum, P. v-f9x (A * x2c "Q: Q
Separation of content management and performance: Many complete sets of CMS systems do not separate various backend subsystems and portals, so that the template performance management on the portal layer is mixed with the content management logic of the news subsystem, and even the management of the BBS and other subsystems are very coupled, the entire system will appear very complex. In addition, the various subsystems of such a system are bound to death, and it is difficult to change the background module. However, if the content management logic of various subsystems in the background is separated from the performance/release of the foreground, there is only a data transfer relationship between the portal and various subsystems in the background: the portal only determines the data selection and performance of each subsystem in the background, and each subsystem in the background is very easy to plug and remove.
4x2i 'K + c1l6u3c separation of content management and data distribution: when designing a portal system, pay attention to cache friendly design: CMS background management and publishing mechanism, the "efficiency" issue should not be considered too much. As long as the design of the final page output is cacheable, the efficiency issue can be solved through a dedicated front-end cache server. ) F8 [(u w: v1q. [0a $
In addition to being used for the final browser, pay attention to the URL Design for search engine friendly: using URL rewrite redirection or path_info-Based Parameter Parsing, dynamic web pages are more like static directories in the form of URLs, so that website content can be indexed by search engines.
'Y9u! R + Z,]
