UPDATE: Statement from Prismic

[jodiedoubleday]

I know this is not the right place to put this but there have been a lot of frustration regarding Prismics lack of support with this Plugin and at the author, which as this is an open source plugin is unfair.

I want to put this here to ensure everyone understands the complexity of this plugin and the issues that have occurred

Gatsby-Prismic plugins: what’s going on?
https://prismic.io/blog/gatsby-prismic-plugins

[mad-gav]

Looks like they've deleted the post for some reason. I'd also like to know where we stand. We are using this plugin for some production sites as it was recommended by prismic. I'd like to know what we do about the future and the roadmap. Will this plugin be unsupported? will there be anymore updates? Will prismic stop supporting the technology behind this plugin?

[ohlr]

@mad-gav there is a statement from a prismic dev in the fork

[arnabonline]

For those who are interested, a cached version is here - http://webcache.googleusercontent.com/search?q=cache:A7zX4SVXopkJ:https://prismic.io/blog/gatsby-prismic-plugins

[matthewtgilbride]

Here is the response from a post I made in the developer community: https://community.prismic.io/t/what-is-the-approach-with-regard-to-gatsby-plugins/1538/4

[birkir]

Hmm okay cool! but really... forget about Gatsby.

https://twitter.com/birkirgudjonson/status/1294272212380397570

[trickydisco78]

Think this is making want to move away from prismic and use a cms that supports gatsby cloud. The changing advice from prismic hasn't been great .Particularly if you've invested in using the plugin for production sites. Just moving a site to next.js from Gatbsy isn't really an option to consider especially if you have a whole team skilled up on gatsby.

This is not to have a go at the work you've put in @birkir as an open source maintainer. I doff my cap to you with the work you've put in maintaining this so far. Not sure how i would do it with a full time role as well. well done