Chapter 2 contains a lot of technical details that might confuse the less technical people (GUI clickers).
Since the first part of the workshop is aimed towards people who just want to use the UI and don't necessarily know how to code, I would get rid of some of the bits:
I would get rid of eduvpn and rabbitmq, this is only relevant for the person installing the software which is not gonna be the the GUI clickers
Distinction between datanode and database: I think that for the GUI clickers it suffices to see datanode and database as one unit
UI, python client, and API: maybe python client is relevant but API is just an implementation detail that GUI clickers are not going to do anything with
I would remove the part about the distributed policy system: for GUI clickers it is enough to know that theres gonna be a policy system, how these policies are distributed is too much info for a feature that hasn't been implented yet
Remove build services: GUI clickers are not going to use it
I think it is important to simplify and not overwhelm the poor GUI clickers with too much details.
Chapter 2 contains a lot of technical details that might confuse the less technical people (GUI clickers). Since the first part of the workshop is aimed towards people who just want to use the UI and don't necessarily know how to code, I would get rid of some of the bits:
I think it is important to simplify and not overwhelm the poor GUI clickers with too much details.