Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HTML/CSS] Various improvements to web and clients #45

Closed
pamelafox opened this issue Oct 11, 2013 · 2 comments
Closed

[HTML/CSS] Various improvements to web and clients #45

pamelafox opened this issue Oct 11, 2013 · 2 comments
Labels
stale No updates for over 30 days.

Comments

@pamelafox
Copy link
Contributor

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 are programs that access and render content...

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)

  • Chrome now uses Blink, a fork of Webkit
  • Perhaps list Opera to show sharing of Blink (and because it's listed on "Browsers" slide)

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 believe ipconfig 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.

@stale
Copy link

stale bot commented Aug 16, 2018

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.

@stale stale bot added the stale No updates for over 30 days. label Aug 16, 2018
@stale
Copy link

stale bot commented Aug 23, 2018

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. 💛

@stale stale bot closed this as completed Aug 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale No updates for over 30 days.
Projects
None yet
Development

No branches or pull requests

3 participants