Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Web Fundamentals: A handbook for best practices

developers.google.com

Post reply on HN
Print view View original

11–20 of 66 posts

Re: Web Fundamentals: A handbook for best practices

#11

Post by kinlan »

aresant wrote: post #10
kinlan wrote: post #4

Earlier quoted context omitted.

Certainly! Good call. We soft launched the site today and are still very actively improving things. I like your suggestions though. I broke the menu and a fix is heading out soon. I'll file the others so we can get them addressed. [EDITED.]

a) Sorry to be a grumbler, I know how hard it is to launch anything. You rock for instantly adding these to git and I appreciate the response. b) I spent a few more mins on the site after posting the comment, the lesson content is very strong. I wonder if the content would be better served by removing the stuff below your headline on https://developers.google.com/web/fundamentals/ - eg those links are where I immedia…

:) we will certainly get them sorted. We are also looking at the nav and the quick access to the content so the links are more easily accessible.

Re: Web Fundamentals: A handbook for best practices

#14

Post by Braunbart »

The icons are broken in firefox because you used a webfont wich is hosted on another domain.

Edit: Just saw that you already know about this: https://github.com/google/WebFundamentals/issues/13

--- Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://web-central.appspot.com/web/essentials/icons/icons.w.... This can be fixed by moving the resource to the same domain or enabling CORS.

Re: Web Fundamentals: A handbook for best practices

#15

Post by dman »

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?

Re: Web Fundamentals: A handbook for best practices

#16

Post by kinlan »

Braunbart wrote: post #14

The icons are broken in firefox because you used a webfont wich is hosted on another domain. Edit: Just saw that you already know about this: https://github.com/google/WebFundamentals/issues/13 --- Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://web-central.appspot.com/web/essentials/icons/icons.w... . This can be fixed by moving the resource to the same domain or…

Thanks for the information. I have updated the tickets (also #2). We will get it sorted asap - there are some plumbing issues that I need to resolve on the main site to get this sorted.

Re: Web Fundamentals: A handbook for best practices

#17

Post by kinlan »

dman wrote: 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).

Re: Web Fundamentals: A handbook for best practices

#19

Post by graycat »

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 a 'landing page'. I don't really know what the heck that is. Once again he is long on obscure terminology and short on definitions.

Apparently he likes his own jargon. Bummer.

(3) His page has a black background with faint type that is nearly impossible to read. In addition he has some 'swaths' of light across the text making the page next to impossible to read. Maybe if I 'selected' the text from the page or got the HTML and extracted the text I could read it, but what he has is not good.

Bummer.

Re: Web Fundamentals: A handbook for best practices

#20

Post by graycat »

dman wrote: 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?

> a) How is one supposed to know what is clickable on that webpage?

And the candidates are, look at the HTML and JS code, write a simulator that can in effect click on each pixel on the page, submit a question to Stack Overflow, click on every candidate spot on the page. May I have the envelope, please (drum roll)? And the winner is, click on every candidate spot on the page! And the winner thanks all the losers and wishes them still less luck the next time!

But, we already knew all this, right?

Was the role in user interface and user experience at Google really that important?

Post reply on HN