My technology is set up to read from the
io.prismic.preview cookie and pass this to the
Prismic-Ref when making a GraphQL request. This has been working wonderfully for me and my client. However, it seems to have recently stopped working! Here's the steps to reproduce.
Steps to Reproduce:
- Visit prismic.io Preview
- In the console run "document.cookie"
If I click "Planned" then choose a release and click "Preview on Production" it does work.
As a side note:
I feel like there's been a move in Prismic recently to dumb down the documentation and direct people to the maintained projects to handle the heavy lifting. I want to say that, as a developer, I deeply disagree with this ethos.
The Vanilla JS docs say that you should use one of the frameworks. And I don't see any docs anymore that explains how the preview cookie is set, or how setting
Prismic-Ref controls the response in GraphQL.
As a developer, I'd like to know how things work on a low level so I can build my own. I don't want to use any of your frontend codebases. Users should have all the tools freely available to build their own frontend tech.
This takes some of the responsibility off of the Prismic dev team if people can build their own integrations as well.
For example, I'm building a Rails project that integrates with Prismic, and I ended up building all my own renderers because the prismic/rails project is outdated and too opinionated. I'm happy to share this with the community! But it's impossible for me to maintain a project like this if you hide these details about how the product works from your technically advanced users.
Please bring back the docs that explain how the
io.prismic.preview cookie is set and how the
Prismic-Ref is set in GraphQL. Share low-level details about what Prismic is expecting from a link-resolver so that people can build their own. My clients and I can't use a static site generator because we need login abilities! So all your Hugo, Nuxt, etc doesn't work for us at all.