WebArch101 draft

[rvedotrc]

This module is intended primarily to take the form of a presentation.

• The goals of this module: https://github.com/HackYourFuture-CPH/programme/blob/webarch101/courses/Foundation/web-architecture-101/goals.md
• The slides (Keynote): https://github.com/HackYourFuture-CPH/programme/blob/webarch101/courses/Foundation/web-architecture-101/HYF%20Web%20Architecture%20101.key
• The slides (exported as PDF): https://github.com/HackYourFuture-CPH/programme/blob/webarch101/courses/Foundation/web-architecture-101/HYF%20Web%20Architecture%20101.pdf
• A conversion of the presentation into markdown: https://github.com/HackYourFuture-CPH/programme/blob/webarch101/courses/Foundation/web-architecture-101/presentation/README.md

Anything that says TODO in the markdown is of course a work in progress.

[adamblanchard]

I can see why you like to smash ideas together with slides :D Really nice flow with the story and building the concepts.

I reviewed it also from the point of covering all the "existing" material proposed to be included in web arch 101 (client vs server, what is backend? (and frontend), client-server model, json, api, http).

JSON was the only thing i didn't see covered explicitly. Was that on purpose or how should we include that?

I think this is ready to be structured into some markdown for a proper review, if you're up for it.

[marcorichetta]

I read the PDF and the .md notes and it makes sense to me!

• This session should/could be entirely a presentation? In the sense that trainees will not be required to do anything in their computers. Obviously there's freedom to use examples or add interactivity to the presentation

[marcorichetta]

Regarding the DNS, connections and content-type sections, is there more content to add?
I mean, in the pdf there were more comments but maybe it was just exploratory

[rvedotrc]

I think it's very much up to whoever is leading the session. The "Goals" page covers the defined scope of this module, and the "Recap" page covers the important bits. My intention is that the material here provides a narrative structure to walk through, which will ensure that the trainees see how the key technical modules fit together; but also that there is hopefully wiggle room in this module for exploration deeper (DNS? TCP?) or sideways (UDP? HTTP cacheing? Security?) as seems appropriate based on time / questions.

[marcorichetta]

I like these key points sections, really useful!

[rvedotrc]

I read the PDF and the .md notes and it makes sense to me!

* This session should/could be entirely a presentation? In the sense that trainees will not be required to do anything in their computers. Obviously there's freedom to use examples or add interactivity to the presentation

Exactly. That is how I first assembled my ideas, as a presentation, and if I were leading the session, that's what I'd do.

I'll try to thread a few exercises in there too, but the primary point of this is exactly as you said: watch / listen / read, get an overall understanding. Not really much to do on their computers.

[rvedotrc]

JSON was the only thing i didn't see covered explicitly. Was that on purpose or how should we include that?

That'll go (brief mention / illustration) in the Data & APIs section.

[marcorichetta]

I think you accidentally pushed some presentation assets.
Aside from that, LGTM 💯