Get Started with Express
This technology has no Slice Machine integration
This framework has no integration with Prismic's developer tool, Slice Machine. You can still build a Prismic website with this technology by using Prismic's Legacy Builder. However, if you're starting a new project with Prismic, we strongly recommend using a technology that integrates with Slice Machine: Next.js or Nuxt.
This guide will teach you how to create a web app with Express and Prismic.
If you want to jump right in, proceed to the Install step:
Curious about pricing? Prismic has an unlimited free tier for projects with one user. To learn more, see our pricing page:
What technical skills do I need?
If a developer is setting up Prismic for you: You won't need any technical knowledge. Prismic is designed to be used by anyone.
Why should I use Prismic with Express?
Express is the most commonly used server-side rendering framework in the Node.js ecosystem. It makes your website dynamic and allows you to create website routes and middlewares. You can use many templating systems (such as Pug or EJS) with Express. However, Express doesn't have a default tool for managing content.
Content, the most important part of your website (the reason you have a website), deserves a tool. Prismic is the tool for your content. It enables dynamic content in your app. Prismic also formats content as slice components that map to your Express templates.
Moreover, Prismic adds some superpowers to your websites, like image optimization, content versioning, scheduling, and user roles.
Have a question or comment?
This documentation is still in beta. If you have ideas for how to improve it, we'd love to hear from you at the Prismic Community Forum.
Six steps to get started
This guide will walk you through six steps to deploying your website and creating content.
Here's what we'll go over:
See example projects below. (Note: These examples use Pug templating. Examples with EJS are forthcoming.)
Was this article helpful?
Can't find what you're looking for? Spot an error in the documentation? Get in touch with us on our Community Forum or using the feedback form above.