Welcome to the adva cms community wiki!

Getting started · Howtos

About adva cms

adva cms is a cutting edge open source cms application plattform based on Ruby on Rails and Rails Engines .

It currently comes with core engines such as:

  • Cms : build multiple sites with hierarchically organized sections
  • Blog : blogging system heavily inspired by Mephisto
  • Wiki : a wiki engine inspired by Signal Wiki
  • Forum : a forum system inspired by Beast

And sports additional engines providing features like:

  • Theme support : completely change every aspect of the design for a site. Easily share and import themes.
  • Spam control : a configurable spam filter chain makes it easy to hook in the spam control system of your choice (currently supporting Akismet and Defensio )
  • Dynamic role based access control : for every site define what roles are required to perform any action
  • Anonymous and registered user accounts

adva cms is build with the following design criteria in mind:

  • Extensibility and flexibility
    As adva cms uses Rails Engines as a foundation users can choose to pick only those engines (think: modules) that suit their needs and omit others, thus making the system as slick as possible. At the same time because of the power of the Ruby on Rails plugin infrastructure it is very easy to extend the plattform with additional features and even whole engines.
  • Your application’s foundation
    Different from other great Ruby on Rails applications adva cms is intended to work as a foundation so you can build your own applications on top of it. As adva cms is shipped as a collection of Rails Engines the Rails’ app/ folder is empty: that’s your space and adva cms won’t touch it.
  • Scalability and speed
    adva cms uses Rails’ page caching throughout the whole front end. That makes it very fast and easily scalable because from the second request on your front-end server of choice takes over and delivers statically cached HTML pages with blazing speed.
  • Internationalization
    adva cms was build with Internationalization in mind right from the start and will use Rails 2.2’s I18n API and Globalize2 to enable multilanguage sites transparently.

revision: 1 last updated: August 12, 2010 11:15 by: Christopher Floess