5 ms·
Most web design shops which build websites for clients will end up using some form of Content Management System, to allow those clients to maintain the site aft
by peakpg 17y ago
Most web design shops which build websites for clients will end up using some form of Content Management System, to allow those clients to maintain the site after launch. BrowserCMS is a solution to our firm's problem, which is wanting the productivity of Rails for building custom websites, but giving clients Web CMS tools to maintain the site after launch.
I'm the product manager for BrowserCMS, so hopefully I can shed some light on the 'whys' behind the project. It is certainly not to clone Drupal in Rails. Drupal is mentioned in the presentation because many developers are familiar with it, so the enviable first question I hear is 'How is BrowserCMS like Drupal?'.
Our intent with BrowserCMS is to provide a client friendly CMS. Making a site maintainable and understandable by non-technical users is the primary goal of the CMS. We also want to allow Rails developers to be able to customize sites. We do have a module system (different than Drupal's), which allows developers to build custom modules (News, Events Calendars, Blog, etc). The dynamic content can be placed by non-technical users on pages. Obviously, it's a new project though (still in Beta), so we are about ~4500 modules behind Drupal here.
Anyway, if folks have more questions, our mailing list is at http://groups.google.com/group/browsercms http://groups.google.com/group/browsercms