Yeah I've been thinking about this kind of an approach for a while - the idea of making a content management system that is just a content store that is accessed via API. Like it.
The largest obstacle for me to adopt such a system is that it requires me to bet my company's content on your system being around. I've looked at, for example, Webpop which is different but has some similar ideas - but I can't get away from the fact that Webpop may or may not be around in a year, so betting on it isn't something I would want to do.
That's what continues to push me to Wordpress and the like, although recently I've been spending more time with static web generators like Harp and DocPad. Those have a similar issue - my boss saying to me "Well, I know we can find Wordpress developers, but will wevbe able to find a Harp developer?"
I work with Adobe Experience Manager (former Day CQ) and the way the content is managed is the best, I have experience with. Of course, it does not mean, the product is perfect. But the concept feels right.
Yes, it looks like the same idea as Jackrabbit / JCR. I hope they've done their homework and understood the advantages and limitations of that API. I always found it a pain to work with, and that's probably the reason it never took off.
I really, really hope they succeed, but they've bitten off a difficult problem. It's not hard to design a simple content management API. What's hard is making it general enough to handle many situations without getting too complex.
Yes, the JCR spec is not easy to implement. But with a mature implementation, you can create your CMS convention driven. Those conventions can be as narrow as you need for a simple CMS. And when you want offer more, you are not limited by the content repository but only by your conventions, which you can widen at any time. I hope, more people will look to JCR as an option, because it solves the content repository problem very well.
We've been around for more than 3 years now, have clients with hundreds of published sites and we're profitable, so we're not going anywhere.
That said, the lock-in is a problem and I wish there was a really great way to address the lock-in. Open-sourcing doesn't really solve it when the software is built to scale up to handle thousands of multi-tenant sites on a distributed infrastructure, but not to be simple enough to install and run that it's viable for a relatively small number websites.
I'm working on a product in a similar space to prismic, and as a developer myself, this would also be a concern for me. The way we plan to approach it is offering a self hosted version of the product, and committing to an open source warranty so that if something went wrong with the company the product could live on. Would these kind of measures make you feel more confident?
There are two concerns - one is that the company goes away. The second is that there aren't any developers that know your product, therefore we can't hire anyone without training. So your measures would deal with the first but not the second. Have you considered open sourcing some part of it?
Hey, indeed, part of the easy learning curve is that all of the kits (i.e. the part that developers actually use in their projects) are open-source on GitHub: https://github.com/prismicio
Also, learning how to develop with it could really hardly be easier, check out the 10-minute video on the developer's portal: https://developers.prismic.io/
Agreed. I think the way openphoto/trovebox does it with photos might be a solution to this problem... an open specification with the choice to store it on your own server or your own AWS acccount... then the company provides pay services for hosting themselves or for providing the pre-built back-end and front-end tools.
Experience with a specific product is way overrated because a) products don't last forever, programming does b) any decent programmer can learn how to work with harp in about the same time it would take a Wordpress expert to get up to speed with your particular Wordpress setup
Somewhat agree/somewhat disagree. Products don't last forever, but the large open source products like Drupal and Wordpress have been around a fairly long time - long enough to instill confidence in my boss that they will, more than likely, continue to exist in the future. I do agree with your second point. But my point was not necessarily about my personal opinion - my point was that organizations are often concerned about this (e.g. my boss) - and that makes it difficult to commit to a smaller, closed-source or hosted vendor.
I share the same concerns as you. This looks like a great product, but it needs a big amount of trust and commitment to get any value from it. Usually these kind of services launches with a boom, start giving huge discounts shortly after and then shuts down silently.
Is your problem related to availability or continuity of the service? Things that could help their, a usable export for the first case. And an insight into the API architecture for achieving scalability and availability for the second.
I've been playing with Prismic.io during this beta period and think it looks like an awesome product with great potential, but I just can't bring myself to actually use the writing side of it for any length of time.
Is there a way to turn off all the skeuomorphic design elements? Paper background? Lots of sliding panels, it's really hard to navigate around and very busy, even on a big screen. I think they need to completely cut it back and simplify, and I'd use it in a heartbeat.
The API based separation is a good idea for real sites (vs blogs), I think it will catch on and is a much better design than the all in one CMS design behind things like Wordpress, Drupal or Ghost.
We call it the "activity". It exists in two different fashions: you can view the one of the whole repository, or just focus on the one of a given document.
For your front-end, you can use absolutely everything you want! Open-source template, or anything; I usually use Bootstrap3, because I'm a huge fan myself. :)
And to answer your last question: we're not using Yahoo's PureCSS in the writing-room.
The largest obstacle for me to adopt such a system is that it requires me to bet my company's content on your system being around. I've looked at, for example, Webpop which is different but has some similar ideas - but I can't get away from the fact that Webpop may or may not be around in a year, so betting on it isn't something I would want to do.
That's what continues to push me to Wordpress and the like, although recently I've been spending more time with static web generators like Harp and DocPad. Those have a similar issue - my boss saying to me "Well, I know we can find Wordpress developers, but will wevbe able to find a Harp developer?"