The Library is where every syncable data type on your site lives, each as its own collapsible section: WordPress posts, pages, menus, widgets, media, categories, tags, and auto-discovered custom post types and taxonomies, plus any custom data sources you define, and, when Bricks is installed, Templates, Components, Bricks Settings, and Global Styles.
Every section offers the same controls:
Before exporting post-type content, preview its dependencies so the related data travels with it. The preview counts what the item actually relies on: media (including images embedded in classic content), terms, custom fields, and parent posts.
That preview is the moment to decide how wide the release should be. Exporting a page without its media leaves broken images on the target, and exporting it without its parent can flatten it out of a page tree. When the preview shows dependencies you did not expect, that is usually a sign the change is bigger than it looked.
The checkboxes in any Library section drive selective export, selective push, and selective workflow runs. Check nothing and the action applies to the whole section.
The receiving site records what every push changes. In Settings → Remotes, Undo last push shows what the last push to that remote changed and puts it back exactly: changed posts, pages and templates return to how they were, items the push added are removed, and custom fields, terms, translation links, settings, custom tables and replaced images are restored too.
Untick items to undo only some of them; the rest of the push stays undoable. Items edited on the remote since the push are flagged, because those edits would be lost. Undo steps back one push at a time, newest first, through the last 10 pushes.
On WPML and Polylang sites, each language version of a post, page, custom post type entry or Bricks template is its own item in the Library. Posts outside the default language are stored with the language in the file name, for example page-contact__en.json next to page-contact.json, so translations that share a slug never overwrite each other.
On import, every item is matched only against posts in its own language, so a Romanian page updates the Romanian page and an English page updates the English one. Existing posts are updated in place and keep their translation links. New translations are linked into the right translation group automatically, even when a translation arrives before its original. Content can also move between a WPML site and a Polylang site that use the same language codes.
By default a push only ever adds translation links. On Polylang sites you can switch on Mirror translation links from the sending site in Settings → General: the translation group of arriving content is then made to match the sender's.
The multilingual plugin must be active on both sites, with the same languages. Test connection in Settings → Remotes checks this.
