Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 46999 invoked from network); 19 Aug 2009 13:14:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Aug 2009 13:14:34 -0000 Received: (qmail 59244 invoked by uid 500); 19 Aug 2009 13:14:52 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 59194 invoked by uid 500); 19 Aug 2009 13:14:52 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 59184 invoked by uid 99); 19 Aug 2009 13:14:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Aug 2009 13:14:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dionne@dionne-associates.com designates 67.222.53.251 as permitted sender) Received: from [67.222.53.251] (HELO outbound-mail-305.bluehost.com) (67.222.53.251) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 19 Aug 2009 13:14:42 +0000 Received: (qmail 32156 invoked by uid 0); 19 Aug 2009 13:14:21 -0000 Received: from unknown (HELO host183.hostmonster.com) (74.220.207.183) by outboundproxy6.bluehost.com with SMTP; 19 Aug 2009 13:14:21 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=dionne-associates.com; h=Received:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer:X-Identified-User; b=DGwDgdtOmIvAWsWq0xyPULW9ZRcWcIopHREL0rzhVfFUBjN24+YaDENNEmIfoeaUAGgxxvOxMNErNb2ZJy2VYaVG3TXanZa0bgflE33xd+f5qp8rgDhLoAVja+7K+IhX; Received: from adsl-99-29-29-126.dsl.wlfrct.sbcglobal.net ([99.29.29.126] helo=[192.168.2.100]) by host183.hostmonster.com with esmtpa (Exim 4.69) (envelope-from ) id 1Mdkzc-0001WU-UW for user@couchdb.apache.org; Wed, 19 Aug 2009 07:14:21 -0600 Message-Id: <06E06A08-5DA4-4457-AF90-67A5AF0238FD@dionne-associates.com> From: Robert Dionne To: user@couchdb.apache.org In-Reply-To: <4A8BF27E.3090801@vpro.nl> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: A CMS on top of CouchDB Date: Wed, 19 Aug 2009 09:14:19 -0400 References: <4A8BF27E.3090801@vpro.nl> X-Mailer: Apple Mail (2.936) X-Identified-User: {2551:host183.hostmonster.com:dionneas:dionne-associates.com} {sentby:smtp auth 99.29.29.126 authed with dionne@dionne-associates.com} X-Virus-Checked: Checked by ClamAV on apache.org You may want to look at and/or talk to these folks[1] who've prototyped something along the lines of a CouchDB based CMS cheers, Bob [1] http://www.ajatus.info/ On Aug 19, 2009, at 8:39 AM, Nils Breunese wrote: > Hello all, > > I work at a company that is currently in the process of evaluating > different content management systems with a focus on web publishing > and community features. We are currently using a CMS that was > developed in-house (started in 1996 when there weren't too many CMS > products around) and later open sourced. However, we feel we have > reached the limits of our current architecture and we're currently > looking at more modern and flexible ways to work with our content > and the web. > > We have had CMS products like Magnolia, Hippo, dotCMS and Roxen > demoed to us, which are all based on either Java Content > Repositories (JCR), XML and/or relational databases and I started > thinking: wouldn't a document-oriented database like CouchDB make an > ideal platform for a CMS? > > Features we're looking for include: > > - Document type specification and corresponding editors which can be > created automatically/easily > - Workflow management > - User roles > - Templating > - Content versioning > - Publication rules (e.g. 'visible after date 1, but only until date > 2') > - Community features like tagging and commenting > - Moderation > - LDAP integration > - Scalability > - Full text search > - REST API > - Easy creation and use of reusable components (polls, lists of > popular items, etc.) built using technologies understood by by > frontend developers (I'm thinking HTML/JavaScript etc.) > - Easy arrangement of widgets, drag and drop layout interface? > > I understand that a mature product with all these features built on > CouchDB does not exist today and probably will take a while to > build. I'd like to just throw the idea of a CMS on CouchDB out on > this mailinglist and hear from people that are interested. I'm not > sure my company is willing to build another CMS (I guess not, but > I'm 'just a developer'), but maybe we could participate somehow in a > project to build a CMS that might some day fulfill all of our needs. > > Any thoughts? > > Nils.