Question of management of a content

With what the content - manager begins?

Sooner or later any owner of a content - site comes to idea, that the content - manager is necessary for his  site. When the quantity{amount} of html-files passes for some hundreds, to cope with them begins difficultly. And if with preparation of a content for a site are borrowed{occupied} a little bit{some} person - it is possible to extinguish light valenki.

And in fact so it would be desirable to give more time to creativity, instead of to kill time for routine. This necessary, but routine job is incured by the content - manager (Content Management System, CMS).

So, if you understand pluss and minuses CMS, and timeliness of his  installation *, it are necessary to answer a question "as". How to pass on CMS?

There are three variants.

a) To charge with this business to professionals - to people which have eaten herd of dogs on a field of creation a content of sites (including design and a program stuffing). But this expensive{dear} enough pleasure. Not everyone is ready to lay out 1000 or more green money **.

b) To find an available free-of-charge or noncommercial variant ***. The main minus of such variant will be, that such CMS " the standard site " what no in the nature is written on certain. Therefore to you it is necessary not only to rummage in interiors CMS (to understand how this "unit" furychit), not only closely{attentively} to study the documentation (without documentation CMS take only mazokhisty), but also to adjust CMS under the needs and design.

For this reason PhpNuke it is considered " lamerskoj a feature " - to put it  easily, he will be adjusted, but well to adjust it  under the needs... And you remain with the "preestablished" design and inconvenient system obnovlenij a content.

v) To write CMS itself. The most good variant. You know, that it is necessary for you, as CMS should work, and what resources to him is permitted to use.

About last variant also there will be a speech further. I remind, that practical and clever advice{councils} (for a subject " How correctly to write CMS ") to allow I do not plan, but I shall try to show, it is necessary to pay attention to what questions and aspects.

Construction CMS begins with a simple question - " What you have resources? " It not a banal question. It is necessary to foreknow, what capacities are accessible.

All CMS can be divided{shared} into three groups conditionally:

a) Dynamic.

The page is formed dynamically as soon as there comes search. Keshirovanie it is not used. Most resursoemkij a variant as the cursor works constantly. If it is a lot of visitors, the weak server can quickly stretch lasty.

The basic advantage of the similar circuit - each visitor receives the freshest variant of a content. Besides individual adjustment of page under each user is possible{probable}.

b) With dynamic assembly.

Dynamically collected (after search) the page keshiruetsja until comes for it{her} updating. During this moment kesh it is dumped{reset}, and the cycle repeats.

Other variant takes into account the user preferences. The page each time is going to dynamically, but from static (zakeshirovannykh) fragments. If any fragment is updated, at the following search he will be peregenerirovan and is brought in kesh.

Average loading on the server.

v) With static assembly.

At updating CMS peregeneriruet all connected pages. Therefore at search it is given out already generated static (probably, collected SSI) page.

Understandably, that the group "b" is designed for constantly changing content (news sites) or on a small amount of visitors, but the group "u" will sustain the big inflow (but it is used, as a rule, at infrequent obnovlenijakh). The group "n" - somewhere in between, but demands competent management keshirovaniem.

So, what resources at you is? You expect for what loading? Whether additional capacities are necessary for you, and whether is ready khoster to give you them?