The paste itself takes a second. Everything that goes wrong was already decided before you pressed the key, which is good news: all four failure modes are checkable in advance.
Check the class namespace#
A section that ships with a class called card will collide with the card class already in your project, and Webflow will merge them. Namespaced classes — lc-card, lc-card-media — cannot collide, and you can find and remove every one of them later with a single search.
Check for global tag selectors#
If the section styles h2 or a or body directly, pasting it restyles your entire site. This is the one that produces the panicked message on a Friday afternoon. Tag selectors are legitimate in a project you own end to end and never legitimate in a distributable section.
How to check quickly#
- Open the section in the Wondrstack preview and switch to the CSS pane.
- Search for selectors that start with a bare tag name rather than a dot.
- If you find any, use the sanitised export option instead of the raw one.
Paste into a wrapper#
Create an empty div, give it a section-scoped class, and paste inside it. This gives you one element to select, move or delete, and it gives the section a scoping boundary if you later need to constrain something with a descendant selector.
Bind variables first#
If your project already defines colour and type variables, bind the section to them before pasting. Wondrstack does this at export time when you pick a bound system, so what lands is already using your values. Rebinding after the fact means touching every style on the section by hand.
