Options for managing UIO are being documented here:

https://wiki.fluidproject.org/display/fluid/Managing+UIO+in+a+project

I chatted with Justin and we decided on the following approach:

• We will automate the updating/preparing of UIO for the Cities site using NPM and Grunt

  • We'll add a package.json and Gruntfile.js

• We will store the UIO build for the Cities site (the output of the automated process) in the website-cities repo

• NPM and Grunt need only be run when updating UIO – for regular site builds, Hugo is used only

• The Gruntfile.js will copy files from the UIO distribution in Infusion to the Hugo static directory, replacing the files there (see https://unpkg.com/infusion@3.0.0-dev.20181204T213346Z.2ca90f6e6/dist/)

Document this process:

• In the README.md for website-cities

• And update https://docs.fluidproject.org/infusion/development/tutorial-userInterfaceOptions/UserInterfaceOptions.html with notes on this approach

@Simon Bates I'm trying to remember if the src directory always included all of the original source or not. I don't think it did, but not sure when this may have changed. We did make some changes recently to pull in third party dependencies from NPM, and had to make some adjustments to the build scripts then. So it may have occurred with those changes. However, we did always need to do some pruning of the source directory as it always included JS files that were already bundled up in the concatenated JS file. We typically include all this information in a VERSION.md file accompanying the infusion src. 

Lately we've just been pulling in Infusion from NPM directly. The NPM package comes with a distribution for a UIO custom build (see: https://unpkg.com/infusion@3.0.0-dev.20181204T213346Z.2ca90f6e6/dist/ for examples). You'll also need to setup some copying of the necessary templates, message bundles and etc. It's a bit of work to setup initially but once it's all done it makes updating and keeping track of the version much easier. Let me know if you'd like to do this and would need some help getting things set up.

I'll check with Justin in January and hopefully it'll be a fairly quick process to verify and update.

At this point, I don't know what process was used to prepare the Infusion that is currently in website-cities.

I have tried:

And that produces an 'infusion-custom.js' of approximately the same size as the one in the website-cities repo. However, the 'infusion-custom.js.map' is a different size and the 'src' directory contains much more stuff than the one in website-cities.