News for hackers. Stuff that matters.
Re:The CMS Is Broken. by thomasfl on Friday July 15, 2011 @05:36AM (#2766798)
The simplest way to design an API, is to use an existing one. I work with a CMS where JSON documents are posted using the WebDAV protocol. Settings for documents and folders are all set with the PROPPATCH verb. The WebDAV protocol has defined API's for ACL, versioning and namespace management like delete, move, copy.

Info about Vortex CMS (in Norwegian): http://www.uio.no/tjenester/it/web/vortex/

Re:The CMS Is Broken. by bergie on Friday July 15, 2011 @05:41AM (#2766806)
Sounds very good. Would the DAV (REST) APIs be accessible for something like https://github.com/bergie/VIE ?
Re:The CMS Is Broken. by thomasfl on Friday July 15, 2011 @05:54AM (#2766827)
Yes it probably would. The API is also accessible from client side javascript. So you could create admin pages in 100% javascript like in HiFi.
Re:The CMS Is Broken. by bergie on Friday July 15, 2011 @05:58AM (#2766834)
Admin pages are one thing, but with VIE you can make content also editable right where it is. See for example what we did with Midgard:

http://bergie.iki.fi/blog/introducing_the_midgard_create_use...

Re:The CMS Is Broken. by thomasfl on Friday July 15, 2011 @06:24AM (#2766886)
I really like the constraints you set on your project: "Build a CMS, no forms allowed". Aloha and other wysiwyg editors can hide the CMS almost totally. Using RDFa to store content is not a bad idea.
Re:The CMS Is Broken. by bergie on Friday July 15, 2011 @06:58AM (#2766936)
If you're interested in integrating VIE into that system, then the EU-funded IKS Project might be able to help you with that: http://www.iks-project.eu/get-involved