Just a thought I had in the shower:
Most attempts at CMS version control end up reinventing large parts of
subversion/git/etc. inside the database. Instead...
Why not use something like FuseFS to implement a filesystem that maps the
Radiant asset tree to paths like "/dev/radiant/pages/home_page"? Then use
the version control system of your choice.
A quick Googling finds an implementation of MetaWeblog API as a Ruby
filesystem, which would make a good starting point:
http://zzamboni.org/brt/2007/03/31/metaweblogfs-ruby-fuse-xml-rpc-oh-my/
::Shrug:: Could be an interesting Summer of Code project for somebody[1].
Jay Levitt
[1] Somebody ELSE.
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
