8 ms·
Front-End Checklist
- miguelrochefort 9y agoIt's already missing iPhone X support.
- zeronight 9y agoIt will be interesting to find what the visitor percentages are for iPhone x. Even though its Apple, at some point its not worth spending the time and money.
- miguelrochefort 9y agoThe iPhone X will be sold out everywhere until 2018.
- jkaljundi 9y agoAre sitemaps still a thing that really matters?
- miguelrochefort 9y agoDon't you wanna get crawled?
- irrational 9y agoActually 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.
- mileycyrusXOXO 9y agoJust define a robot.txt file instructing the crawler to not index your website. See: http://www.robotstxt.org/ http://www.robotstxt.org/
- seanwilson 9y agoThis is a common misconception: https://support.google.com/webmasters/answer/7424835?hl=en#h17 https://support.google.com/webmasters/answer/7424835?hl=en#h... > robots.txt Disallow does not guarantee that a page will not appear in results: Google may still decide, based on external information such as incoming links, that it is relevant. If you wish to explicitly block a page from being indexed, you should instead use the noindex robots meta tag or X-Robots-Tag HTTP header. If it's something like a staging site, you'd be better putting it behind a login screen to prevent mistakes anyway.
- jkaljundi 9y agoHave 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.
- franze 9y agomeasurability 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).
- andrei_says_ 9y agoCurious if you have examples of the types of sitemaps you mentioned: segmentation, namespacing, one per pagetype etc. and the reasoning behind the variations.
- franze 9y agoi.e.: tourradar.com/robots.txt
- hayksaakian 9y agoIf you're coding it from scratch, don't bother. If you're using wordpress or another pre-baked system, then it's worth having a sitemap plugin (example: Yoast SEO) or the built-in sitemap (like for Shopify). Submit it to Google Search Console, Bing, and you're done (essentially).
- franze 9y ago<body lang="en"> - High? why?
- stephenr 9y agoI'd have thought things like that were better handled as a response header (same for the charset).
- robin_reala 9y agoNo, because pages can be saved, and then the page loses the information. Or rather, by all means do it (it does get the information to the browser quicker) but make sure you also add the information to the page.
- Teichopsia 9y agoI also found that odd. I've always placed mine in the HTML tag. <html lang="en"> tough, I don't know what the difference is.
- robin_reala 9y agoPutting it on <html> is better as that defines the language for <title> as well. The lang attribute defines the language of the tree that the element is the root node of.
- franze 9y agostill, who uses it for what? browsers dont change behaviour because of it, search engines ignore it, users dont see it.
- robin_reala 9y ago1. The main reason is screen readers. Imagine a screen reader trying to pronounce ‘Je ne regrette rien’ with an English voice, then imagine the same with a French voice. 2. I’d be surprised if search engines didn’t use it at least as a flag for content language (although I’m sure that it‘s only supplemental at best). 3. Styling based on language. CSS has a :lang() pseudoclass selector so you can do p:lang(en) { color: red; } p:lang(fr) { color: blue; } . Or tie quote styles to language based on generated content. Or most usefully adjust font metrics based on language for multilingual sites (typically you’d want to boost the font size a little for Chinese or Japanese as there are less characters for same information, but each character is a little more dense).
- Raphmedia 9y ago> Alternative text: High All <img> have an alternative text which describe the image visually. Please don't do that. Don't put an alt on ALL images. Screen readers will read all of them. Skin and flavour images don't deserve to be read outloud. Nobody wants to hear "bottom left corner of logo" or "rounded corner".
- robin_reala 9y agoTypically you’d use background images for something like that. Regardless, if you do have an image that doesn’t add anything to the information on the page give it an empty alt attribute to indicate to the screen reader that it shouldn’t try to read out the file name or something.
- Teichopsia 9y ago<img src=".." alt=""> Do you mean like that? Empty quotes and it would not be read?
- robin_reala 9y agoExactly. Every img element should have an alt attribute; those with visual content should have explanatory text in it.
- Teichopsia 9y ago: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.
- 9y ago
- stefantheard 9y agoAwesome list, I always forget about several things on here it's going to be nice to have a reference to prevent that from happening.
- iKenshu 9y agoWhat about back-end? Should be nice have one
- techtalsky 9y agoOWASP guidelines are a good start.
- MatthewPhillips 9y agoNote 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: <!doctype html> <html lang="en"> <title>My Title</title> <div id="main"></div> Also note that the html tag can also be omitted, unless you need to set the language. Don't worry about closing it either.
- Deimorz 9y agoEdit: 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-tags 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.
- Pxtl 9y agoThe new craziness is basically that HTML is no longer structured as a tree, no more closing tags that don't semantically hold data, etc.
- irrational 9y agoMy 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.
- SippinLean 9y ago>Tag omission in text/html: >An html element's start tag can be omitted if the first thing inside the html element is not a comment. >An html element's end tag can be omitted if the html element is not immediately followed by a comment. https://www.w3.org/TR/html5/semantics.html#the-html-element https://www.w3.org/TR/html5/semantics.html#the-html-element
- davedx 9y agoThese 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.
- DerfNet 9y agosubmit a pull request
- groby_b 9y agoNo. But e.g. automated translation now needs to guess your language, and that's... not always successful. Screenreaders will need to guess the language to pronounce properly. Search engines will have to infer the language. And so on. Your site isn't "broken", per se, but it's not as high quality as it could be.
- chrismorgan 9y agoI wonder how much lang=en can actually be trusted—enough things put it in by default that I can easily imagine its presence on non-English pages. Update: from elsewhere on this thread, Google ignores <html lang>: > But the language attribute within the HTML markup is something we don't use at all. We've found that this language markup is something that is almost always wrong. So we tend to ignore that. https://www.seroundtable.com/google-ignores-the-html-lang-attribute-22974.html https://www.seroundtable.com/google-ignores-the-html-lang-at...
- groby_b 9y agoIt tends to be more reliable if it's not lang=en. The cargo culting nature of web development makes some things a bit painful. FWIW, Chrome's translate feature does care about lang=. Or at least it did last time I checked. It's one of the things that has no downside, and a small upside. If you leave it out, your site isn't horribly broken. People will always get the content, but tools that process the content might be wrong.
- amk_ 9y agoThis would be a good checklist for anyone considering building a UI framework. This kind of thing is the reason Bootstrap & friends are so large - they do a lot for you.
- threatofrain 9y agoAn oft overstated thing -- but the organization of CSS is currently being massaged by the front end community, and in-line CSS is no longer considered an awful thing with Radium and others.
- ozaark 9y agoSeems like this could be presented without as much clutter. Not really useful at a glance for a checklist. Also, some of the info isn't well researched and lacks citations for claims as others have mentioned. One would be better off just using the Google Web Starter kit[1], other boilerplate options, or just chrome dev tools running Audits to get started with a solid front-end. [1] https://developers.google.com/web/tools/starter-kit/ https://developers.google.com/web/tools/starter-kit/
- rco8786 9y agoFollowing this list is a great way to never launch something into production.
- speedplane 9y agoSeriously... surprised there isn't a tabs or spaces diatribe in there.
- sergeyfilippov 9y agoJust keep a boilerplate handy I've helped a friend to publish a one-page website over the weekend, and I believe it follows most of this checklist
- chente 9y agoPixel perfection, are we still striving for that?
- ravenstine 9y ago> All <img> have height and width set (Don't specify px or %) So what unit should be used?
- CM30 9y agoNone, image height and width attributes don't have the unit included. (They generally assume these values are in pixels by default[1]) https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img https://developer.mozilla.org/en-US/docs/Web/HTML/Element/im...
- frio 9y agoI can't help but notice there's no "Security" section. Perhaps by the time you've got the HTML rendering it's too late, but SRI tags, CSP headers and whatnot all deserve some mention. https://github.com/thedaviddias/Front-End-Checklist/issues/23 https://github.com/thedaviddias/Front-End-Checklist/issues/2...
- mycentstoo 9y agoWhat would be a great idea is an app that scans for the presence of these conditions.
- laktek 9y agoIf anyone wants to have a crack at it, you can use Page.REST to build it. If not I might be able to get to it towards next week :)
- speedplane 9y agoHere's a better checklist: Run a W3 validator on your HTML, fix the red stuff that isn't too annoying to fix. Launch. Deal with all that other stuff later.
- adad95 9y agoI love the http://webdevchecklist.com/ http://webdevchecklist.com/ site.
- swoongoonz 9y ago>Pixel perfect: High Pages are close to pixel perfect. Depending on the quality of the creatives, you may not be 100% accurate, but your page needs to be close to your template. What is this 2004?