Can you help me understand exactly what this does, and how it is better than basic CMS?
(not being a brat, I'm actually curious. It's just that I just couldn't quite figure it out by reading the website at a quick glance, which you could also take as feedback I guess)
Imagine you want to build a hotel booking app, with content scattered throughout the site. But because it's an app, it doesn't make sense to build out from a CMS (in the good old "This needs editable text, let's use Wordpress as the base!" way).
If you did you'd end up with many one-line bits of text that can be edited, out of context. Well, Prismic doesn't provide context AFAICT, but it does provide much nicer writing tools.
Beyond that I don't have a great understanding yet. I can't see how you'd associate new text with objects in your app (or even if they should be maintained outside); it doesn't handle the generate-URLs-on-the-fly-from-my-routing-system so they don't break when URLs are re-structured...
..or where assets are stored, or (if it's actually for longer-form writing than I'm considering) why you'd choose it instead of Wordpress.
I like the UI, I like the concept, but like you I'm struggling to think laterally enough for the use-cases.
I think the main difference it that _you_ display the informations (instead of modifying a template).
I would say:
- You write your content in a WYSIWYG like editor (no need to build a new one)
- The content is structured: you explicitly define which kind of information you want (the editor will be adapted accordingly).
- It provides an API to get your informations. So you can build a website using your techno (say Ruby on Rails) which fetches the content from prismic.io.
- There are also development kits to make this part more easily.
- More technical: it's cache friendly. An URL can be cached infinitely, the content it returns will never change.
By the way you can use prismic.io to manage the content of an existing website or mobile application.
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.
Comments
Can you help me understand exactly what this does, and how it is better than basic CMS? (not being a brat, I'm actually curious. It's just that I just couldn't quite figure it out by reading the website at a quick glance, which you could also take as feedback I guess)
Imagine you want to build a hotel booking app, with content scattered throughout the site. But because it's an app, it doesn't make sense to build out from a CMS (in the good old "This needs editable text, let's use Wordpress as the base!" way).
If you did you'd end up with many one-line bits of text that can be edited, out of context. Well, Prismic doesn't provide context AFAICT, but it does provide much nicer writing tools.
Beyond that I don't have a great understanding yet. I can't see how you'd associate new text with objects in your app (or even if they should be maintained outside); it doesn't handle the generate-URLs-on-the-fly-from-my-routing-system so they don't break when URLs are re-structured...
..or where assets are stored, or (if it's actually for longer-form writing than I'm considering) why you'd choose it instead of Wordpress.
I like the UI, I like the concept, but like you I'm struggling to think laterally enough for the use-cases.
I think the main difference it that _you_ display the informations (instead of modifying a template).
I would say: - You write your content in a WYSIWYG like editor (no need to build a new one) - The content is structured: you explicitly define which kind of information you want (the editor will be adapted accordingly). - It provides an API to get your informations. So you can build a website using your techno (say Ruby on Rails) which fetches the content from prismic.io. - There are also development kits to make this part more easily. - More technical: it's cache friendly. An URL can be cached infinitely, the content it returns will never change.
By the way you can use prismic.io to manage the content of an existing website or mobile application.
maybe this blog post can help https://blog.prismic.io/Ux-QjgEAAGMGit8h/writing-room-and-co...
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.