Re:Writing Room and Content Query API, ideas for reshaping C...
by phpnode on Thursday March 13, 2014 @11:02AM
(#7392225)
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?
[ Parent
| on HN ]
Re:Writing Room and Content Query API, ideas for reshaping C...
by inthewoods on Thursday March 13, 2014 @01:40PM
(#7393350)
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?
Re:Writing Room and Content Query API, ideas for reshaping C...
by rudyrigot on Thursday March 13, 2014 @02:15PM
(#7393623)
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/