Prismic FAQ: direct answers to common questions Have some questions about Prismic? We've put together some answers to some of the most commonly asked questions. It’s almost like talking to a human – maybe even better. On this page What is the value of Prismic What is Prismic in a nutshell What is a headless CMS What problems does Prismic solve What’s different about Prismic What is Prismic - slightly longer answer How is Prismic different from other CMSes What do people make with Prismic What kind of people can get the most out of Prismic What Prismic is not for Who Prismic is not for My question isn't listed here 🤔 What is the value of Prismic For everyone With Prismic, teams of developers and marketers/editors/content managers can create websites and apps with instantly updatable content and custom designs For developers Prismic enables front-end developers to build websites and apps using any technology, programming language, or framework: React, Angular, Node, Laravel, Rails, vanilla JS/PHP/Ruby, the list goes on For content managers and marketers Prismic makes content teams independent so that they can create new pages without having to ask for help from developers For PMs and buyers Prismic makes content management more efficient by selectively addressing the needs of developers and content teams. For developers, the headless API-centric architecture enables them to use any technology they like, which increases the speed and quality of development. Meanwhile, the content editing features make marketers and content managers more independent, resulting in faster time-to-market for new materials. What is Prismic in a nutshell A CMS – content management system Specifically, a headless, API-first, hosted, proprietary CMS – with a web app for creating and publishing content What is a headless CMS It's a CMS with an API. We also wrote a 500-word article that explains the concept of headless in more detail. What problems does Prismic solve Building websites is still surprisingly hard: most CMSes make either developers or content managers suffer (often both) Having experienced that first-hand, we set out to create a CMS that would make it possible to control content in websites and apps in a way that makes things easier for both developers and editors. What’s different about Prismic Developers can work with any technology What: Developers can use their preferred tools and programming languages to build websites and apps Why: Because of the Prismic content API and SDKs for major languages Content teams become independent What: Content managers can update content in websites and apps instantly and independently Why: Because editors can create, edit, and publish content in the authoring environment (Writing Room) without involving developers No infrastructure management What: Prismic doesn’t require infrastructure setup, configuration, or maintenance - so teams can start building a project immediately. Why: The Prismic team maintains its own content infrastructure (the “cloud”) What is Prismic - slightly longer answer Technically speaking, Prismic is 2 things: Writing Room. The place where content managers work. It’s a web application. It's very similar to what's called "admin panel" in many other CMSes. API & content backend. The place where all content is stored. Developers query the API when they need to plug some content into their project. How is Prismic different from other CMSes Compatible with every technology Developers can use whichever tools/languages they prefer for their projects Headless, not monolith Developers get to build a custom frontend instead of working with template configurations or proprietary technology API-first, not WYSIWIG All content created in Prismic is available via an API. Allowing it to be fetched by any app. Hosted, not maintain-it-yourself The Prismic team maintains both the software and infrastructure so that teams can start working on their projects immediately. Proprietary, not open source The Prismic team maintains the software and infrastructure behind Prismic and provides support if anything goes wrong. We love the open-source philosophy and we use a lot of open-source tools ourselves. So far we've been focusing on building a profitable company, but we do intend to make some parts of Prismic open-source in the future. Editing environment built around content team workflows Prismic is not just a UI on top of a database. It provides important editorial features such as rich editor, collaborative editing, live and shareable previews, dynamic layouts, revision history, and scheduled publishing. What do people make with Prismic Projects with custom design and UX which are hard or impossible to make with existing website builders (Wix, Squarespace, etc.) or template-based CMSes (Drupal, WordPress, Joomla, etc.) Websites: landing pages, e-commerce websites, editorial projects, promo websites, static sites, etc. Native apps of any kind Anything else that is online and involves content and can be built by a developer What kind of people can get the most out of Prismic Just about anyone, from individual developers right up to large teams in enterprise environments. But the majority of our users meet some, if not all, of the following criteria: want to choose their own technology stack like to customize design and UX don’t want to maintain CMS-related infrastructure prefer to iterate and release projects quickly And have the following job titles Content and marketing teams use Prismic to edit words and pictures in websites and apps Developers use Prismic to build frontends of said websites and apps Designers use Prismic to create unique looking websites What Prismic is not for Simple 1-page websites – because there are simpler tools to achieve that goal, such as visual website builders (Wix, Squarespace, etc.) Mobile/data backend like Parse – because Prismic addresses workflows that are specific to content management and authoring experience (it's not just an API on top of a database) We're constantly thinking of more things to add to this list Who Prismic is not for Teams without developers (or that can't outsource to developers for the initial setup) Teams that prefer visual website builders Teams that insist on maintaining their own servers Teams that don't put an emphasis on authoring experience My question isn't listed here 🤔 The best place to find answers to Prismic related question, both common and unique, is our Community Forum.