Edit imported layouts
How Kindly recognizes repeated content and preserves existing layout structures.
Reference#
Imported and AI-built pages rarely use the theme's or the plugin's class names, and a page builder gives every card or
button its own generated class (elementor-element-f92ef34). The editor recognizes a set of alike things from what
the browser lays out instead: a grid, a flex row or a list whose children have the same shape (the same tags nested
the same way, classes ignored; two paragraphs or three count as the same). A typical imported button grid illustrates this: each .e-grid holds four button widgets with different classes, each <div><a><span><span>. A theme's own
named items, the plugin's blocks and table rows come first, exactly as before; this only fills in where nothing named
the items.
- In Simple, a button in such a grid has This button → Add another button / Remove this button in its settings. Remove takes the whole widget (its wrapper), never just the link, so no empty cell is left; the copy keeps the widget's classes and spans, says "New button", goes nowhere yet and opens its link settings. Cards (with a heading), photos, links and other items get the same.
- In Developer mode, Move, Duplicate and Delete on such a button act on its widget, and the + offers another of the same shape first (see above).
- What is never treated as one of a set: anything in live content, a form or its fields, menus and tab bars
(
nav,role=navigation/tablist/menu/…), table cells (rows have their own actions), blocks of different shapes side by side, and big blocks: with only two alike children, each must be small (at most 16 elements, with no grid or row of its own inside), so a two-column page layout isn't mistaken for two cards. A plain bulleted list is typed (Enter adds the next item); a list of links is a set of items. - The last one left: a layout seen with several this visit stays one (so the last button still offers Add another, and can't be removed on its own), and so does a lone item in a grid with several columns.
- Opening the editor changes nothing in this markup: no classes added, nothing converted. Copies get fresh IDs
(
freshIds) and every change is one Undo step.
An edited collection keeps a small data-ke-items identity with its existing shape. This lets the last item remain addable after saving and reopening on a phone, even when its grid has one column. The editor adds this identity only when a collection is changed. It does not convert or rewrite layouts just by opening them. Existing theme data-ce-item adapters keep their names and use the same whole-widget editing behavior.
Rich linked cards retain their headings, paragraphs and media when copied. A simple button copy instead opens its words and destination settings. The same repeated-content controls work in permitted site parts; menu, form and live-source internals remain managed by their own controls.
Developer Layout → Add content inside opens an exact insertion point for a section or container, including a grid that is itself a whole section. Its Same as these option adds a matching item; the other choices allow a deliberate custom addition.