[Web4lib] Content management systems

[Andrew Hankinson]

The portability of content is one of the things that originally attracted me
to Drupal.  Previous CMS' that I'd used seemed to be stuck in the 'news
site' paradigm, and had problems dealing with static content pages, leaving
me with no alternative but to write a 'news story' but treat it like static
content - a concept that left a bad taste in my well-ordered-world mouth.

I'd used Mambo previously, and a few in between (Textpattern has a special
place in my heart) but it wasn't until I found Drupal that the idea of a
node being a page, but it can be anything (including a news story, but not
limited to one) that I really liked.

Flexinode has been used extensively on one drupal site that I administer,
and I suspect that when we upgrade I'll move that to CCK.

Cheers,
Andrew

On 3/20/07, Micah Stevens <micah at raincross-tech.com> wrote:
>
>
> Yep, that's handy when a lot of people are working on the same system,
> that's
> what my software does, and you can publish multiple versions, or work on
> version and not publish them as need be, so you can be collaborating on a
> page and get it approved before it gets published.
>
> I should look at how Drupal does theirs..
>
> Thanks
> -Micah
>
> On Tuesday 20 March 2007 5:36 am, Matt Grayson wrote:
> > Drupal does have built-in support for versioning. You can set it up so
> that
> > when a page is saved, a new revision is automatically created. So, if a
> > user makes a change that needs to be undone, it's a one click process to
> > roll back to the prior version. In practice, I haven't had to use it
> much.
> > But it's a nice safety net.
> >
> > Matt
> >
> > On 3/19/07 4:52 PM, "Micah Stevens" <micah at raincross-tech.com> wrote:
> > > On 03/19/2007 02:00 PM, Matt Grayson wrote:
> > >> We've been using Drupal at http://library.utmem.edu/ for almost a
> year
> > >> now with a fair amount of success. Drupal 5 has just come out with
> quite
> > >> a few improvements and I'm looking forward to upgrading. The biggest
> > >> challenge we've faced with Drupal is the lack of support for "real"
> > >> publishing workflows - where all content changes go through an
> approvals
> > >> process. On the whole, though, we're pleased with how Drupal has
> > >> performed.
> > >>
> > >> Matt
> > >>
> > >> --
> > >> Matt Grayson
> > >
> > > I'm curious from a development standpoint of how this would work. I
> use
> > > a versioning system for all page changes in a system I work on, but
> not
> > > an approval process as this hasn't been requested yet. Would this just
> > > allow unpublished changes, and then you require specified users to
> sign
> > > off before it can be published?
> > >
> > > -Micah
> _______________________________________________
> Web4lib mailing list
> Web4lib at webjunction.org
> http://lists.webjunction.org/web4lib/
>