@projektemacher/storymapjs 0.10.7 → 0.11.0

package/dist/docs/migration.html

@@ -36,6 +36,8 @@
                 <li><a class="button" href="./readme.html">README</a></li>
                 <li><a class="button" href="./migration.html">Migration guide</a></li>
                 <li><a class="button" href="./iiif.html">IIIF docs</a></li>
+                <li><a class="button" href="./authoring.html">Authoring</a></li>
+                <li><a class="button" href="./events.html">Events</a></li>
                 <li><a class="button" href="./api/index.html">API docs</a></li>
                 <li><a class="button" href="../index.html#help">Help</a></li>
             </ul>
@@ -153,6 +155,38 @@ are rendered wider with a visible track for contrast.</li>
 <td><code>font_css: &quot;stock:&lt;name&gt;&quot;</code> (or a path)</td>
 <td>paths now resolve against the page URL (not the library location), plus the font files ship via <code>@fontsource-utils/scss</code>; no separate font CSS link needed</td>
 </tr>
+<tr>
+<td><code>font_css: false</code> (bundler consumers)</td>
+<td><code>stock:&lt;name&gt;</code> resolves via <code>import.meta.url</code>, which only survives when this package is <em>not</em> processed by a bundler — bundling inlines <code>dist/js/storymap.js</code> into a chunk and the theme URL breaks. Instead <code>import &quot;@projektemacher/storymapjs/css/fonts/font.default.css&quot;</code> (fingerprinted, <code>files/</code> rebased by the bundler) and pass <code>font_css: false</code> for no injected <code>&lt;link&gt;</code>. <code>&quot;none&quot;</code> works too for JSON. A failing theme only warns</td>
+</tr>
+</tbody></table>
+<h2>A story with no map</h2>
+<p><code>map_type: &quot;none&quot;</code> runs the storymap as text and media only. Nothing is
+constructed: no <code>ol/Map</code>, no tile layer, no tile consent row, and the overview
+control is hidden. The slider panel takes the full width, because there is no
+map behind it to fade over.</p>
+<p>This is the shape a photo essay or a transcript-led story wants, and it is the
+one the map engine&#39;s unconditional construction used to make impossible. Note
+that <code>map_type: &quot;&quot;</code> and an absent <code>map_type</code> both still mean OpenStreetMap, and
+<code>map_type: null</code> now falls back to that default instead of throwing out of the
+constructor — absence is not reinterpreted, so no existing document changes
+meaning. Map-derived accessors (<code>getBaseLayer()</code>, <code>getMarkers()</code>, …) return
+their neutral values, and the map setters are no-ops.</p>
+<table>
+<thead>
+<tr>
+<th>Old</th>
+<th>New</th>
+</tr>
+</thead>
+<tbody><tr>
+<td>a text-only story with a dummy <code>map_type</code></td>
+<td><code>map_type: &quot;none&quot;</code></td>
+</tr>
+<tr>
+<td><code>map_type: null</code> (crashed the constructor)</td>
+<td>normalised to the default, <code>&quot;&quot;</code> → OSM</td>
+</tr>
 </tbody></table>
 <h2>Removed globals and exports</h2>
 <table>
@@ -197,7 +231,7 @@ are rendered wider with a visible track for contrast.</li>
 </thead>
 <tbody><tr>
 <td><code>vine</code> media type (service shut down)</td>
-<td>vine URLs fall back to the <code>website</code> iframe — use another media source for those slides</td>
+<td>vine URLs fall back to the <code>website</code> iframe — or paste the provider&#39;s <code>&lt;iframe&gt;</code> snippet into the slide text (sanitized, https-only); use another media source for those slides</td>
 </tr>
 <tr>
 <td>Juxtapose <code>frame/?uid=</code> embed URLs</td>
@@ -207,7 +241,26 @@ are rendered wider with a visible track for contrast.</li>
 <td>Twitter <code>@nickname</code> rendering</td>
 <td>tweets from <code>x.com</code> URLs are now parsed too (fixes <code>@undefined</code> nicknames); no migration needed</td>
 </tr>
+<tr>
+<td>Ricoh360/theta360 embeds (#391)</td>
+<td>service no longer available (won&#39;t fix) — paste the provider&#39;s <code>&lt;iframe&gt;</code> snippet into the slide text if the service returns</td>
+</tr>
 </tbody></table>
+<p>Extra media per slide (#358, partial): a slide takes <code>media_extra</code> (a list of
+further media items, rendered after the primary one) plus <code>media_layout</code>
+(<code>stack</code>, the default, or <code>row</code> for two side-by-side items). An <code>&lt;iframe&gt;</code>
+embed snippet pasted into the slide <code>text</code> field still renders sanitized
+(scripts, event handlers and non-https sources dropped) — keep that as the
+migration path for removed media types:</p>
+<pre><code class="language-html">&lt;p&gt;Extra footage:&lt;/p&gt;
+&lt;iframe
+    src=&quot;https://example.com/embed/123&quot;
+    width=&quot;560&quot;
+    height=&quot;315&quot;
+    frameborder=&quot;0&quot;
+    allowfullscreen
+&gt;&lt;/iframe&gt;
+</code></pre>
 <p><code>map_type: &quot;zoomify&quot;</code> is supported again (legacy): the image pyramid renders
 via the storymap data&#39;s <code>zoomify</code> options (<code>path</code>, <code>width</code>, <code>height</code>), using a
 JS warning instead of the previous removal error. Cropped edge/remainder tiles
@@ -219,29 +272,325 @@ storymap JSON sources.</p>
 <h2>Map engine: Leaflet → OpenLayers</h2>
 <ul>
 <li><code>storymap.map</code> now exposes the <strong>OpenLayers <code>Map</code></strong> instance instead of a
-Leaflet map. Port any direct Leaflet calls (e.g. <code>setView</code>, <code>flyTo</code>) to the
-OpenLayers API (<code>getView().animate(...)</code>, ...).</li>
+Leaflet map. Port any direct Leaflet calls to the OpenLayers API (table
+below). It is <code>null</code> until the map has been built.</li>
 <li>Markers are DOM overlays (<code>.vco-mapmarker</code> / <code>.vco-mapmarker-active</code>) like
 before; the mini map is an OpenLayers <code>OverviewMap</code> control.</li>
 <li>New basemap options: vector styles via <code>map_type: &quot;osm:&lt;style&gt;&quot;</code> (OpenFreeMap)
 or a Mapbox style JSON URL.</li>
+<li>The <code>Ol*</code> aliases re-exported from <code>src/main.ts</code> (<code>OlMap</code>, <code>OlView</code>,
+<code>OlLayer</code>, <code>OlTileLayer</code>, <code>OlVectorLayer</code>, <code>OlSource</code>, <code>OlProjection</code>) let
+a consumer type the map and layers without depending on <code>ol</code> directly;
+anything beyond those (features, geometries, coordinates) still needs <code>ol</code>.</li>
 </ul>
+<h3>Direct Leaflet calls → OpenLayers</h3>
+<p>Both maps are reachable from the same place (<code>storymap.map</code>), so only the
+call syntax changes:</p>
+<table>
+<thead>
+<tr>
+<th>Leaflet</th>
+<th>OpenLayers</th>
+</tr>
+</thead>
+<tbody><tr>
+<td><code>map.getCenter()</code></td>
+<td><code>map.getView().getCenter()</code> — panel-shifted, see below</td>
+</tr>
+<tr>
+<td><code>map.getZoom()</code></td>
+<td><code>map.getView().getZoom()</code></td>
+</tr>
+<tr>
+<td><code>map.setView(c, z)</code> / <code>map.fitBounds(b)</code></td>
+<td><code>map.getView().fit(extent, { size: map.getSize() })</code></td>
+</tr>
+<tr>
+<td><code>map.panTo(c)</code> / <code>map.flyTo(c, z)</code></td>
+<td><code>map.getView().animate({ center: c, duration: 300 })</code></td>
+</tr>
+<tr>
+<td><code>map.setZoom(z)</code></td>
+<td><code>map.getView().setZoom(z)</code> (or <code>.animate({ zoom: z })</code>)</td>
+</tr>
+<tr>
+<td><code>map.getSize()</code> / <code>map.getBounds()</code></td>
+<td><code>map.getSize()</code> / <code>map.getView().calculateExtent(map.getSize())</code></td>
+</tr>
+<tr>
+<td><code>map.on(&quot;moveend&quot;, fn)</code></td>
+<td><code>map.on(&quot;moveend&quot;, fn)</code> (same event names; <code>movestart</code>/<code>move</code> also exist)</td>
+</tr>
+<tr>
+<td><code>L.tileLayer(url, opts).addTo(map)</code></td>
+<td><code>new TileLayer({ source: new XYZ({ url, attributions }) }).setMap(map)</code></td>
+</tr>
+<tr>
+<td><code>L.control.attribution</code> / <code>L.control.zoom</code></td>
+<td>OL <code>Attribution</code> / <code>Zoom</code> controls (pass them via <code>map_options.controls</code>)</td>
+</tr>
+<tr>
+<td><code>map.getPane(&quot;overlayPane&quot;)</code></td>
+<td><code>map.getOverlayContainer()</code> (markers are DOM siblings, not OL features)</td>
+</tr>
+<tr>
+<td><code>map.invalidateSize()</code></td>
+<td><code>map.updateSize()</code></td>
+</tr>
+<tr>
+<td><code>map.remove()</code></td>
+<td><code>map.setTarget(undefined); map.dispose();</code> (or <code>storymap.dispose()</code>)</td>
+</tr>
+</tbody></table>
+<p>The exposed center is deliberately panel-shifted: in landscape the view is
+offset so the visible map sits left of the slide panel, which means
+<code>getView().getCenter()</code> does <strong>not</strong> equal the current slide&#39;s location.
+That is a display concern, not a data one — read the location from the
+slide, not from the view. There is intentionally no offset-aware getter;
+an earlier <code>_getMapCenter(offset)</code> parameter promised that correction and
+never applied it, so it was removed rather than left to mislead.
+| <code>map.options.crs</code> / <code>map.getPixelOrigin()</code> | <code>map.getView().getProjection()</code> / <code>map.getPixelFromCoordinate(coord)</code> |</p>
+<p>Marker positions are still DOM elements, so <code>marker.getLatLng()</code> has no
+equivalent — read the slide data (<code>storymap.data.stlides[n].location</code>) or use
+<code>storymap._map.getMarker(n).latLon()</code>.</p>
+<h3>Map and marker methods</h3>
+<p>The map/marker methods of the original viewer are still there with the same
+names and behaviour (<code>storymap._map.&lt;method&gt;()</code>, <code>marker.&lt;method&gt;()</code>); the OL
+engine implements them as thin wrappers over <code>storymap.map</code>. Two methods are
+deprecated no-ops and one is gone:</p>
+<table>
+<thead>
+<tr>
+<th>Original method</th>
+<th>Status</th>
+</tr>
+</thead>
+<tbody><tr>
+<td><code>updateDisplay</code>, <code>goTo</code>, <code>panTo</code>, <code>zoomTo</code>, <code>viewTo</code></td>
+<td>unchanged</td>
+</tr>
+<tr>
+<td><code>getBoundsZoom</code>, <code>markerOverview</code>, <code>calculateMarkerZooms</code></td>
+<td>unchanged (<code>getBoundsZoom()</code> now returns <code>number | undefined</code> instead of a falsy value)</td>
+</tr>
+<tr>
+<td><code>createMiniMap</code>, <code>createMarkers</code>, <code>createMarker</code></td>
+<td>unchanged</td>
+</tr>
+<tr>
+<td><code>setMapOffset</code>, <code>calculateMinMaxZoom</code>, <code>updateMinMaxZoom</code>, <code>initialMapLocation</code></td>
+<td>unchanged</td>
+</tr>
+<tr>
+<td><code>show()</code> / <code>hide()</code> (map and marker)</td>
+<td><strong>deprecated no-ops</strong> — they were already empty in the original viewer. Style <code>.vco-mapmarker</code> or use <code>marker.active(false)</code></td>
+</tr>
+<tr>
+<td><code>map.addTo(container)</code> / <code>map.removeFrom(container)</code></td>
+<td>unchanged — inherited from the <code>DomMixed</code> mixin: append/remove the map container and fire <code>added</code>/<code>removed</code>. The engine override re-targets and re-measures the OpenLayers viewport, so a move into a differently sized parent works</td>
+</tr>
+<tr>
+<td><code>marker.createPopup()</code></td>
+<td><strong>deprecated no-op</strong> — it never did anything upstream either (empty base body, commented-out Leaflet body), so the <code>map_popup</code> option that called it had no effect. Still accepted, still inert. Use <code>marker.openPopup()</code> / <code>storymap.openMarkerPopup(n)</code> instead</td>
+</tr>
+<tr>
+<td><code>marker.addTo()</code>, <code>marker.removeFrom()</code>, <code>marker.updateDisplay()</code>, <code>marker.active()</code>, <code>marker.location()</code></td>
+<td>unchanged</td>
+</tr>
+<tr>
+<td><code>marker.openPopup()</code> / <code>closePopup()</code> / <code>togglePopup()</code> / <code>isPopupEnabled()</code> / <code>popupOpen</code></td>
+<td><strong>new</strong> — programmatic control of the popup card (<code>marker: { popup: true }</code>); <code>openPopup()</code> returns false when disabled or not a real marker, <code>popupOpen</code> reports the state</td>
+</tr>
+<tr>
+<td><code>storymap.openMarkerPopup(n)</code> / <code>closeMarkerPopup(n?)</code> / <code>isPopupOpen(n)</code></td>
+<td><strong>new</strong> — open/close/query a stop&#39;s card from the viewer; <code>openMarkerPopup</code> navigates to <code>n</code> first and returns false (changing nothing) when disabled, out of range, disposed or mapless</td>
+</tr>
+</tbody></table>
+<p>Marker helpers that Leaflet provided on the marker object (<code>getLatLng</code>,
+<code>setIcon</code>, <code>bindPopup</code>) are gone; use <code>marker.latLon()</code>, the
+<code>.vco-mapmarker</code> element and your own DOM/CSS.</p>
+<h2>Reaching the map, layers and markers</h2>
+<p><code>storymap.map</code> is the raw <code>ol/Map</code> (typed as <code>OlMap | null</code> — it is set during
+construction, so check it before first use in an async setup). Everything the
+viewer keeps internally is available through accessors on <code>storymap</code> (and on
+<code>storymap._map</code> for the engine methods):</p>
+<table>
+<thead>
+<tr>
+<th>Accessor</th>
+<th>Returns</th>
+</tr>
+</thead>
+<tbody><tr>
+<td><code>getBaseLayer()</code></td>
+<td>the base tile/vector layer</td>
+</tr>
+<tr>
+<td><code>getOverlayLayers()</code> / <code>getOverlayLayer(i)</code></td>
+<td>overlay layers / one by index (<code>null</code> if out of range)</td>
+</tr>
+<tr>
+<td><code>getOverlayCount()</code></td>
+<td>number of overlays</td>
+</tr>
+<tr>
+<td><code>setOverlayVisible(i, on)</code> / <code>setOverlayOpacity(i, opacity)</code></td>
+<td>show/hide and fade one overlay</td>
+</tr>
+<tr>
+<td><code>getMinimap()</code></td>
+<td>the inner overview <code>ol/Map</code> (<code>OlMap | null</code>), not the <code>OverviewMap</code> control itself — there is no accessor for the control object</td>
+</tr>
+<tr>
+<td><code>getLine()</code> / <code>getLineActive()</code></td>
+<td>the full and the travelled route <code>VectorLayer</code></td>
+</tr>
+<tr>
+<td><code>getMarker(n)</code> / <code>getMarkers()</code></td>
+<td>one marker or all of them, in slide order</td>
+</tr>
+<tr>
+<td><code>setExtraAttributions(html)</code></td>
+<td>extra attribution HTML, listed after the source credits</td>
+</tr>
+<tr>
+<td><code>isImageSpace()</code></td>
+<td>whether the map is a IIIF image in image space (see below)</td>
+</tr>
+</tbody></table>
+<p><code>tile_source_factory</code> may return a full <code>ol/layer/Layer</code> (not just a source)
+anywhere a layer is built, so custom layers can carry their own opacity,
+z-index and events. A custom layer without a source (Allmaps&#39;
+<code>WarpedMapLayer</code>) passes through untouched; source reads go through a
+capability check, so it simply skips the tile-grid fits.</p>
+<p>The viewer reserves three z-index ranges and custom layers should stay out
+of them: <strong>0</strong> for the base tiles, <strong>1..n</strong> for the stacked <code>overlays[]</code>
+entries in order, and <strong>10/11</strong> for the full and travelled route lines. A
+custom layer with no explicit z-index lands wherever OpenLayers puts it,
+which is above the lines — set one explicitly if the layer must sit inside
+the stack.</p>
+<h3>Layer switcher</h3>
+<p><code>show_layers_control: true</code> adds a disclosure button to the menubar with
+basemap radios and overlay checkboxes. Basemap candidates come from
+<code>basemaps[]</code> (entry 0 is the initial basemap unless <code>map_type</code> says
+otherwise; omit for an overlays-only control); overlay rows come from the
+built <code>overlays[]</code> entries, so a malformed entry never gets a row and row
+<em>i</em> is always layer <em>i</em>. <code>label</code> may be a function for host i18n (re-invoked
+on <code>refreshLabels()</code>), <code>locked: true</code> renders a row checked and disabled,
+<code>control: false</code> hides a row without removing the overlay — but function
+labels survive only in constructor options, because <code>mergeData()</code> lets
+storymap JSON overwrite same-named option keys. A runtime basemap swap
+rebuilds layers but never the view, so candidates needing another
+projection are refused with a warning; switching fires <code>basemapchange</code> /
+<code>overlaychange</code>, and the visitor&#39;s choice is never persisted.</p>
+<h3>Image space vs. georeferenced</h3>
+<p><code>map_type: &quot;iiif&quot;</code> is a mercator map by default. With <code>map_as_image: true</code> the
+image <em>is</em> the map: the view projection becomes <code>EPSG:4326</code>, the view is
+fitted to the image extent and marker locations are pixel offsets into the
+image rather than lat/lon. Ask <code>storymap.isImageSpace()</code> instead of testing
+<code>map_type</code> — georeferenced IIIF (a manifest with <code>navPlace</code> regions) is an
+ordinary mercator map, and <code>map_bbox</code> with a georeferenced layer is one too.</p>
+<h3>Knowing when the imagery is there</h3>
+<p>Tile and image sources attach asynchronously, so <code>loaded</code> can fire before the
+imagery exists. Listen for <code>imageready</code>, which fires once a source is ready and
+carries <code>{ source, kind, layer }</code> (<code>kind</code> is <code>&quot;iiif&quot;</code>, <code>&quot;zoomify&quot;</code> or
+<code>&quot;tiles&quot;</code>); it is re-fired on the <code>storymap</code> as well:</p>
+<pre><code class="language-js">storymap.on(&quot;imageready&quot;, ({ kind, source }) =&gt; {
+    console.log(&quot;imagery ready&quot;, kind, source);
+});
+</code></pre>
+<h3>Tearing a storymap down</h3>
+<p>Call <code>storymap.dispose()</code> when the embedding view goes away (SPA route change,
+dialog close). It clears the timers and the resize observer, removes the
+<code>window</code>/<code>document</code> listeners, cancels running slide animations, disposes the
+slider and the OpenLayers map, and sets <code>storymap.map</code> to <code>null</code>. Calling it
+twice is safe; the instance is unusable afterwards.</p>
+<h2>Custom map providers</h2>
+<p>Any slippy-map tile URL works as <code>map_type</code> — pass the template verbatim
+(including <code>{z}/{x}/{y}</code>), relative or absolute:</p>
+<pre><code class="language-js">new StoryMap(&quot;embed&quot;, data, {
+    map_type: &quot;https://tiles.example.org/base/{z}/{x}/{y}.png&quot;,
+});
+</code></pre>
+<p>Mapbox style JSON URLs render as vector tile layers; OpenLayers
+<code>Map</code>/<code>View</code> pass-through stays available via <code>options.map_options</code>
+(<code>controls</code> replaces the defaults, <code>interactions</code> are added to the
+viewer&#39;s own pan/zoom set, <code>view</code> merges over the computed default).</p>
+<p>For source classes the templates cannot express (WMS, authenticated or
+gridded sources), use the <code>tile_source_factory</code> option. It is consulted
+for every base, overlay and minimap layer before the built-in
+<code>map_type</code> handling — return any <code>ol/layer/Layer</code> (used as-is) or a bare
+<code>Source</code> (which is wrapped in a <code>TileLayer</code>), or <code>null</code>/<code>undefined</code> to fall
+through:</p>
+<pre><code class="language-js">import TileLayer from &quot;ol/layer/Tile&quot;;
+import TileWMS from &quot;ol/source/TileWMS&quot;;
+
+new StoryMap(&quot;embed&quot;, data, {
+    map_type: &quot;wms:flood&quot;,
+    tile_source_factory: (map_type, { options, createDefault }) =&gt;
+        map_type.startsWith(&quot;wms:&quot;)
+            ? new TileLayer({
+                  source: new TileWMS({
+                      url: &quot;https://geoserver.example.org/wms&quot;,
+                      params: { LAYERS: map_type.slice(4) },
+                      crossOrigin: &quot;anonymous&quot;,
+                  }),
+              })
+            : createDefault(),
+});
+</code></pre>
+<p>The second factory argument also carries the resolved <code>options</code>
+(<code>{ options, createDefault }</code>). A factory may return any <code>ol/layer/Layer</code>
+(used as-is — including sourceless layers such as Allmaps&#39;
+<code>WarpedMapLayer</code>), a bare <code>Source</code> (wrapped in a <code>TileLayer</code>), or
+<code>null</code>/<code>undefined</code> to fall through to the default <code>map_type</code> handling.</p>
+<p>Custom sources must carry their own attributions (via the returned
+source or the <code>attribution</code> option) — only the built-in <code>osm*</code> types
+are credited automatically. <code>tile_source_factory</code> is constructor- and
+runtime-only (functions cannot ride storymap JSON) and also applies to
+<code>overlays[]</code> entries, whose <code>map_type</code> values go through the same
+factory.</p>
 <h2>Data and tooling</h2>
 <ul>
 <li>Storymap JSON is now validated against a JSON Schema
 (<code>schema/storymap.schema.json</code>); invalid documents are reported to the
 console at load time.</li>
-<li>IIIF Presentation 3 manifests are accepted directly as storymap sources.</li>
-<li>The StoryMap IIIF extension context changed to
-<code>https://christianmahnke.de/iiif/storymap</code> — manifests produced with the old
-<code>https://example.org/ns/storymap/v1</code> context need re-converting
-(<code>scripts/convert-to-iiif.mjs</code>).</li>
+<li>IIIF Presentation 3 manifests are accepted directly as storymap sources.
+The map settings map onto <code>storymap:</code> terms of a map configuration service
+(IIIF has no basemap or tile-layer vocabulary of its own), and the
+geospatial parts use the native extensions where they exist: <code>navPlace</code>
+Points for slide locations, a <code>navPlace</code> Polygon for the story extent
+(<code>map_bbox</code>), an IIIF Image API Selector for <code>location.region</code>, and the
+Georeference Extension for placed rasters. A georeferenced layer is
+manifest-only (the legacy format cannot express ground control points); see
+<a href="./iiif.html#geo-referenced-layers">docs/storymap-as-iiif-manifest.md</a>.</li>
 <li>The editor, staging/backend infrastructure, AWS/GitHub hosting scripts and the
 Python authoring server are gone — this is a viewer-only library.</li>
+<li><strong>Slideshow tours</strong> are a third input format: W3C <code>AnnotationCollection</code>
+documents (the format of slideshow-style guided image tours) load
+directly by object, file or URL, auto-detected after the IIIF branch
+(<code>slideshow: false</code> opts out). A pure translator converts them to
+storymap data — per-slide image regions, rotation, filter grading,
+spotlight masks, per-slide basemaps, narration with playback flags and
+player chrome — which renders only for slideshow tours (the internal
+<code>slideshow_source</code> marker; other documents are unaffected). Convert
+offline with <code>npm run convert:slideshow</code>; the full mapping is in
+<a href="slideshow.md">docs/slideshow.md</a>.</li>
 </ul>
-<h2>Events (unchanged)</h2>
-<p><code>change</code> (with <code>current_slide</code>), <code>loaded</code>, <code>title</code>, <code>dataloaded</code>,
-<code>fontLoaded</code>, plus the listener map in the constructor — all work as before.</p>
+<h2>Events (unchanged, plus new ones)</h2>
+<p>The canonical reference is <a href="./events.html">docs/events.md</a> — one table per
+emitter, with payloads. What changed in migration terms: <code>change</code> gains
+<code>current_id</code>, <code>loaded</code>, <code>title</code>, <code>dataloaded</code>, <code>fontLoaded</code>,
+<code>transitionstart</code>/<code>transitionend</code>, <code>error</code> and the constructor listener map
+all work as before; <code>markerAdded</code>/<code>markerRemoved</code> still fire on the map
+object; <code>imageready</code>, <code>markerclick</code> and <code>popupopen</code>/<code>popupclose</code> are new
+(see above).</p>
+<p>Two additions for IIIF tours: <code>await storymap.loadAnnotations()</code> fetches a
+manifest&#39;s externally referenced annotation pages and appends them as stops,
+then fires <code>annotationsloaded</code> with <code>{ stops, searchService, failed }</code>. A
+slide&#39;s stable identity is available as <code>storymap.getSlideId(index)</code>, which
+is what the <code>#slide-N</code> hash and the <code>iiif-content</code> deep link resolve
+through.</p>
 
         </main>