• static HTML documents (*.html files);
• style sheets (*.css files);
• client side scripts (*.js files);
• script URLs generating the same HTML code;
• application specific text files, text based data sources etc.

Often multiple files contain the same text fragments and when change is needed all those files must be updated at the same time. For example most of the website's HTML documents may have same basic layout, header, navigation, footer etc. Still all those documents have unique content and features, additionally often there is a need to have some documents that don't comply with common design idea of the site.

Below is the list of commonly used approaches and disadvantages associated:

The dilemma over the maintaining the similarities and difference is anything but new and there is well known solution to it - inheritance. While descendant inherits some of the properties and behaviors from its parent(s) is can have some of those properties redefined and it can also have additional (personal) ones. The very same approach can be applied to the files in web site's hierarchy. The idea of SCMS is to take the best of two worlds: have separate static file for each text document, but generate them to the server's disk based on the hierarchy of inheritable elements only when update is needed.

• Easy to maintain similarities - since system offers inheritance similar elements are defined once and then inherited from parents automatically. For example code for navigation is defined once and it is inserted to all the documents except files where it is explicitly excluded or changed;
• Easy to maintain differences - with the inheritance in place, the differences are described locally only where they are needed without affecting other files. For example if several pages have to use different layout then webmaster defines that alternative layout (once) and assigns it only to those particular page;
• System can be used on top of the existing scripts based solution - the server side scripts will generate the dynamic content (i.e. confirmation page with results of visitor's submission) while SCMS will help manage all the rest resources that are contain static or rarely changing content (i.e. company info, products list etc). Additionally the code of the server side scripts can be managed using the SCMS;
• Effective server resources utilization and improved website performance - all static content is generated and saved to server's disk. During the request the content is pulled from the static file, no resource hungry scripts are invoked. Additionally static part of dynamic script can be optimized with this system. Example: the shopping cart has list of special offers, while content of the shopping cart is dynamic and must be generated for the visitor upon the request, the text of special offers may not be dependent on the visitor's interaction so in this case it can be pre-generated by SCMS and saved in the shopping cart template used by the dynamic script.
• Better search engines rating - with the maintenance simplified for the static documents the webmaster can afford to have more of them thus improving the rating of each resource and website as whole (for explanations see the section above).

• Web server: any web server supporting CGI
• Scripting Language: Perl v.5+
• Modules: CGI, HTML::Template, DBI, DBD::MySQL, URI::Escape, Time::Local, Data::Dumper
• Database: MySQL
• Permissions: database read/write, disk read/write