I noticed that the new StoryMaps code is not hosted on Esri's Github site. It appears that only the 'classic' StoryMaps are hosted on Github. I would like to request Esri consider please continuing to support open source initiatives by hosting all web application code on Github. Our organization uses Portal but does prefer to host web applications on an isolated web server or via S3/CloudFront. We are not able to do this with the new StoryMaps. Furthermore there are style and branding changes that we would prefer to make with the original CSS and HTML rather than via the StoryMaps configuration. Thank you for your consideration.
@wetlandsuser -- All bug reports should be submitted to Esri Support.
I have a bug report for image handling for the arcgis python storymap code, but am unsure where to file it?
It specifically is about the code failing to check dimensions for JPEG images where the image contains EXIF data in frames preceding the JPEG data itself in the image file.
There's an exciting new way to embed stories in your own web pages. This method of embedding works via a <script> tag (as opposed to a simple <iframe>) and provides advanced capabilities to customize a story's style, content, and behavior via code.
For more information, see What's new in ArcGIS StoryMaps (February 2025).
@BlairDeaver3 - While this capability is currently only available for StoryMaps on ArcGIS Online, it's possible we could bring this to ArcGIS Enterprise in the future. Are you able to test out this new feature and let us know if it would meet your needs?
Update: Kaycee and I have exchanged messages about the examples mentioned above.
@OwenGeo - Thanks Owen. IT has worked with us previously to use iframes with these products, but as a federal agency our security policies are continually evolving and can be fairly strict. Regarding specific branding requirements, is there an e-mail where I send details?
@BlairDeaver3 / @LefterisKoumis -- We are considering several of the options mentioned on this thread, but each one comes with a long list of pros and cons as well as different amounts of additional development/maintenance effort and resources that we need to weigh in terms of the additional value they offer.
We are still in the research phase and appreciate the use cases and information you are providing since they are extremely helpful in helping us understand the community's requirements.
@LefterisKoumis -- Sounds like you do not need to make any customizations and work in an organization that manages its own IT/infrastructure resources. If your only need is to host the ArcGIS StoryMaps app on your own infrastructure, ArcGIS Enterprise is available for that use case. ArcGIS StoryMaps is included in Enterprise 10.8.1 and later.
Owen thank you for providing the link "Customizing your StoryMap’s URL (esri.com)" but the main reason for the idea is to host out custom StoryMap app on our servers. Why not providing a developer's version like the WAB or ExB?
@OwenGeo- Awesome feedback. Thank you. I would like to also reiterate the benefit of being able to isolate the StoryMap deployment files on a server or CDN outside of Enterprise/Portal instance from a maintenance, DevOps, and scalability perspective. Are there any plans for the option to download a compiled and minified version? This would be fantastic.
@KayceeFaunce -- Thank you for the additional information! That is very helpful.
We are planning to add more flexibility into the theme and story builders over time. Do you have a link where we could see a header and footer used by your organization? That would help us understand the types of customization options and layouts that we might provide.
I understand your organization's concern about the security of iframes. If it's helpful, there are many ways to more safely allow iframed content rather than simply disallowing them.
iframes have a "sandbox" attribute that provides a low-permissions environment that blocks potentially malicious activities. Specific pieces of functionality can be unlocked on an as-needed basis. ArcGIS StoryMaps uses the sandbox attribute on all iframes. There are also content security policies (CSPs) that can be used to allow only embedded content from trusted sites. A CSP could be used to allow only content from storymaps.arcgis.com, for example.
There are a lot of great resources on the web about iframe security. Here's an article that I found generally helpful: Play safely in sandboxed IFrames - HTML5 Rocks
@OwenGeo - Hi Owen, my organization requires very specific branded headers and footers on all products (specific pixel dimensions of header, footer, and logo; specific logo placement; specific links in footer) that cannot be adequately re-created using the theme builder. In the past, we have used iframes to insert StoryMaps between our header/footer templates, which also allows us to display the product on our own domain. However, iframes are viewed as a security vulnerability and our organization is encouraging us to move away from their use. In our specific use case, we either need code that we can deploy on our own server with the required customizations (like we can do with the classic templates) or much more flexibility in the builder itself in terms of the customizations we can make.
@KayceeFaunce -- Thanks for your note about this idea. Could you please provide more information about the customizations you require that are not currently supported in the theme builder or story builder?
Also, can you provide more information about the disapproval of iframes so we can better understand that restriction?
I vote for this too. Because of my organization's strict visualization identity standards that we are unable to meet using the lack of customization ability in the new builder and the disapproval of iframes, we are being encouraged to seek alternatives to Esri StoryMaps unless the code is made open source.
I vote for it too!
Thank you @OwenGeo for your suggestions. I would still like to find a way to separate and isolate the web application files from the server. This would involve hosting the files on a separate web server or CDN from the GIS Server. This was an option before.
For those of you who voted or commented on this idea that are interested in hosting code solely for the purpose of customizing the URL of a story, please see this article that provides some suggestions related to this request: Customizing your StoryMap’s URL (esri.com)
I vote for this as well
I vote for this too
This would be helpful to my organization as well...
This would be very helpful.
Yep, me too. I'm in the situation where I want to use some features of the deprecated classic story maps that aren't present in the current version and can't wait until Esri gets around to implementing it (which might be never).
Interested in this as well. In addition to the above use cases, we would look to a solution like this to provide an avenue for hosting StoryMaps using our own domain names, rather than only at https://storymaps.arcgis.com.
I vote for this too.
I second that request. It is very important for our organization to have the option to use the portal or just rest services to create the storymap.
Connectez-vous pour publier, suivre le contenu, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
