The Prismic blog Product announcements, news, and thoughts on content management & software development from the Prismic team

Writing Room

September 11,2020

Changes to how we handle SVG's

We have recently disabled the use of SVGs with the Imgix integration. The reasoning behind this is because of security vulnerabilities with SVGs, in that they can be injected with JS which could cause malicious behavior on your websites. Another reason for this decision is because the Imgix query parameters have no effect on SVGs. So from now on SVGs will be treated as files rather than images and because of this they will not be delivered from the the domain images.prismic, they will now come from our Amazon servers. The Team thought this change would not result in any breaking changes, but one case we didn’t foresee was people currently with SVGs and query params who update their documents and this is why we didn't communicate this earlier. This is our bad and we should have been more thorough in our testing.

By Phil Snow


June 11,2020

Development environments: a sandbox where you can test, try, and iterate safely

Few things are more important for your website development and maintenance than knowing that you can safely iterate and test new features without putting your live website at risk. But, fear no more, with Prismic’s new development environments feature you can easily clone your production environment and work on new iterations and designs in a separate and safe development environment.

By Edward Hewitt


June 07,2019

How Ueno chose their framework and why they went with Gatsby

In our latest video with Birkir, he and Sadek discuss how Ueno chose their framework and why they went with Gatsby. Choosing Gatsby and staying React-based allows for a component-based approach that makes it easy for projects to be divided whilst still allowing developers to easily collaborate and work independently. Their preference for a component-based approach is one of the main reasons that they like using Prismic as a CMS.

By Edward Hewitt


April 30,2019

How Next.js and Gatsby work and how they're different

New React frameworks are appearing constantly, so often in fact, that keeping up with all of the latest options takes a lot of work. Next.js and Gatsby are two of the most popular, particularly with Prismic users, so we invited We Bos to the studio to talk to Sadek about how each of them works, their ecosystems, and how they are different when it comes to rendering, data management, routing, and deployment.

By Edward Hewitt


April 05,2019

How to choose a tech stack for your website - Episode 1: Introduction

Not sure what the best build for your website is? Don't worry, you're not alone. Navigating the world of frameworks, technologies, and languages out there is not easy - even for experts - and each new build has new requirements. How to choose your tech stack is a question that we get a lot, so Nouha and Sadek decided to sit down in the Prismic Studio and share tips and advice on how to make your decisions.

By Edward Hewitt

Writing Room

June 05,2018

New feature: Set up new custom types faster by reusing existing content components

A quick reminder for those who haven’t used slices yet: slices are reusable content components that can be inserted into any custom type. Slices are good for recurring content elements that appear across different pages of a website: for example, a “headline + image + text paragraph” section that can appear on different landing pages with different layouts. The point of slices is to enable creating new pages without writing new code – so that content managers can create new pages independently.

By Renaud Bressand


July 03,2014

Geo-code your content: find documents around you!

Customising content in relation to one's geographic position (geo-coded content) has become very important in the past few years. For example, when looking for stores on the "Les Bonnes Choses" pastry shop website, it is very handy to be suggested the nearest store depending on your location. This kind of feature is now possible through's Content API thanks to a new document fragment named “GeoPoint”.

By Sébastien Renault


May 22,2014

Even faster API for faster websites: deliver API & media assets via a CDN

From the early design days, we architectured to provide extreme performance for websites and apps using our content API. Our API is designed to be elastically scalable. In addition, one of the key properties allowing us to achieve high performance is that all our API content calls can be cached forever. This is also true for the media assets linked by the documents: they can be cached forever as well.

By Guillaume Bort