A few small improvements to StoryMapJS

Based on research and user testing, we're making a number of small changes to StoryMapJS. We think they make the tool easier to use, but we wanted to explain the changes for any veteran users who might notice them.

Thumbnail preview

First, we made a simple change to the media section: you'll now see a thumbnail preview of whatever media you've attached to the slide. This should make it easier for people to know what they are looking at as they move between slides editing a StoryMap.

We've added a thumbnail preview to the "media" section of the StoryMap slide editor.

More prominent position for social sharing

Many people are not aware that you can configure your StoryMap for better results when sharing on social media. You can set the title, image and description which appear when you share a link on Facebook, Twitter, Slack, and other services. These configuration options used to be on a tab under the "options" menu, where they were often overlooked. We've moved them to the "sharing" pane so that people will see them when they're relevant. As a temporary measure, we still have a "sharing" tab in the original location, but it just explains this change for people who don't read this post.

Now when you "share" a StoryMap, the social media details are easier to find and update.

Set Gigapixel option later


Also, we've learned that many people don't understand the "gigapixel" variant of StoryMap, even though we ask if you want to make one each time a new StoryMap is created. Since it's a relatively rarely chosen option, we removed the choice when creating a StoryMap, although of course you can still make them. We now assume that when you click "new," you're making a conventional StoryMap, but if you do want to make a gigapixel StoryMap, you can choose that by going to the "options" menu and choosing it from the "map type" menu. As always, making a gigapixel storymap requires the ability to process your base image and host the image tiles on a web server, so if this part sounds foreign to you, you can safely ignore it.

Eliminate the "draft" feature?


Finally, a change we expect to make soon, but haven't yet. From the beginning, the StoryMap authoring tool has had a concept of "draft" and "published" StoryMaps. We imagined a situation where someone published a StoryMap, then found that it needed changing. Because StoryMap saves frequently while you're working, someone might come look at your published StoryMap while you were in the middle of making edits. However, we realize that the existence of the "draft" and "published" versions is not clear to many people — we have seen published StoryMap URLs which end in draft.html, which undercuts the entire feature. Since StoryMapJS only saves when you move from field to field, the real risk of someone seeing partial work while you're editing it is not too high, so we're thinking about eliminating the "draft" version for new StoryMaps. We think this will fit better with the mental model most people have when they're working on a StoryMap, simplify the code, and reduce a lot of possible confusion. If you have strong opinions about this either way, let us know!

About the author

Joe Germuska

Chief Nerd

Joe runs Knight Lab’s technology, professional staff and student fellows. Before joining us, Joe was on the Chicago Tribune News Apps team. Also, he hosts a weekly radio show on WNUR-FM – Conference of the Birds.

Latest Posts

  • With the 25th CAR Conference upon us, let’s recall the first oneWhen the Web was young, data journalism pioneers gathered in Raleigh

    For a few days in October 1993, if you were interested in journalism and technology, Raleigh, North Carolina was the place you had to be. The first Computer-Assisted Reporting Conference offered by Investigative Reporters & Editors brought more than 400 journalists to Raleigh for 3½ days of panels, demos and hands-on lessons in how to use computers to find stories in data. That seminal event will be commemorated this week at the 25th CAR Conference, which...

    Continue Reading

  • Prototyping Augmented Reality

    Something that really frustrates me is that, while I’m excited about the potential AR has for storytelling, I don’t feel like I have really great AR experiences that I can point people to. We know that AR is great for taking a selfie with a Pikachu and it’s pretty good at measuring spaces (as long as your room is really well lit and your phone is fully charged) but beyond that, we’re really still figuring...

    Continue Reading

  • Capturing the Soundfield: Recording Ambisonics for VR

    When building experiences in virtual reality we’re confronted with the challenge of mimicking how sounds hit us in the real world from all directions. One useful tool for us to attempt this mimicry is called a soundfield microphone. We tested one of these microphones to explore how audio plays into building immersive experiences for virtual reality. Approaching ambisonics with the soundfield microphone has become popular in development for VR particularly for 360 videos. With it,...

    Continue Reading

  • Prototyping Spatial Audio for Movement Art

    One of Oscillations’ technical goals for this quarter’s Knight Lab Studio class was an exploration of spatial audio. Spatial audio is sound that exists in three dimensions. It is a perfect complement to 360 video, because sound sources can be localized to certain parts of the video. Oscillations is especially interested in using spatial audio to enhance the neuroscientific principles of audiovisual synchrony that they aim to emphasize in their productions. Existing work in spatial......

    Continue Reading

  • Oscillations Audience Engagement Research Findings

    During the Winter 2018 quarter, the Oscillations Knight Lab team was tasked in exploring the question: what constitutes an engaging live movement arts performance for audiences? Oscillations’ Chief Technology Officer, Ilya Fomin, told the team at quarter’s start that the startup aims to create performing arts experiences that are “better than reality.” In response, our team spent the quarter seeking to understand what is reality with qualitative research. Three members of the team interviewed more......

    Continue Reading

  • How to translate live-spoken human words into computer “truth”

    Our Knight Lab team spent three months in Winter 2018 exploring how to combine various technologies to capture, interpret, and fact check live broadcasts from television news stations, using Amazon’s Alexa personal assistant device as a low-friction way to initiate the process. The ultimate goal was to build an Alexa skill that could be its own form of live, automated fact-checking: cross-referencing a statement from a politician or otherwise newsworthy figure against previously fact-checked statements......

    Continue Reading

Storytelling Tools

We build easy-to-use tools that can help you tell better stories.

View More