Content Deployment/ Access Options

📘 Background

This brief background is here to provide some grounding on what NimbleStory is for those arriving to this page to understand how NimbleStory content can be deployed for use into other sites/ apps and evaluating risks. If more information is required, just reach out and we can discuss options in more detail.

NimbleStory is a visual-first, mission delivery platform that is used in several different ways but there are 3 primary use-cases:

• Collaboration around visual content - Users Login directly to NimbleStory to collaborate on visual content and refine it until it is ready for delivery/ deployment.

  • The resulting basic content can be viewed directly, embedded, or exported for deployment elsewhere, but access controls and collaboration features would not be available in external deployments.

• Curation of Interactive Solutions - NimbleStory Curators assemble unique Interactive Solutions by connecting various visual elements together into Journeys, Smart Diagrams, Geographic Maps, Gameboards, Playbooks or fully combined Concept Explorers.

  • The resulting interactive content can be viewed directly, embedded, or exported for deployment elsewhere, but access controls and usage tracking features would not be available in external deployments.

• Direct Content Deployment and Tracking - Users connect to NimbleStory to view/ interact with specific Curated Interactive Solutions and connected visuals while their progress is tracked by either team/project membership or invdividually so reporting can be assembled on content reach/ imapact.

  • The resulting reporting data can be viewed directly or exported for use elsewhere.

Content created in NimbleStory can be deployed ON NimbleStory or in external systems, depending on the needs of the customer.

📘 Content Access Sharing & Delivery Options Summary

Once the content has been properly created/ refined/ curated and is ready for users to interact with on a broader scale, there are several options for deploying that content to constituent audiences. This table summarizes and compares the available options for deploying NimbleStory content. Additional details are in the expanded sections below.

📘 Key Feature and Usage Differences

📘 Self Hosting Options - Exported to NimbleStory Companion Player

• Most NimbleStory interactive solutions can be exported for use by our Companion Player. At this time, that companion app is only available for SharePoint as an SPFX Web Part but other platforms are on the Roadmap.

  • This self hosted option offers a good balance between control and features, but does involve installing a NimbleStory component into your environment (ex. a web part for SharePoint) that knows how to render NimbleStory interactives.

  • Once this component is installed and setup, it can be used multiple times to render different NimbleStory interactive solutions. Advanced use-cases can also include locally edited content (ex. Storing content in SharePoint Lists for local editing and exposure through the interactive vs going back to Nimblestory and re-exporting changes there).

    Access limits and usage tracking would need to be managed in the local environment since the NimbleStory SAAS platform would not be connected or called in any way.

• Companions

  • SharePoint Web Part (Available Now - by request)

  • Teams App (In Development)

  • Miro Add In (On Wish List)

  • Confluence Add In (On Wish List)

• Setup Steps

  • Download the Companion (contact NimbleStory support for the right link)

  • Import the Companion into your (SharePoint for now) environment and ensure it is usable on the site/ pages that will hold the content

  • In NimbleStory company. nimblestory.com locate the solution, ensure it is fully curated/ ready for deployment and use the export option to get the exported content/ structures.

  • In your site (SharePoint for now), add the expanded Export content (visuals, documents, and a manifest) to the correct File Area (Document Library) and then add the companion app (Web Part) to the page that you want to add the content to and configure it to use the export content you just loaded. Configure the size/ content open options to suit your needs.

• Content Updates

  • Structural content updates would require re-export from NimbleStory.

  • Some limited LOCAL content updates are possible for specificly configured solutions, including:

    • Local Content Links (https links to local things should always be available)

    • Special JSON Datasets (geographic and smart diagram interactives support this)

    • SharePoint Lists (journeys support this)

    • Contact support if you have a specific requirement in mind

• One-time Install Dependencies

  • The companion app is a react app wrapped for the platform and would have npm depencies on intial setup/ install.

• Runtime Dependencies

  • NO Internet Dependencies

  • NO External Tracking/ Metrics

📘 Self Hosting Options - Exported HTML 5 Zip/ Bundles

• This self hosted option is flexible and usable in just about any web platform that can support a static folder of HTML/CSS/JavaScript/Images.

• We have seen this deployment method used on a variety of platforms, including SharePoint, WordPress, AWS S3, CloudFlare Pages, and of course plain web hosts (IIS/Apache/Tomcat/nginx/etc.).

• Access limits and usage tracking would need to be managed in the local environment since the NimbleStory SAAS platform would not be connected or called in any way.

• Content Updates

  • Structural content updates would require re-export from NimbleStory.

  • Some limited LOCAL content updates are possible for specificly configured solutions, including:

    • Local Content Links (https links to local things should always be available)

    • Special JSON Datasets (geographic and smart diagram interactives support this)

    • Contact support if you have a specific requirement in mind

• Dependencies:

  • This is Static HTML 5 Content that consists of HTML, Client-Side JavaScript, CSS, Images, and some JSON files that are used to direct how the app loads

  • NO Internet Dependencies

  • NO ServerSide Dependencies (no asp/php/jsp/cfm/etc, no databases, serverless)

  • NO Tracking/ Metrics

  • NO Software Installs at all