...and Play is really quite awesome, thanks Guillaume and Sadache! Thanks for the open bar you guys sponsored after Scala.io Paris conference as well ;-)
We're working on a different website for explaining the approach of the product.
Do you think that the following fails at explaining the idea of the product?
prismic.io is a different approach to content management.
It features a Writing Room for content writers to author and manage content,
and a Content Query Api for developers to integrate managed content into any website or app.
The paragraph you've posted there is very helpful - it gives me more of an idea of what the product as a whole does, and it does sound really quite interesting!
Even doing something like including that at the top of the current website would work wonders for giving an explanation before delving into finer details.
Thanks for the valuable feedback.
Here is a question, do you think the following explains well the product?
"prismic.io is a different approach to content management.
It features a Writing Room for content writers to author and manage content,
and a Content Query Api for developers to integrate managed content into any website or app."
I think the idea is that you expose the content through an API which can be inserted anywhere.
Prismic.io, an API for content.
Prismic.io is a content management system that only publishes through an API. Let your writers focus on writing and your developers and designers can focus on layout.
"It features a Writing Room for content writers to author and manage content"
I don't know why I'm supposed to want a Writing Room. What makes it more desirable than the post entry pages I'm used to? I think a brief explanation of what value the Writing Room adds would be helpful.
"a Content Query Api for developers to integrate managed content into any website or app."
This should be another sentence and may not be considered a feature depending on who your target is. Also, "integrate managed content" is a little hard to understand. Maybe "embed content" instead.
It is very hard to talk technical specificities on the homepage while staying understandable for everyone. There is a big room for improvement for sure (and that's what we're targeting), so thanks for your feedback.
Also we'll keep working on our API and development kits documentation, any help is appreciated.
Take this as a positive criticism. Good looking website but it me took too long to get it. Not really sure if I still fully got it.
The site doesn't really doesn't say what it is. "Manage your content in one place. Display it your way. Using your favorite technology. prismic.io is a different approach to content management." - all that seems like filler text to me.
I watched the video. It was way too complex. All the close up shots, error messages, etc. Make it simpler.
btw. I wouldn't go searching answer to API questions in a blog.
Put simply, it is a backend called "Writing Room" for managing and structuring content, and an Restful API for developers to integrate this content in any technology (websites or apps).
So the pitch is, it's a managed CMS backend that gets your content-creators working immediately while you dev the rest of the site. Then you just run queries to pull the content.
Not a bad idea; worth checking out if you're in the market, I figure.
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.
Don't hesitate to ask questions!