History
Started in late 2007 the first version of Beezilla was written in ASP.NET. The first version (backoffice) was written as a web based developement tool. Users could easely create web applications (forms, views, reports ...)
The first version was one the five finalist at the Canada MSDN code awards 2008.
In early 2008 the first version of Beezilla frontdesk was released to the public, that version was a complete rewrite using PHP ans MySQL ans was more CMS oriented that the previous version. User could now manage their corporate web site.
It is planned to release a second version of the Backoffice in late 2008.
Advantages of using a CMS
Decentralized maintenance.
Based on a common web browser. Editing anywhere, anytime removes bottlenecks.
Designed with non-technical content authors in mind.
People with average knowledge of word processing can create the content directly. No HTML knowledge needed.
Configurable access restrictions.
Users are assigned roles and permissions that prevent them from editing content which they are not authorized to change.
Consistency of design is preserved.
Because content is stored separate from design, the content from all authors is presented with the same, consistent design.
Navigation is automatically generated and adjusted.
Menus are typically generated automatically based on the database content and links will not point to non-existing pages.
Content is stored in a database.
Central storage means that content can be reused in many places on the website and formatted for any device (web browser, mobile phone/WAP, PDA, print).
Dynamic content.
Extensions like forums, polls, shopping applications, searching, news management are typically modules.
Cooperation.
Encourages faster updates, generates accountability for authored content (logs) and cooperation between authors.
Content scheduling.
Content publication can often be time-controlled, hidden for later use or require user login with password.
Based on a common web browser. Editing anywhere, anytime removes bottlenecks.
Designed with non-technical content authors in mind.
People with average knowledge of word processing can create the content directly. No HTML knowledge needed.
Configurable access restrictions.
Users are assigned roles and permissions that prevent them from editing content which they are not authorized to change.
Consistency of design is preserved.
Because content is stored separate from design, the content from all authors is presented with the same, consistent design.
Navigation is automatically generated and adjusted.
Menus are typically generated automatically based on the database content and links will not point to non-existing pages.
Content is stored in a database.
Central storage means that content can be reused in many places on the website and formatted for any device (web browser, mobile phone/WAP, PDA, print).
Dynamic content.
Extensions like forums, polls, shopping applications, searching, news management are typically modules.
Cooperation.
Encourages faster updates, generates accountability for authored content (logs) and cooperation between authors.
Content scheduling.
Content publication can often be time-controlled, hidden for later use or require user login with password.
Comments
Write New Comment ▼
Write New Comment
Sorry! This knol's owner(s) have blocked you from editing, making suggestions, or commenting here.