Live data from Hacker News

Web Fundamentals: A handbook for best practices

developers.google.com

21–30 of 66 posts

Re: Web Fundamentals: A handbook for best practices

#21
post #19

With the title 'Web Fundamentals', from Google there might be something good there to learn. Butm three points: (1) "Multi-screen" is not in my Funk and Wagnalls and, thus, has a specialized meaning, is a 'term', and needs at least a definition and likely also motivation, explanation, and examples. So, the author of this course on writing Web sites doesn't know how to write. (2) He says that the course will end with…

Hi, We will get these sorted. I was surprised that this got picked up so early as we were just starting to canvas feedback from developers, so it still a work in progress.

Multi-screen/Multi-device was the term we chose because mobile-first is a very very loaded and our goal is to target mobile as a base but ensure everyone builds up from that experience. But you are correct, it needs to be introduced.

[Edit] - adding bugs https://github.com/google/WebFundamentals/issues/17 https://github.com/google/WebFundamentals/issues/18

Re: Web Fundamentals: A handbook for best practices

#22
post #18

I really hope this design pattern of huge fonts across the screen is a fad and will go away sometime soon. That and parallax scrolling. It's bugging me to no end for some reason. Am I alone in this?

No, I can't stand design which say "you read our heading, great! Now scroll a bit to read the next 5 words" either.

Re: Web Fundamentals: A handbook for best practices

#26

Somewhat surprised there's no discussion of security going on here - even at a design level, there are some useful considerations.

Good point. We're planning to add more content later. What's on the site now is what we were able to write in the first 6 weeks. The goal is to eventually grow this to be as thorough as developers.android.com or iOS Dev Center (but for the web).

Re: Web Fundamentals: A handbook for best practices

#27
post #24

The requested URL /web/fundamentals/resources/samples/getting-started/your-first-multi-screen-site/addvideo was not found on this server.

Hmm. For me it correctly redirects to the appropriate path on google-developers.appspot.com. Could you verify that you're still having trouble and if so file an issue describing where specifically you encountered the dead link?

https://github.com/google/WebFundamentals/issues/new

Re: Web Fundamentals: A handbook for best practices

#29
post #17
post #15

a) How is one supposed to know what is clickable on that webpage? b) Why are the circles not valid click targets? c) If you say this -> "To deliver the best user experience, we must deliver content as quickly as possible (<1 second)" then why does your section on Critical Rendering Path show the optimized page load in 1.5 seconds?

Great points. thanks for the feedback. I have an open issue to ensure that it is clearer to understand which elements are clickable. (b) is frustrating. (c) when I tested it today it loaded in 0.6 seconds, but I will work with Ilya on getting this sorted asap ( https://github.com/google/WebFundamentals/issues/14 ).

For issue 14, I believe he meant that the image on the page (https://developers.google.com/web/fundamentals/documentation...) shows the optimized rendering taking 1.5 seconds, not that the page itself loads in 1.5 seconds.

Re: Web Fundamentals: A handbook for best practices

#30
While there's good advice contained within, the phrase "best practices" in the title may already be off-putting to some, because of how overused it's been to describe anything that anyone at one time thought was a good idea, leading to assuming that there is always only one "best" way to do something. In my experience, there never is.
Post reply on HN