A few things. I would expect a writing application to have incredible copywriting. You have to out-write the writers! Here are some examples where the text could be improved, though really the whole page needs to be rewritten using the inverted pyramid. 1. "Api" should be "API". 2. "You're the skilled developer, so why would it be ok to settle for technical constraints as soon as there's manageable content involved?"…
I really hate this kind of comments. It wouldn't hurt to be a little constructive while criticising someone's work.
Prismic.io goes live
21–30 of 54 posts
Re: Prismic.io goes live
#22I would suggest to clean up landing page and clearly explain what is prismic.io. I tried to figure out that from the landing page, but no luck. And if you are not native English speaker - use that in your advantage. Write short sentences.
Re: Prismic.io goes live
#23It's frustrating as this product looks like a great idea and looks well done, but you're leaving out all the important bits of information that I'd want to know immediately. Do I have to request the the content from prismic with every request? Is it done client or server side? What kind of caching will I be able to do my end? What happens when you go down? That website and especially the video are terrible at communi…
We've answered most of your question in our blog, take a look at https://blog.prismic.io 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. Our API has a cache…
Re: Prismic.io goes live
#24A few things. I would expect a writing application to have incredible copywriting. You have to out-write the writers! Here are some examples where the text could be improved, though really the whole page needs to be rewritten using the inverted pyramid. 1. "Api" should be "API". 2. "You're the skilled developer, so why would it be ok to settle for technical constraints as soon as there's manageable content involved?"…
I really hate this kind of comments. It wouldn't hurt to be a little constructive while criticising someone's work.
Re: Prismic.io goes live
#25I'd love to see footage of the user testing on this. I might be wrong but I can imagine many a furrowed brow on initial exposure.
Update - Either I'm really dumb or adding a picture to a post is rather confusing.
I was really expecting a completely stellar UX to be the main selling point. It's a very pretty UX but it's not immediately intuitive. Which leads me to wonder what the main selling point of this actually is. I kind of like the idea of decoupling content from the code that generates the website but that's an abstraction that many will struggle with.
It's not really any worse than what we're currently expecting content authors to work with (Wordpress et al) - but it's not significantly better either. So it lives or dies on the value of the decoupling - which I'm struggling to feel is a big enough win.
Re: Prismic.io goes live
#26Re: Prismic.io goes live
#27Re: Prismic.io goes live
#28A) It's not the same as thing X B) It's better than thing Y, because of Z C) Their Q (which is part of their product) is really really good!
To someone landing on the page, that doesn't tell me what they do on a grander, more abstract scale, it only gives me a pinhole view of parts of their app, and thus prevents me from seeing the bigger picture. I'm sure the product as a whole is great (after all, I know each part is great), but I still have no idea what the product as a whole does!
I've read the FAQ, and I still can't quite figure out what this is offering. Can anyone condense this into a single paragraph (or better, sentence) that describes concisely, and completely what prismic does? I really can't fathom it from their website...
Re: Prismic.io goes live
#291. Define all document types (document metadata and structure) in their custom JSON.
2. They build pretty looking CRUD forms based off the JSON so non technical content writers can fill in and manage content.
3. Expose all documents via a REST API with a bespoke query language.
4. Allow content to be edited collaboratively and changes to be scheduled / buffered.
That's about it, actually. Would work very well when I build a site for my mum's chocolate shop.
Re: Prismic.io goes live
#30A few suggestions: * Make it possible to "Tab" between fields, same for using "Cmd-Return", "Cmd-A", ... * Inserting an image is really ankward, as soon as I upload it, I expect it to be in the article/product/... but it's not, I have to "Select" it, and then choose some kind of dimensions, and the UI/UX for it is not user-friendly, I think you should show the image in the article images sections, and then have small…
There will definitely be support for several languages in the writing-room too.
For our pricing all of the answers to your questions are here: https://prismic.io/pricing
Thanks for liking it! :)