Stories
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
A story is a sequence of chapters. Each chapter has a title, Markdown text, images, galleries, carousels, embeds, videos, buttons and separators, and can have a scene: a saved map, a camera position and the layers to show. A reader scrolls through the chapters and the map beside them changes to match.
Read a story
Section titled “Read a story”A story opens at /stories/<id>. Anyone who can read it can open it, signed in
or not. The Maps page has a Stories tab next to Maps that lists the
stories you can read.
- On a wide screen the chapters scroll beside a fixed map. The chapter in view sets the scene. A story can instead put the chapter text in a floating panel over a full-bleed map; see Reader settings.
- On a phone the chapters become a stepper with Previous and Next buttons. The arrow keys also step through them.
- Each chapter change is announced to screen readers. With reduced motion on, the camera jumps instead of flying.
- A story can show a navigation bar above the chapters with its title and a list of them. Select a chapter in the list to jump to it. On a narrow screen the list collapses.
- When a chapter’s scene differs from the map’s current view, the map moves there as the chapter comes into view. The author picks how: Fly, Glide or Cut (see Scenes). Fly and Glide last longer for a longer move. Layers a scene turns on or off fade in and out.
- A chapter on a different map loads that map ahead of time and crossfades to it.
- If you pan or zoom away from the chapter’s view, Back to this chapter’s view appears on the map. Select it to return.
- A gallery image opens full size in a dialog with its caption and Previous and Next buttons. A carousel shows one image at a time with dots for the others.
- The Map data button opens the table of the scene’s map under the map, as it does on the map page. The map’s Readers can open the attribute table setting decides whether it is offered; see Map data. In the floating layout the chapter panel ends above the open Map data panel.
- A chapter whose map you can’t open shows its text with a notice. A story in which no chapter has a scene reads as text, with no map pane.
- The map’s attribution stays folded on a phone until you press its button.
The owner and admins see an Edit button.
Create and edit a story
Section titled “Create and edit a story”On the Stories tab, select New story, give it a title and select Create and edit. A new story is a private draft that only you and admins can see. Creating one needs the same permission as editing dataset metadata.
The editor lives at /stories/<id>/edit.
Chapters and text
Section titled “Chapters and text”Select Add chapter, then give the chapter a title and write its content. The editor has a Write and a Preview tab, and a toolbar for bold, italic, headings, links, and bulleted and numbered lists.
A chapter holds text blocks, images, galleries, carousels, embeds, videos, buttons and separators. Add text block, Add image, Add gallery, Add carousel, Add embed, Add video, Add button and Add separator add them, and each block has buttons to move it up or down. Use the move buttons in the chapter list to reorder chapters. A story can hold up to 200 chapters, a chapter up to 100 blocks, and a draft up to 2 MB.
A button is a link that looks like a button. Give it a Button label and a
Link address that starts with http:// or https://; the draft doesn’t
save until every button has both. A separator is a Line or a Gap
between blocks.
A gallery and a carousel hold up to 12 images each. Add another image adds one, and every image takes alt text, or Decorative image, and an optional caption, as a single image does. A gallery shows its images together; a carousel shows one at a time.
An embed shows another web page in a frame and a video shows a video player.
Give each a Title, which screen readers announce, and a Page address or
Video player address that starts with https:// on a site an administrator
has approved. The field lists the approved sites. Until an administrator
approves sites, the two blocks are off, and a draft doesn’t save while one is
incomplete. An administrator approves the sites under Story embeds and
videos in Admin settings, on the Network tab. If a site is removed
later, readers see a notice in place of its frame.
Scenes
Section titled “Scenes”Open a chapter’s Map scene to pick a saved map. Pan and zoom the map in the editor and select Use current view to keep that camera for the chapter. Layers shown turns the map’s layers on and off for this chapter only. Remove scene gives the chapter text only.
Transition sets how the map moves to this chapter’s view: Story default, Fly, Glide or Cut. A Cut jumps. With reduced motion on, every transition is a cut.
Edit map in Builder opens the scene’s map in a new tab. Layers you add there appear in the story when you come back to the editor.
Reader settings
Section titled “Reader settings”Reader settings in the editor’s toolbar sets how readers see the whole story. The settings join the draft and reach readers when you publish.
- Navigation bar shows the story title and a list of chapters above the story.
- Layout is Side panel, which scrolls the chapters beside the map, or Floating panel, which puts the chapter text over a full-screen map. On a phone the map sits above the text either way.
- Panel position places a floating panel Left, Right or Centre. A centred panel covers the middle of the map, where each chapter’s view points, though readers can still move the map around it.
- Reader theme is Follow the reader, Light or Dark. Follow the reader uses the reader’s own light or dark setting.
- Transition is the default for chapters that don’t set their own.
Saving
Section titled “Saving”The editor saves the draft by itself, two seconds after the last edit and when you hide the tab. There is no Save button. The status line says whether the draft is saving, saved, or has changes readers don’t see yet. If a save fails, select Retry.
Readers see only the published version. Select Publish to replace it with the draft, and Discard draft to go back to the published version.
If someone saved the draft somewhere else after you opened it, the editor says so. Load latest takes their version and drops yours. Overwrite with my version keeps yours.
Publishing is refused when a map the story uses can’t be read by everyone the story’s visibility reaches. The message names the maps you can read and counts the rest. Widen those maps’ visibility or narrow the story.
Images
Section titled “Images”Add image uploads a PNG, JPEG or WebP file of up to 50 MB. The server re-encodes it as WebP, at most 2,400 pixels on a side, without its metadata. It also keeps a 640 pixel wide card size and a 1200 by 630 JPEG for link previews.
Each image needs alt text, or it must be marked Decorative image. Saving waits until every image has one or the other. A caption is optional.
A story holds up to 200 images and 250 MB of them. An admin can also cap the image storage each user’s stories hold; see Settings. Over a limit the upload is refused. Duplicating a story copies its images.
An image that no draft or published version uses is removed after 7 days, long enough to undo a removal. A background job also deletes stored image objects that no story names, once they are a day old.
Cover image
Section titled “Cover image”Open Details and use Cover image. The cover shows on the story’s card, above its first chapter and in its link preview. It changes when you save the details.
Details, visibility and groups
Section titled “Details, visibility and groups”Details holds the title, a summary, Who can read it, Groups and the cover. Select Save details to apply them; they take effect without publishing.
Visibility is Private, Internal or Public. A public story is readable by anyone once it is published. On an instance that limits public content to admins, only an admin can make a story public.
A visibility wider than a map the story uses is refused. Narrowing a story is always allowed.
Link previews
Section titled “Link previews”When a public, published story is shared in a chat or social app, the preview shows its title, summary and cover image. A story with no cover shows the map image of its first readable scene. This needs Public App URL; see Settings. Any other story answers a crawler as if it did not exist.
Share with groups
Section titled “Share with groups”The Groups section shares a story with sharing groups. See Sharing with groups for what happens to a story and to the maps its scenes use.
Embed a story in another site
Section titled “Embed a story in another site”A published public story has an Embed button in the story header. It shows an iframe snippet and Copy embed code. Paste the snippet into a page on your site and the story shows there without the GeoLens header. The frame stops showing the story if it is no longer public.
Duplicate and delete
Section titled “Duplicate and delete”On the Stories tab, Duplicate copies a story, images included, as a private draft. Delete removes it for good and leaves its maps alone.
The delete dialog for a map lists the stories that use it.
See also
Section titled “See also”- Sharing with groups: story groups and the maps they need
- Map builder: create the maps a story uses
- Dashboards: widgets beside a map