Content Management System Overview The content management system is a very broad concept: all from the news system from the commercial portal to the personal WebLog can be called a release system.
Frame type: itself does not contain any application implementation, just provide the underlying framework, specific applications require a certain secondary development, such as cocoon, vignette; application: itself is a specific type of application implementation, already included news / comment management Some subsystems such as voting, forum, wiki. For example: Postnuke Xoops, etc., but in any case, first understand your actual demand before publishing system selection: I want to move my demand hard in accordance with ready-made systems. Visits, permission control, and various functional needs. Every module and function are more clear, then go online to find a similar implementation: You will find that every one has a mature implementation, and it is still improving and developing, if not : Your needs are too special, or you can try to break down into smaller system combination implementation. The content management system is separated into the following levels: the demand for each level is preferred.
Background Business Subsystem Management (Management Priority: Content Management): News entry system, BBS Forum Subsystem, full-text inspection subsystem, etc., the content of the convenient manager for different systems is entered: the editorial management interface you have obtained, clear Business Logic: Permissions Control Mechanism of Various Subsystems, etc .; Portal System (Performance Priority: Template Management): Most final output pages: Home, sub-channel / topic page, news details page is generally a variety of back subsystems The various combinations of modules are very rich. The Portal system is responsible for the combined manifestation management of these posterior subsystems; reception release (efficiency priority: release management): Backers for end users, and search engines Spider's URL design, etc ...... Separation of content management and performance: Many complete sets of CMS systems do not separate all subsystems and portal in the background, so that the content management logic of the template performance management and the news subsystem at the PORTAL layer Together, even the management of subsystems such as BBS is very high, the entire system will be very intebriring. Moreover, the comparison of each subsystem of each subsystem is difficult, and if the module in the background is difficult to change. However, if the sessile content management logic of the background, the performance / release of the front desk, the PORTAL and the background are only the relationship between the data transfer: Portal only decides to pay and perform the hits and performance of each subsystem data in the background, and the background Each subsystem is also very easy to swap. Separation of content management and data distribution: Take Cache Friendly Sex Design: CACHE Friendly Sexual Design: CMS Background Management and Publishing Mechanism, it should not take too much "efficiency" problem, as long as the final page output design Cacheable, efficiency issues can be solved by a more special cache server. In addition, in addition to facing the final browser user, pay attention to the URL design of search engine friendly (Search Engine Friendly): Turn through the URL REWRITE steering or PATH_INFO-based parameter analysis makes dynamic web pages in the link (URI) form more like static Directory structure, convenient website content is included in the search engine; here, I summarize some of the information found in the content publishing system selection:
Selection of content management system Key words: CMS Content Management http://www.cmswatch.com.com Htttp://www.cmsinfo.orgcms Discussion Mail list http: // www. CMS-List.org Business Software and Open Source Project List: http://directory.google.com/top/.../content_management/ Recommended: XML-based release framework http://cocoon.apache.org / specific implementation complex The degree may be different depending on the demand, but the more large systems need to be divided: content (data), performance (template) and application logic (program) are as separated and managed to these three. Portal --- Portal Open source Projects: http://jportlet.sourceforge.net/ Apache Software Foundation: Jakarta JetSpeed 1.3JetSpeed home page: http://jakarta.apache.org/jetspeed/site/index.html JetSpeed Portlet API: http://cvs.apache.org/viewcvs/jakarta-jetspeed/proposals/portletapi/http://www.liferay.com/Home/index.jsp http://basicportal.com/ http: // www .jahia.org / http://jporta.sourceforge.net/ Business: Bea WebLogic Portalhtp: //edocs.bea.com/wlp/docs81/javadoc/com/bea/portal/model/portlet.html IBM WebSphere Portalhttp : //www.software.ibm.com/wsdd/zones/portal/ Oracle Portal Developer Kithttp: //portalstudio.Orcle.com/ Other: PSMLHTTP: //jakarta.apache.org/jetspeed/site/psml.htmlbea: Web logic portal 4.0http://www.bea.com/products/weblogic/portal/index.shtmlibm: WebSphere Portal 2.1Http://www-4.ibm.com/software/webservers/portal/ iplanet PORTAL Server 3.0http://www.iplanet.com/products/iplanet_portal/home_portal.htmloracle: Oracle 9i Portalhttp://www.racle.com/ip/deploy/ias/portal/index.ht MLSAP Portal: http://www.iviewstudio.com/Solutions/ProductS/efs/ Reference: Wafer: Java Development Framework Study Http://www.waferproject.org/index. HTML Portal (Portal) system related development framework: http://udoo.51.Net/mt/archives/000011.html Advertising Management System Keywords: AD Server Advertising System and Content Separation, can greatly reduce the relationship between systems degree.
