Manage system by CMS = = website content management system, it is a kind of site construction solution!
Content management system is a very extensive concept: the news from commercial portals to publish a sophisticated Weblog system can be called the release system.

Frame: itself does not contain any application, provide a framework, the concrete application of floor needs certain second development, such as the Cocoon, Vignette,
Application: itself is a specific type of application oriented, already contains news/review management, voting, BBS, some subsystems WIKI. Example: postNuke xoops etc,

However, in the release system before the first selection, the actual demand of oneself is the most important: think according to their needs off-the-shelf systems hardware upgrade copy is not desirable. Traffic, access control and various functional requirements. Each module and function oneself are clear, then go online for similar: you'll find that in fact each link to the current are more mature, but also realized in improving and developing, if not: your demand too special, or can be decomposed into smaller to realize the system.

Content management system was separated into the following several aspects: the levels of demand different priorities

Back-office operations management subsystem priority: the management of content management) : news input system, BBS BBS subsystem, fulltext retrieval subsystem, convenient for different content of the system administrator type: wysiwyg editors management interface, clear business logic: various subsystems of access control mechanism; etc.
The Portal system () template priority: the performance of the final output page: most homepage, and channel/project page for details page is commonly, news of backstage subsystem, the combination of modules by combinational logic is very rich, the Portal system is responsible for these combinations of performance management background subsystem,
Receptionist: (giving priority to efficiency by management) : the end user, the cache and search engine spider URL design etc...
Content management and performance of the complete separation: many of the CMS no background and subsystem design that separated the Portal template in the Portal of performance management layer and news content management subsystem logic together, even the management subsystem and BBS is very high, the coupling system can appear very confused. But this system of each subsystem is dead, if bound to change the background of the module. But if the backend various subsystems and the content management performance/issued after the separation, the Portal and backend subsystems is the data transmission relations: the Portal only backstage data of each subsystem and performance, and the various subsystems are also very easy connectors.

Content management and data distribution of separation: need to pay attention to the Portal system design can be cached (cut) design: the Cache management background and release mechanism of CMS, don't over-think it "efficiency", as long as the final pages of output Cacheable comparison, the efficiency of the design problem of more front by solving the Cache.

In addition, except for the end user, but also pay attention to the browser for Search engine Friendly (cut) URL search.com design: through the URL to PATH_INFO REWRITE the parameter parsed or based on dynamic web link (that) more like a static URI form the directory structure, convenient website content; by Search engine,