11–20 of 20 posts
what do you call that facebook-esque feed story? Is there an open source template that one can use in their projects?
is it using yahoo's PureCSS?
question about the screenshot here https://prismic-io.s3.amazonaws.com/wroom/6018bdb7cc0be70b68... what do you call that facebook-esque feed story? Is there an open source template that one can use in their projects? is it using yahoo's PureCSS?
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.
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…
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.
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…
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.
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…
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?
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…
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
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…
It exists: Apache Jackrabbit + Apache Sling 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.
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.
Earlier quoted context omitted.
It exists: Apache Jackrabbit + Apache Sling 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 han…
Earlier quoted context omitted.
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?
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…
