You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The client/browser/server interaction image is a bit too simply. Maybe add URL under the arrow between client and browser (and add navigation field to browser image), and add an additional arrow going from browser to server requesting a specific page? I also like the additional step listed in this image (source) where the server has to find the "data".
"...each browser varies in how it displays webpages" seems drastic to me, as though each webpage will look completely different in each browser. Perhaps "...each browser can vary slightly in how it displays webspages." to show the end result can be pixel-perfect, but it's not always the case, especially with newly added elements/features.
The chart is about a year out of date. Link is helpful, but would be nice to see an updated chart. Would be awesome if this could be generated on the fly from data pulled from somewhere (perhaps gs.statcounter.com like caniuse.com?).
It may be useful to explain how developers [should] choose which browsers they want to focus on. Perhaps add a link to caniuse.com.
IPv6 is mentioned, described as a number, but hexidecimal is show. May want to mention what hexidecimal is (base 16) and perhaps link to the Wikipedia article for IPv4/IPv6/Hexidecimal.
According to Wikipedia, 127.0.0.1 isn't necessarily always the "self" address, so I'd suggest rewording to say "usually". And, for IPv6, it is ::1.
ifconfig isn't available on Windows machines, and is being deprecated on Linux. ip address can be used on Linux, and I believe ipconfig is the command for Windows.
Maybe add node.js to list of server-side programming languages? It's JavaScript, so, theoretically, those who see these slides will soon know JavaScript too. Might be too much information for a beginner though.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been updated in the last 30 days. It will be closed if no further activity occurs within the next 7 days. Feel free to reach out on the #opensource channel in our Slack team or mention an admin for further help and resources if they are needed.
This issue has been automatically closed due to max staleness.
Thank you so much for your contributions to Girl Develop It SF.
Please feel free to open up another PR at any time. 💛
Thanks to Brandon Frohs:
HTML/CSS Lesson 1 Slides
Next/previous slides are visible (unlike in Lesson 2).
The Web (#2)
The client/browser/server interaction image is a bit too simply. Maybe add URL under the arrow between client and browser (and add navigation field to browser image), and add an additional arrow going from browser to server requesting a specific page? I also like the additional step listed in this image (source) where the server has to find the "data".
Clients (#3)
Tablets may be worth adding to the list of devices.
Browsers (#4)
Perhaps change the first sentence to be more descriptive:
Browsers (#5)
"...each browser varies in how it displays webpages" seems drastic to me, as though each webpage will look completely different in each browser. Perhaps "...each browser can vary slightly in how it displays webspages." to show the end result can be pixel-perfect, but it's not always the case, especially with newly added elements/features.
Browser Parts (#6)
Browser Usage (#7)
The chart is about a year out of date. Link is helpful, but would be nice to see an updated chart. Would be awesome if this could be generated on the fly from data pulled from somewhere (perhaps gs.statcounter.com like caniuse.com?).
It may be useful to explain how developers [should] choose which browsers they want to focus on. Perhaps add a link to caniuse.com.
Step 1: The URL Breakdown (#9)
May want to add a port example (ports are used later, but not explained).
Step 2: Server Name -> IP (#10)
Bottom of image (including the source of the image) is cut off.
IP Addresses (#11)
IPv6 is mentioned, described as a number, but hexidecimal is show. May want to mention what hexidecimal is (base 16) and perhaps link to the Wikipedia article for IPv4/IPv6/Hexidecimal.
According to Wikipedia,
127.0.0.1
isn't necessarily always the "self" address, so I'd suggest rewording to say "usually". And, for IPv6, it is::1
.ifconfig
isn't available on Windows machines, and is being deprecated on Linux.ip address
can be used on Linux, and I believeipconfig
is the command for Windows.Servers (#15)
Maybe add node.js to list of server-side programming languages? It's JavaScript, so, theoretically, those who see these slides will soon know JavaScript too. Might be too much information for a beginner though.
The text was updated successfully, but these errors were encountered: