4 ms·
Wrong. Personally for me a dead end criteria is a CMS without an API. But you mean most people don't need it right? I also think that's not right, because many
by X4 13y ago
Wrong. Personally for me a dead end criteria is a CMS without an API. But you mean most people don't need it right? I also think that's not right, because many companies want Mobile Apps, Intranet tools etc. and integrating their crap with the CMS through an API makes a whole lot sense.
I looked at http://prismic.io http://prismic.io, but I haven't found anything that's opensource and comes close to it. Do you know something like that?
- justincormack 13y agoNo not saying most people dont need it, they are a reducing pool, the people who do need it have moved away already.
- X4 13y ago>> […] people who do need it have moved away already. hmm, what do you mean and to which platform? I was thinking of enterprise users and companies who mostly start with a cheap cms, then add features here and there then an app, then an intranet thingy and at the end you have a spaghetti architecture, because everything has it's own front-end without a unifying API. It's rare that developers write their own solutions, you can say, hey nobody would do that, but the reality is far from that. Most devs simply use what's there and try to integrate different projects "by their own way". I found some things that can be done better at prismic.io and think there is some wasted potential there. - It requires writing your own controller that needs to implement caching or you have a 500ms delay for API requests - No multilanguage from the beginning (gotta bake your own solution, that's not so fun) - Slugs for objects in collections are ugly (see blog example) Here are all REST API based "CMS", unfortunately, none of them is actually perfect. http://www.programmableweb.com/apitag/CMS?protocol=REST http://www.programmableweb.com/apitag/CMS?protocol=REST