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

Front-End Checklist

github.com

Post reply on HN
Print view View original

21–30 of 82 posts

Re: Front-End Checklist

#21

Post by Teichopsia »

robin_reala wrote: post #17
Teichopsia wrote: post #13

Earlier quoted context omitted.

Do you mean like that? Empty quotes and it would not be read?

Exactly. Every img element should have an alt attribute; those with visual content should have explanatory text in it.

:D I knew that. I'm not that noobish.

Let's see. If we use an image that doesn't add anything to the content, one would normally use background-attachment to add an image to say, the hero section.

(It seems you edited your comment?)

Good to know that the screen reader would try to read the file name if there isn't any alt text in it, I didn't know that. So, in the cases we do need to place an img in the document, then we simple place an empty alt text as in my above comment to tell the screen reader not to read the file name since it is only used for decorative purposes...?

Edit: I confused your comment with another one.

Re: Front-End Checklist

#23

Post by Deimorz »

MatthewPhillips wrote: post #20

Note that you don't actually need the head or body tags in your page. The browser already knows what is allowed in the head. It looks weird at first, but you can write your html like so: My Title Also note that the html tag can also be omitted, unless you need to set the language. Don't worry about closing it either.

Edit: my original comment (retained below) is wrong about this being malformed, and it's completely valid. Some more info here: https://html.spec.whatwg.org/multipage/syntax.html#optional-...

---

Original comment:

The fact that browsers are able to handle malformed HTML doesn't mean that you should do it that way. There's no meaningful benefit that I can think of, and the potential to break a ton of things that aren't as lenient.

Re: Front-End Checklist

#24

Post by jkaljundi »

miguelrochefort wrote: post #4
jkaljundi wrote: post #3

Are sitemaps still a thing that really matters?

Don't you wanna get crawled?

Have not found the crawl rates changed for sites where everything is well linked together. Then again, these have been just small sites with a few million pages.

Re: Front-End Checklist

#25

Post by mileycyrusXOXO »

irrational wrote: post #19
miguelrochefort wrote: post #4

Earlier quoted context omitted.

Don't you wanna get crawled?

Actually I do work on a website that we do not want crawled. It would be handy to know which things to leave out to make it less likely your site will be crawled or show up high in a google result.

Just define a robot.txt file instructing the crawler to not index your website.

See: http://www.robotstxt.org/

Re: Front-End Checklist

#26

Post by davedx »

These are very subjective, I've never done half of the 'high' priority items, and I've never had any issues with my site having a 'disfunction'. Take this list with a gigantic grain of salt.

For example, your site certainly won't break from missing the 'lang' attribute.

Re: Front-End Checklist

#27

Post by Pxtl »

Deimorz wrote: post #23
MatthewPhillips wrote: post #20

Note that you don't actually need the head or body tags in your page. The browser already knows what is allowed in the head. It looks weird at first, but you can write your html like so: My Title Also note that the html tag can also be omitted, unless you need to set the language. Don't worry about closing it either.

Edit: my original comment (retained below) is wrong about this being malformed, and it's completely valid. Some more info here: https://html.spec.whatwg.org/multipage/syntax.html#optional-... --- Original comment : The fact that browsers are able to handle malformed HTML doesn't mean that you should do it that way. There's no meaningful benefit that I can think of, and the potential to break a ton of things that aren…

The new craziness is basically that HTML is no longer structured as a tree, no more closing tags that don't semantically hold data, etc.

Re: Front-End Checklist

#28

Post by irrational »

Deimorz wrote: post #23
MatthewPhillips wrote: post #20

Note that you don't actually need the head or body tags in your page. The browser already knows what is allowed in the head. It looks weird at first, but you can write your html like so: My Title Also note that the html tag can also be omitted, unless you need to set the language. Don't worry about closing it either.

Edit: my original comment (retained below) is wrong about this being malformed, and it's completely valid. Some more info here: https://html.spec.whatwg.org/multipage/syntax.html#optional-... --- Original comment : The fact that browsers are able to handle malformed HTML doesn't mean that you should do it that way. There's no meaningful benefit that I can think of, and the potential to break a ton of things that aren…

My understanding is that it is not malformed, but actually a part of the spec. Maybe someone else has a link to the appropriate part of the spec, but following someone else's link to the spec and reading it for myself is how I learned that it is not malformed.

Re: Front-End Checklist

#29

Post by Yaggo »

Deimorz wrote: post #23
MatthewPhillips wrote: post #20

Note that you don't actually need the head or body tags in your page. The browser already knows what is allowed in the head. It looks weird at first, but you can write your html like so: My Title Also note that the html tag can also be omitted, unless you need to set the language. Don't worry about closing it either.

Edit: my original comment (retained below) is wrong about this being malformed, and it's completely valid. Some more info here: https://html.spec.whatwg.org/multipage/syntax.html#optional-... --- Original comment : The fact that browsers are able to handle malformed HTML doesn't mean that you should do it that way. There's no meaningful benefit that I can think of, and the potential to break a ton of things that aren…

It's not malformed in the traditional meaning, the HTML5 spec actually says that HTML, HEAD, BODY, etc. unambiguous tags can be omitted.

Re: Front-End Checklist

#30

Post by franze »

jkaljundi wrote: post #24
miguelrochefort wrote: post #4

Earlier quoted context omitted.

Don't you wanna get crawled?

Have not found the crawl rates changed for sites where everything is well linked together. Then again, these have been just small sites with a few million pages.

measurability

crawling != indexing

with a segmented sitemap (i.e.: one per pagetype, per namespace, ..) you get important communicated to indexed ratios you otherwise do not get.

if crawling and indexing works, it works but if it doesn't you should know it (see it in google search console) and debug it (narrow it down via segmented sitemaps).

Post reply on HN