Matt J.

Ah okay - a timeline I believe. Will do some testing.

I wonder if understanding which elements to look out for that might not import correctly would at least build back your confidence that the process works 90% of the time?

if you are doing side-by-side, it might be worth just copy/pasting the content over - just saying that makes me so sad though. ugh

yeah totally get it - the process is locked in for you guys

The legal page is likely one big rich text field within the webflow component, blog posts would also not work. Are there are other components or element types that you are noticing where copy is not importing?

ahh okay hmm it might be the rich text field elements - those have not been reliable for a very long time - its not as simple as it sounds actually - very complicated.

Ana T. Gosh Ana, that sounds incredibly frustrating. Very sorry for the issues here. I'll do some testing to see if I can replicate this. One potential workaround that is not super ideal but you can test it out and let me know is copying/pasting the pages 1-by-1. Not sure how big your project is, so this might be a completely unreasonable workaround. I typically handle copy edits further down the process line - either in Figjam or Webflow/Pastel but I realize that everyone's workflows can be different. Content is one of the most painful pieces, so I can imagine how painful it has been when it doesn't import correctly too. I'll see what I can find.

Cliff B. Marc-André J. Hey guys, check out this FAQ that goes over how to do the same concept but to a different component. https://relume.notion.site/How-to-add-more-content-to-Layout-348-f0f075378c6a4eafb066d3657ff1a19d?source=copy_link Also keep in mind that Webflow has updated their interactions to use GSAP by default so you may need to toggle to classic interactions to see where the interactions are applied. What might be slightly different for this component is timing the keyframes a little within the interactions - so play around with it.

Alexander S. apologies for the bug - thanks for flagging it.

It doesn't appear we've made any changes to this recently - so its likely that this has been broken for awhile, and unfortunately our small but mighty team is tied up and likely wouldn't be able to resolve this immediately. I've created a bug ticket for it but I don't have an ETA. In some cases, its possible that this component will show up in the search, but was not actually built out in React. I would refer to the React library directly and use the filtering options to see which components are actually available. Apologies for the issues here.