Hide parts of Storymap for later publication

[AnninaOberrenner]

I am creating a storymap template, that should present the results of an ongoing project. It would be very helpful if i could take my whole template (that shows the project from start to finish) and then pick parts that i want to hide from the viewer when the story is published. Like this i wouldn't have to create all the parts again. And since there is also no possibility to copy slide shows or tables, i really need to do it all again.

[OwenGeo]

@AnninaOberrenner -- You can duplicate StoryMaps, which might help in this case. You could create a story or template with all the parts you need and then duplicate it and remove pieces that are not needed in each case.

We are also working on a way to reuse content across StoryMaps that we hope to start rolling out sometime next year.

[DataOfficer]

I agree a way to have certain aspects in 'drafts' would be fantastic.

[SehmiloSheriff]

Hi @AnninaOberrenner, you can create the entire StoryMap from start to finish, duplicate it, and then remove any details you don't want the viewer to see in the duplicate copy. Every piece of content from the StoryMap will be present in your new duplicate copy, without having to start afresh. You will find the duplicate copy button when you click the three dots next to the account button (top right). After clicking 'Duplicate', it will save it as a copy of (name of story). You can rename it when publishing. I hope this helps.

[AnninaOberrenner]

@OwenGeo @SehmiloSheriff I want to show the results of an ongoing project to my customers, e.g. i want to publish the first third of my storymap now, and the second third in a  month, and so on. Of course i can duplicate a storymap but my problem ist that i then have to redo all of the parts i didn't publish now. Do you know what i mean? 

It would be easier if i had an opportunity to hide parts and then show them again when i am at the next stage of my project. 

[AaronKoelker]

@AnninaOberrenner Reading your specific use-case: a suggestion for an alternative could be to use a StoryMap Collection and have a StoryMap for each part. Whenever you want to share the project around, just use the Collection URL and treat that as the main story item—that way readers will always see the latest parts that have been published without needing to hunt down the link/url to each individual StoryMap you release as the project goes on.

Here's an example NY State Parks did where they published out a new part once a month to a single Collection: https://arcg.is/1v5D8S1