There are a million web tutorials out there. I suggest starting with W3Schools. It's not perfect, but it's pretty good.
The browser is lazy, and it won't reload files it already has it its cache. Files like CSS files and JS files.
As a web designer, we often revise those files and we want to see if our changes worked. So, we want the browser to reload not just the main page content, but the supporting files as well.
For force it to reload everything, hold down the shift key when you reload.
Should we primarily use LABEL with ID?
Sure. Let's look at the reading on labels
I suggest using LABEL by structure, rather than ID.
Think about the difference between reading Instagram and posting to
Instagram. When we read, we GET
stuff from the
server. When we post stuff, we use the POST
method.
Get sends a small amount of data to the server. Basically, just a link:
GET /article/1234
GET youtube.com/watch?v=8939489
Posting sends a lot more data (e.g. image files) to the server, so we have to use a different format and such.
Possibly, but rarely. Of course, GET and POST can be mis-used (I've misused them in the past, but I'm trying to be better.)
LTS misuses POST in the course lists, and it annoys me to no end.
The server (which we will start next week) supports various endpoints (the end of the URL) and methods (GET, POST and a few others). If the server doesn't support a particular combination, the browser will get a 404.
Great question, but for another day. We'll talk more about security later.
I would love to talk more about accessibility, but there are only so many days in the semester. I will sprinkle it in when it's relevant and we have time. I say more about it in CS 204, including a whole reading on accessibility
It does some basic accessibility testing, helping us make web pages that are accessible to all.
I'll demo on this page!
Oh, my apologies. We have a new CS 110, so I archived the old one, and that broke these links. I'll find some alternatives, or resurrect those.
Thanks; I appreciate the editing help.
W3 Schools is a good place to start. For fancier things, I often find myself at CSS tricks. Web searching will find others.
Sure. Don't stress about it. It's useful, both in this class and as a software engineer, but you'll get the hang of it.
Note that HTML is both more important and easier
CSS is complicated and tricky, but ultimately it's mostly cosmetic.
(But I'm a nerd: I dress for function, not fashion.)