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.
Comments
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.