Questions about CMS Live preview features (ex Payload)

[Zmove]

Hello,

I'm really interested by webstudio (in fact, just bought a lifetime licence ^^) and I wonder how the CMS features can integrate with some CMS live preview features.

With webstudio, we have an incredible tool to live preview standard page, and with the new content mode, it's perfect for clients.

Lets imagine that client also have a blog managed with a CMS that have live preview system (lets take payload as an example)

Does webstudio can integrate with that features, gor example getting the payload backoffice to create / edit a blog post, with webstudio loaded in the live preview side, and being ajusted in real time with the content I'm editing with payload.

Is it doable actually ?

Thank you for your explainations

Best regards

[kof]

We haven't tried

[Zmove]

Thank you for your answer. I'm interested by some feedback if somebody already tried that kind of things. I'm looking for a way to maximize the user experience when using an external CMS to create the feel, as much as possible, of an integrated cms

[kof]

I can see 2 ways of how this can be working:

1. Published site connected to live data over api so oyu can just open the published site. Question is if payload has drafts and how these can be shown. One could publish the site on wstd domain (staging) and make the api calls with "draft" flag or something like that if there are drafts or optionally just not link the drafted pages yet to production and open them via url manually

2. Using payload preview - generate the webstudio site using CLI, after that it could be possible to open it inside payload like any other react app, in the end webstudio site is just a react app. and then go the usual route. In this case previews are meant for content, not for design changes, even though design changes are also possible with additional sync call.

@jmikrut wanna collaborate on this?