A file-based CMS which uses standard HTML5 markup
Hyperframe integrates conventional HTML files into a managed framework with cascading top or side menus, banners, footers or other dynamic content.
Recently, there has been a surge of interest in file based Web content management systems. These differ from the mainstream products such as Joomla! or Wordpress, in that they do not store the webpages in an SQL database, but instead store them as disk files. The advantages conferred by this arrangement are greater speed, security and simplicity, plus portability - The transfer of a website from one hosting service to another of similar specification often involves no more than simply copying the files over.
The majority of file-based CMS require that the files containing the webpage information are written in a special code known as markdown syntax. Thus, whilst significantly easier to set up than the database-backed variety of CMS, the importing of a website to these still requires a good deal of rewriting or data conversion. Hyperframe, by contrast, uses the industry standard and very familiar HTML syntax. Thus with Hyperframe, importing of existing static websites is very straightforward, and there is no need to spend additional time learning another unfamiliar syntax. If you understand HTML, you can use Hyperframe effectively.
The provision of a very intuitive, wordprocessor-like online editor also makes Hyperframe easy to use for persons who only wish to edit or add page text, without having to get involved in the technicalities. In view of these features, we think you will find Hyperframe to be one of the best file-based CMS currently on offer.
The storage of your webpages in conventional files is an instance of 'understandable technology' -You know where on disk your pages are stored, what format the information is in, and can examine, edit, copy or back them up as required, all with standard tools. This also makes the import of existing static sites very easy, in some cases merely copying the files over and adding menu items is all that is required. Packages of this file based type are sometimes known as a flatfile CMS, although that term does not necessarily indicate that all webpages have to be in the same folder/directory, rather it indicates the distinction from relational database storage.
Aimed at the Web professional building sites for commercial clients or the more experienced enthusiast, configuration is by direct editing of settings. Here, you won't find the endless pages of options and tickboxes present in mainstream database-backed CMS. What you will find is a concise set of config options which are easy to understand, and quick to set by way of straightforward text files. This makes for a small, fast core system whilst allowing great flexibility.
Pages may be created online with the integrated copy of CKEditor, or created locally and uploaded by FTP. This gives great flexibility to work in either traditional local data storage or centralised-storage environments. This also enables the commercial designer to permit controlled updating of the site by the client, thus saving on professional maintenance work. A rollback facility allows the webmaster to recover from mistakes made by self-updating clients.
Cascading menus and ajax make for an efficient site navigation experience with few page reloads. This is an area we've spent a good deal of effort on, clear and fast navigation being critical to a positive visitor experience of any site. The design objective here is to provide a menu system which caters for almost all page-linking needs, which shows the visitor clearly their location in the site structure, and which avoid tedious repeated page reloads to get to a destination.
As on any well-prepared website, stylesheets and page text are separated, such that the webdesigner can make a full range of customizations to the site appearance without having to rewrite pages. Multiple, visitor-selectable frames (the equivalent of a template in mainstream CMS) are possible, making for easy testing and demonstration of styling options to clients.
As far as possible we have used straightforward procedural code in writing Hyperframe. We have used object oriented code in some places where it offered a clear advantage, but for the most part we have kept to traditional coding methods on the basis that this keeps the system code lucid and easy to modify, should that be required for a specific application.
File-based storage also eliminates one of the major security issues of database-driven CMS, namely that if the coder omits to 'sanitize' user-entered data of SQL programming instructions in just one single place of the many such places in a major project, then the site is open to hacking. When no database is involved, code injection hacks are quite simply not available to exploit.
Requires: Apache 2.x webserver with php5.2 or later.