To minimize setup time, the AiiDA session relied on browser-based teaching: participants connected to a JupyterHub server, where they could log in with their email address and a password of their choice. After logging in, each participant was redirected to a Jupyter notebook server running inside a private docker container where all the necessary software for the tutorial had already been installed (based on the AiiDA lab ). After a brief introduction, the participants used the Jupyter notebook interface to work through the detailed hands-on materials (tutorials.readthedocs.io/en/latest/pages/2020_BIGMAP/index.html), which included instructions on how to run a Quantum ESPRESSO calculation through AiiDA and introduced them to the concept of how AiiDA stores calculation provenance. Besides the presenter, two tutors were available for addressing specific questions in breakout Zoom rooms. The built-in polling feature of Zoom was used to track the progress of participants at defined points during the 2h period, followed by brief recaps of sections of the tutorial material. Despite this being our first trial of the fully browser-based approach, we received highly positive feedback via the form circulated after the event. 100% of responses stated that the browser-based approach worked well, 95% found the hands-on sessions easy to follow, and several comments specifically mentioned a preference for the browser-based approach over downloading a virtual machine image to run locally. From the tutors' perspective, the browser-based approach allowed to basically eliminate setup-related issues entirely, which so far we've not been able to achieve by other means (VirtualBox helps reduce issues substantially but some tend to remain, such as BIOS settings to adjust or participants running out of disk space). Running the JupyterHub on an autoscaling Kubernetes cluster on Amazon web services allowed to keep the size (and thus the cost) of the cluster small during the testing period before the workshop, let it grow dynamically during the workshop, and shrink again to a minimal configuration after the workshop had finished (terraform-based setup instructions are available at ). The JupyterHub was shut down two days after the event, giving all participants ample time to take their data home.