I think the issue is jus that we need to tell the client what fiels to download, even though they can then be selected dynamically during the experiment.
There are two ways the list of resources can be generated:
- A. if you use the html folder inside the project (as default) then there will be a resources folder inside that and you can drag a copy of the files into there manually. Builder will do it’s best to populate that folder based on what it finds in conditions files and parameter settings of components, but it can’t detect the contents of code components
- B. the newer option is that we don’t use the html folder, just the root of the project for the javascript/html files. In theory this is better because we don’t need to duplicate files but we still need to provide a list of resources to the client that it should fetch at the beginning of the study. The way to make manual additions to that list isn’t yet exposed in the Builder interface and needs coding in the JS manually. But hopefully you’re using option A!
