3 ms·
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 document
by thomasfl 15y ago
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/ http://www.uio.no/tjenester/it/web/vortex/
- bergie 15y agoSounds very good. Would the DAV (REST) APIs be accessible for something like https://github.com/bergie/VIE https://github.com/bergie/VIE ?
- thomasfl 15y agoYes it probably would. The API is also accessible from client side javascript. So you could create admin pages in 100% javascript like in HiFi.
- bergie 15y agoAdmin 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_user_interface/ http://bergie.iki.fi/blog/introducing_the_midgard_create_use...
- thomasfl 15y agoI 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.
- bergie 15y agoIf 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 http://www.iks-project.eu/get-involved