You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm curious if Puck can support "external" components for on-site editing – components that aren't part of the source code where Puck is installed. Some site builders let you register your components and define their properties (similar to what Puck already supports). Then, you use a component like <Render> to actually render the page.
This approach allows you to either render the site within an iframe or embed the editor on the page for on-site editing.
Another advantage is cross-platform support. While Puck is a React library, the rendering part could work on React, Vue, or even Web components.
Would it be possible for Puck to control a remote <Preview> component?
Hi! Congrats on this fantastic project!
I'm curious if Puck can support "external" components for on-site editing – components that aren't part of the source code where Puck is installed. Some site builders let you register your components and define their properties (similar to what Puck already supports). Then, you use a component like
<Render>
to actually render the page.This approach allows you to either render the site within an iframe or embed the editor on the page for on-site editing.
Another advantage is cross-platform support. While Puck is a React library, the rendering part could work on React, Vue, or even Web components.
Would it be possible for Puck to control a remote
<Preview>
component?Related to: #302
The text was updated successfully, but these errors were encountered: