Starting off in the year 2005 fooBar CMS v1.0 was born, using a very simple yet effective design layout and simplistic modular based system. fooBar CMS v1.0 was used widely on small to medium sized dynamic web sites utilising newsletters, image galleries, dynamic page content modules and even to the extent of in-house business management systems.
During the many years, fooBar CMS received many upgrades and custom design changes to suit the front-end environment of a website. BBClone was introduced as a statistics programs and tinyMCE was the main WYSIWYG (what you see if what you get) editor. htmlMimeMail was then included a few months before the year 2006 to introduce valid HTML emails that could be sent from the CMS within modules such as newsletter modules and front end contact forms.
During the years of 2006 -2007 was a new begining with the birth of dynFields™ technology.
dynFields™ v1.0 was originally built to allow two or more mySQL tables to 'synchronise' together allowing one table to dynamically load information from another table with limited knowledge of sql queries by sending a command to the newly created dynFields™ API. The dynFields™ API was able to output in two formats, php arrays and xml. With this new functionality, fooBar CMS was then able to extend itself more in the dynamic content management system market. The main goal behind dynFields™ was to allow the same functionality for mySQL v4.x as v5.x, stored procedures etc.
Such web sites as propertyextra.com.au, apa.com.au & buysellrealestate.com.au started to use this new technology built by the main developer of fooBar CMS allowing them to load a template driven front-end using the fooBar CMS.
Mid 2007 saw the creation of fooBar CMS v2.0.0 and dynFields™ v2.0. fooBar CMS had undergone a complete rewrite of all its' code, folder and template structure, module and class structures as well as allowing reseller capabilities and extended marketing systems for developers and resellers.
fooBar CMS v2.0.0 was the birth of the fooBar API allowing xml-rpc commands, an SDK for freelancer php developers and an extension based system to plug into the new dynFields™ API. Output formats now extended into xml, array, rss, atom, json and query based outputs. Programming hooks where installed to allow extensions for pre-made modules and ajax based web sites.
dynFields™ v2.0 saw the creation of an advanced php xml interpreter and command console, database structure and field management, table links, javascript console, ajax functionality and the introduction of mootools v1.11.
dynFields™ was now the backbone to the fooBar CMS, allowing fooBar to call the dynFields™ API to output strict XHTML for managing, adding, editing and deleting records for multiple database tables.
By the end of 2007 the fooBar CMS had taken shape; design and functionality wise. dynFields™ had quickly become three times its' original size and is still growing till this day with added functionality, outputs and field based widget and management systems to allow developers and end users to easily manage their data with a click of a button.
fooBar CMS had now seen a complete re-write of the image gallery, dynamic page management, account management, newsletter, address book and 50% of a complete shopping cart and stock management system complete with PayPal and Google Checkout payment gateways.
The first release of the fooBar CMS v2.0.1-1 beta was used on a few small web sites for taking the CMS for a 'test drive'.
With limited bug reports and a few suggestions for functionality, fooBar developement was broadend bringing on two more developers to help build module based systems for fooBar (blog and private message systems). Using an advanced upgrade system, fooBar CMS is able to upgrade modules automagically or manually without using ftp or editing database structures to complete the upgrade.
Still in developement today fooBar CMS will exceed all other CMS applications on the market as every aspect of the CMS can be modified!
That's right, you heard correctly. Every aspect of the CMS can be modified to suit the clients expectations; allowing fooBar CMS to step up the game within the content management industry.
