The section entitled System Build will cover three areas in detail. It will explain all the aspects of the Cliqon framework, starting with our definition of a MVC system. It will explain those aspects of Cliqon that we have written ourselves and the modules that we have imported and utilised from elsewhere and other authors, such as the Razr templating system and Redbean database handler.


The framework subsection will cover the following key server side functions – routing, authentication, REST api, database, ORM, html generation, template rendering, logging and debugging, configuration, file system, image manipulation, forms, menus, reports, lists, users, session and cookie handler, integration with services such mail, ftp and Node, text and array searching, JSON handler and finally plugins.


The framework subsection will also cover the following key client side facilities – style sheets, templates and javascript. The presentational framework for the Administration system is based on CoreUI. Rendering of every aspect of the Administration is accomplished using rendered templates, server generated HTML and AJAX.


The structure subsection will explain how we have used the framework functions to build an administration system which you, as a developer, can augment and enhance. It will explain how extend the Cliqon system by writing your own classes and methods as modules and plugins.


Finally the subsection on website presentation will explain how to create and maintain content in Cliqon so that Cliqon can act as a Content Management System (CMS) utilizing multi-lingual templates, pages, components, blocks and strings.


In principle, we can describe Cliqon as a Module – View – Controller system (MVC). There is no settled and agreed definition for the meaning of an MVC system.



Created with the Personal Edition of HelpNDoc: Qt Help documentation made easy