# Tech Behind the Scenes

<figure><img src="/files/U6IyvZL62LieS02aKOjp" alt=""><figcaption></figcaption></figure>

Because theatre makers were forced into fully remote work in 2020, their perspective on integrating digital technology into their production process has shifted. I documented this shift in the performance space itself, but there has been an equally dramatic shift in behind-the-scenes methods. Digital tools are not new to theatre makers - obviously email, text messages and SMS services, document writing programs, spreadsheets, slideshows, CAD programs, QLab and other tech cueing integrations, file sharing systems, digital photography, and video and image editing software have all been integrated into the theatre creation toolkit. It would be a rare production even before the pandemic to be fully analogue. However, post-pandemic, there are even more tools available, triggering changes to the entire theatre making pipeline from auditions to final performance. This Spotlight documents what I have found about these changes so far.

<figure><img src="/files/VR6mP342auEczBkfdDty" alt=""><figcaption><p><em>Figure 32: Screen grab of Streamed Shakespeare's</em> Henry IV <em>production folder on Google Drive, which Holly Champion allowed me to access as part of my archival research into this livestreamed performance. The folder contains several test images demonstrating how Chromakey setups could work for various characters. The Chromakey tests, the testing process itself, and the online documentation itself demonstrate a few ways that technology is integrated into second wave digital theatre behind the scenes.</em> </p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://secondwavedigitaltheatre.gitbook.io/flinders-phd-research-project/spotlights/tech-behind-the-scenes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
