Widget
Widget is the settings page of a single widget. Where the Gallery says which widgets exist and Layout says where they sit, this panel says how one of them behaves.
It opens whenever you click a widget card in the Gallery, or a widget row in the Layout tree. The rail button reopens the last widget you looked at.
The header switcher
Section titled “The header switcher”The dropdown at the top lists every widget currently on your map, by the name it displays. Switching there is the fastest way to go from one widget’s settings to another’s without going back to the Gallery each time.
What every widget has
Section titled “What every widget has”Whatever the widget, three things are always there.
- Enabled: the same switch as the Gallery card, so you can turn a widget off from its own page.
- Position: the map corner it sits in, when it is a corner widget. A widget placed in a region has no corner to pick, and the picker is absent rather than inert.
- Display name: the label your audience reads. Rename a Legend to What the colors mean and that is what appears on the map, in the Layout tree and in the switcher above.
Under those, the widget’s own parameters. A widget with nothing to configure says so plainly.
What the parameters decide
Section titled “What the parameters decide”This is the panel where the two level model of ALIGN becomes concrete. Each widget’s parameters answer two different questions.
What the widget does by default. The Measure widget opens in the unit you chose, the Terrain widget applies the exaggeration you set, the Bookmarks widget publishes the views you saved, the Legend shows the items you curated.
What your audience may change. Most widgets carry exposure switches: whether a visitor can change the unit, unfold the panel, add their own bookmark, adjust the exaggeration. Turn them off and the widget becomes a display, turn them on and it becomes a tool.
Whatever a visitor changes on the map stays in their session. It never writes back into your configuration.
Third party widgets
Section titled “Third party widgets”Directions, Reverse geocode and Street View send data to an outside service to work. Their parameters carry a permanent notice saying what leaves ALIGN, and a provider picker. The account key itself is resolved at runtime from your Integrations and is never written into the saved map.
Saved with your map
Section titled “Saved with your map”Every parameter here is saved with your web map, and travels into an application built from that map. It is also the exact surface the AI Assistant writes to when you ask it to set a widget up, which is why its work shows up in this panel like your own.