-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wayne Schlitt wrote:
Bill Taroli writes:
Sorry if I'm rehashing an old discussion... but has any thought been
given to using a CMS and perhaps delegating maintenance of different
parts of the site to different people? The CMS would offer some
measure of protection, too, since most good ones offer versioning and
the ability to easily roll back content should "problems" occur.
I don't think anything has been decided, but yes, both Julian and I
have talked about some sort of revision control system. Julian
installed subversion on the new box, but I don't think anything has
been set in stone.
I think Subversion-based revision control is the best we can do for the
current site, which is Mason-based, i.e. based on individual files that
must be edited "by hand".
Julian also says that the wiki that he is hoping to migrate most of the
content to will have audit trails and rollbacks and such. It will also
allow far more people to be able to edit it without the need to deal with
the actual machine.
It is an enhanced spin-off of UseMod Wiki[1] that I have used for a handful
of sites already, because it is so easy to maintain and use, and highly
customizable and extendable. As for revision control, all pages are
inherently versioned, see [2] for an example on the Council website.
References:
1. http://www.usemod.com/cgi-bin/wiki.pl
2. http://spf.mehnle.net/?action=rc&days=90
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCqhwtwL7PKlBZWjsRAsODAJ9MQKFHiRZBU3AtdEPp5zBXGroRAgCdFuDD
V8F/Twu05Ru2e+MMNOebVdU=
=padw
-----END PGP SIGNATURE-----