There's no mention of embedding or "white labeling" prismic within other applications. Is this possible? For example, within product X I need to manage quite a bit of content, but would rather not build in a CMS. Can we integrate Prismic to do the content management parts?
Since all of your content is structured and delivered through your API, you can simply pull it from your application, and use the content the way you want.
Look at me take an existing Bootstrap site, and inject content in it: https://blog.prismic.io/Ux-CMgEAAFwI9kFg/turn-a-bootstrap-th... (here in PHP, but you can use any technology you want). Here, it's a static Bootstrap site, but if your application was more complex, it wouldn't me more complicated to embed prismic.io powered content!
Maybe I wasn't very clear. What I'm interested is the reverse - within my application, using the Prismic UI to author content, that I then expose outside the application. I don't want my application's users to know or care about Prismic - they're just using my application. Then I can take the content they've authored and use it like normal either within my app, or external to my app, for example.
Comments
There's no mention of embedding or "white labeling" prismic within other applications. Is this possible? For example, within product X I need to manage quite a bit of content, but would rather not build in a CMS. Can we integrate Prismic to do the content management parts?
This is a great use case for prismic.io!
Since all of your content is structured and delivered through your API, you can simply pull it from your application, and use the content the way you want. Look at me take an existing Bootstrap site, and inject content in it: https://blog.prismic.io/Ux-CMgEAAFwI9kFg/turn-a-bootstrap-th... (here in PHP, but you can use any technology you want). Here, it's a static Bootstrap site, but if your application was more complex, it wouldn't me more complicated to embed prismic.io powered content!
Maybe I wasn't very clear. What I'm interested is the reverse - within my application, using the Prismic UI to author content, that I then expose outside the application. I don't want my application's users to know or care about Prismic - they're just using my application. Then I can take the content they've authored and use it like normal either within my app, or external to my app, for example.