Why you should choose zoglairFirst things first: zoglair loves web professionals (designers and/or developers), that is, people who make their living by building web sites for their clients. A big part of its design philosophy targets them, by providing convenient and time saving solutions to common problems in this business. That is not to say that zoglair is not suitable for end users. It is just to emphasize the fact that some of its great benefits can be better understood and appreciated by web professionals:
Which is what, is left as an exercise for the reader! Easy as ABCYou will be surprised by the simplicity of zoglair's interface. The first time you see its control panel, you may think it's a toy CMS. Streamlined, without the abundance of choices, options and fancy icons one usually sees in other systems. However, this is clearly a case where looks are deceiving... Its power is there, waiting to be explored. The nicest thing about zoglair's control panel (~backend) is the fact that it does not really exist... It is just a menu under a different skin! You see, in zoglair, the front and back ends are not two separate and discrete code bases. They may appear as such, as default, but the bottom line is that not a single folder, file or function (apart from the menu) in the whole zoglair source code is for Born to be WideA fundamental requirement of zoglair's design was to be flexible enough to support the most popular web applications right from its core, without the need of 3rd party extensions that may or may not interfere with its logic flow. Having a core that is not tight to a specific content type (article / product / topic / etc), but instead is able to handle any of them, simultaneously and under a common interface, offers the following advantages:
Thin, Fit and FastBloatware is a common term for a software that uses disproportional amounts of resources (disk space, memory, CPU time) to its functionality. In other words, if a software can be rewritten so that while functionality remains the same (or not noticeable less), needed resources are greatly reduced, then that software is bloated. Since bloated software has a bigger codebase and requires more resources than it should, it is:
Zoglair is the definition of anti-bloatware, should this term exists, despite its multi-personality nature. It is a fine example of the KISS and DRY principles. Please, have a look at our Multi-Domain SupportA single zoglair installation can power multiple sites, just as a single web server can drive multiple domains via its virtual hosting interface. Each site works with different data and is completely separated from the others. This has a tremendous advantage in maintenance as you not only control your sites from a common interface, but also work with and upgrade a single codebase and as a result all of your sites update automagically! You can even choose the scope of installed extensions (addons): you can make them available in as many sites you want (with a single physical copy, as in zoglair itself). Integrated BackupAs strange as it seems, backup is not a standard offering in the CMS world, although it should. Administrators all over the world are accustomed to using external programs for their backup needs, not always without problems, especially when data are getting big. In zoglair, backup is no longer a concern, no matter how big your database is. And, of course, what good it would be without a restore operation, which is also available. But that's not enough... We take it a bit further by offering a synchronization feature that allows you to have a local copy of your site's data in perfect sync with minimum fuss. This is a valuable tool for media oriented sites which can get really huge and traditional full backups are just too time-consuming to be practically useful. Self UpgradesAlmost every desktop application nowadays is able to notify users of new upgrades and - after they confirm - upgrade themselves automatically, without further interaction. Unfortunately, this is almost not happening in the world of web. Traditionally, one needs to download an archive from the vendor's web site, unzip it, transfer it (via ftp) on one's web site and possibly run an upgrade script. After a better-safe-than-sorry backup and site shutdown, so no visitor interferes with the process. Additionally, one should make sure that the new upgrade does not create any incompatibility issues with any site modifications. So, upgrading a web application is not always a seamless and risk-free procedure. Zoglair follows the desktop paradigm for upgrading itself. Not only there will be no need to download/upload anything, but also in case of a significant change in the codebase and/or data schema that could cause incompatibilities, the user is warned. Additionally, a migration script will take care of upgrading 3rd party additions and modifications, if possible! Innovative Cache MechanismCache is an intermediate mechanism, between a client and a server (in their broader sense), which transparently stores data to make them available faster, next time these data are requested. Generally speaking, a cache is a good thing and any CMS can benefit from its presence. It doesn't matter if it is a slow CMS or a fast one. There will always be requests that take time to be fulfilled, such as long run-time calculations and full table scan queries. However, caches have a native flaw (besides their redundant storage, which we choose to trade for speed): data freshness. You see, an item cannot be cached forever because it is a dynamic item (if it wasn't then there would be no need for a cache, in the first place). So, when the life span is set too low, there are a lot of cache misses and unnecessary server processing. When the life span is set too high, there are a lot of cache hits but the data are old news! Developers and administrators have no way to know the exact time in the future where data will change. They arbitrarily set an item's expiration time based on how frequently this item is requested and how Well, with zoglair's cache there is no guessing... Besides scalar numeric values, it accepts data model events as life spans. So, we simply cache data Last but not LeastThe following properties may also be of interest to you:
|
Latest Updates |