[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion fits for a content management system?

From: Will Appleton <wfappleton_at_gmail.com>
Date: 2007-07-17 20:30:47 CEST

On 7/17/07, Konrad Rosenbaum <konrad@silmor.de> wrote:
>
> On Tuesday 17 July 2007, Marcelo de Barros Alcantara wrote:
> > My doubt is if subversion fits as a content management system.
> >
> > We are a big portal in Brasil with thousands of new documents created
> > every day. We intend in our new publishing system to keep versions of
> > the generated material.
> >
> > I am asking this question because I could not find on the net any case
> > related to use subversion for a situation other than keep project
> > documents/source code.
>
> Are all people who create and edit documents developers or are
> there "normal" people, like graphics designers, journalists, etc. there as
> well?
>
> If they are all developers this will work quite well - eg. parts of KDE's
> web pages were "managed" in subversion (http://developer.kde.org) for a
> while.
>
> If even only one of them is less technical it will fail because the
> update-modify-commit cycle that comes quite natural to development is
> somewhat unintuitive for content creation.
>
>
> Konrad
>
> Some of our business analysts are using SVN/TSVN as a poor man's content
management system. We don't need a promotion model for these documents at
this point, though we could fake one with branches and permissions. So far
this is working well for us. The only downside to this setup is that the
SVN and TSVN documentation is written for programmers, and not the average
content creator. Most of our non-programming SVN users have such basic
versioning needs that training hasn't been a very big problem.

-=W=-
Received on Tue Jul 17 20:30:14 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.