Create separate builds for each wallscreen

[camillevilla]

This would be a nice thing to have for #196

[thatbudakguy]

in an ideal world, would the solution for this create a build that is exclusive to a single wallscreen? I'm not sure we could stop it from including all the media files, but we might be able to get it to only generate the HTML for certain wallscreens. if we do that, is it important that the build/archive be easy to use without extra instructions (e.g. "unzip it, start up a server, make sure you navigate to this URL, some of these links will be broken" vs "just unzip it and start a server")

relatedly, would this also ideally create a build that can be deployed to hohbach as a single archive, so that the webserver running on those windows PCs will serve a single wallscreen's content only? or is that not as important, and the only goal is preservation-focused (#196)?

[camillevilla]

Good questions, @thatbudakguy! I think the latter "unzip it and start a server" is sufficient. Mostly, I'm interested in separate version tracking if curators need to edit or add content later in 2022.

• For now, I think it's fine if the build includes thumbnails, attractor images etc. from the other experiences. In the long run, we might want to move these out of the repo
• 🤔 We could bundle up the files with a web server (e.g. the current version of nginx we're using), but I think it could create more annoying dead files in the long run.

RE: deployment considerations

• It's not important that the PC builds serve a single wallscreen's content right now. The current site build size is 9GB and we'll be adding two more videos. The space on the PCs is limited, but I don't imagine we'll run into space issues until say... a sixth wallscreen? I'd be ok punting on this until we have to deal with additional wallscreens being installed or experiences being decommissioned.
• It might be a question for @ggeisler: if there are plans to switch content between the two physical screens as part of future usability testing, we might want to revisit distinct Google Analytics IDs for each screen.

[ggeisler]

It might be a question for @ggeisler: if there are plans to switch content between the two physical screens as part of future usability testing, we might want to revisit distinct Google Analytics IDs for each screen.

I'm not sure I fully understand the issue, but if it helps, as far as I know there would be no reason to switch content from one screen to the other. I believe the choice of which physical display is assigned the Silicon Valley Archives content versus which is assigned the Diversity content is intentional related to where the displays are in the physical space.

My understanding (although at this point I imagine it's all just a guess) is that over time wallscreen 7 will always display some sort of the SVA content (i.e., that's the primary, permanent theme of the physical area, including the nearby display cases). Over time wallscreen 11 could have different screen titles and feature different experiences but (I think?) the general theme will always be diversity, at least for the foreseeable future.

[camillevilla]

Closing this issue in favor of some refactoring in #276