There is an ongoing shift in content management from traditional CMS to headless CMS. A headless CMS allows you to completely separate your content management system from the presentation layer. The content is made available via API and can be consumed in any kind of frontend, from websites to mobile apps.
This is a companion discussion topic for the original entry at https://strapi.io/blog/handling-previews-in-a-headless-architecture
Did you test it with Strapi V4 ?
I already implemented the preview from a previous blog article, but some pieces were missing such as make Strapi env variable work on the client side.
The part about Next is straightforward, but you just implemented the preview API only for articles, though there’s chance people want it for every content type and handle this need additional logic (both on Strapi and Next).
Also, I have seen Strapi plugins handling this feature but didn’t test it myself, the best would be to add this as a native Strapi feature, as nearly every project needs it in my opinion