Apps, Pages, components, and data
Understanding four layers makes the v9 editor easier to navigate.
An App is the saved map configuration that you embed with a MapSVG shortcode. It contains its Pages, component settings, Layout, templates, and other presentation options. The map list and open workspace tabs let you move between Apps.
An App has editable drafts, one current Published version, and History. Editing a draft does not change the Published configuration until you publish. See Drafts.
Page and Layout
Section titled “Page and Layout”The component tree shows the current Page under App. Its containers hold the visible components. Layout determines where those containers and components appear on Desktop, Tablet, and Mobile.
Do not confuse this Page with the WordPress page that contains your shortcode. The WordPress page is the host; the MapSVG Page is part of the embedded App.
Components
Section titled “Components”Map, Filters, Directory, Tooltip, Popover, and other components each own part of the experience. Select a component in the tree to inspect its available Settings, Interactions, Styles, and Code panels. Some components have only Settings and therefore do not show a panel-switching toolbar.
Map contains its fixed internal components, including Region and Marker. These are selected for configuration, not moved into arbitrary page containers.
Collections, Queries, and bindings
Section titled “Collections, Queries, and bindings”A Collection stores records or represents a source such as WordPress posts. A Query defines which records and fields to return. A Page’s Objects and Regions bindings select those Queries.
Directory and Filters choose one of the Page’s bindings. They do not independently choose a Collection. Two components using the same binding share its filtering and pagination.
Data is shared. Publishing or restoring an App configuration does not roll back edits to database records, Collection fields, or shared Query definitions. Keep data backups independently of App version history.