Replicate Webflow website dynamically


I am building a website for my client on Webflow. During the project, the client came up with the idea that he wanted a second website that would be a copy of the first one. The content from Webflow is to be uploaded dynamically (e.g. every 4 hours) to a local environment on another server. Ultimately the sites are to have the same content, only the copy will be extended with components written in React.

We came up with the solution to use DevLink to export the pages as components and publish them to the local environment.

My questions to the above are:

  1. can you recommend a solution (other than DevLink) to dynamically update content on the local environment based on the content posted on Webflow?

  2. the DevLink components were a bit different from the components on Webflow (e.g. different padding). Is there any way to streamline the uploading of components so that they are mirrored at 100%?

  3. There is also the idea of duplicating the page on Webflow and adding React components to it.

a) Is this possible? Is there a stable solution for this?

b) How can content be dynamically replicated from page A running on Webflow to page B running on Webflow? I am mainly concerned with static page content.

An example of a component made in React: a multistep form with about 100 questions, at the end displaying a kayak chart with the user’s strengths and weaknesses.

Here is my site Read-Only: LINK
(how to share your site Read-Only link)

I’m not clear on your end reason for having two sites, etc. however here’s how I’d accomplish it.

Webflow design build for the React components, using Devlink to export them. Your padding issue is easily solveable and probably related to your container, not anything to do with Webflow or Devlink.

Site 1 is Webflow-hosted with your static page content.
You can update content anytime and republish.

Site 2 is self-hosted, and contains your embedded React components.
The “duplicate content” is served by reverse proxy, so essentially you get exactly whatever Site 1 is on your Site 2 domain, plus whatever changes your RP makes to e.g. embed React components.

There are alternatives, like catching Publish webhook events and using the API to dissect your static pages, but it’s far more work for a far more fragile end system.

Thank you @memetican for your answer.

Do you think exporting the whole site as one component will be a problem? Is it better to export each section one by one? Or does it not matter?

As in multiple pages, with navigation?
I’ve never seen that done, and I don’t know how it would work but you could try it.

That’s a very different approach from the RP I suggested.