ΠΠΎΠ½ΡΡΠΎΠ»ΡΠ½ΡΠΉ ΡΠΏΠΈΡΠΎΠΊ ΠΏΠΎ ΡΡΠΎΠ½ΡΠ΅Π½Π΄Ρ ΡΠ²Π»ΡΠ΅ΡΡΡ ΠΈΡΡΠ΅ΡΠΏΡΠ²Π°ΡΡΠΈΠΌ ΡΠΏΠΈΡΠΊΠΎΠΌ Π²ΡΠ΅Ρ ΡΠ»Π΅ΠΌΠ΅Π½ΡΠΎΠ², ΠΊΠΎΡΠΎΡΡΠ΅ Π²Ρ Π΄ΠΎΠ»ΠΆΠ½Ρ ΠΈΠΌΠ΅ΡΡ / ΠΏΡΠΎΠ²Π΅ΡΠΈΡΡ ΠΏΠ΅ΡΠ΅Π΄ Π·Π°ΠΏΡΡΠΊΠΎΠΌ Π²Π°ΡΠ΅Π³ΠΎ ΡΠ°ΠΉΡΠ° / HTML ΡΡΡΠ°Π½ΠΈΡΡ Π² ΠΏΡΠΎΠ΄Π°ΠΊΡΠ½.
ΠΠ½ ΠΎΡΠ½ΠΎΠ²Π°Π½ Π½Π° ΠΌΠ½ΠΎΠ³ΠΎΠ»Π΅ΡΠ½Π΅ΠΌ ΠΎΠΏΡΡΠ΅ ΡΡΠΎΠ½ΡΠ΅Π½Π΄ ΡΠ°Π·ΡΠ°Π±ΠΎΡΡΠΈΠΊΠΎΠ², Ρ Π·Π°ΠΈΠΌΡΡΠ²ΠΎΠ²Π°Π½ΠΈΡΠΌΠΈ ΠΈΠ· Π½Π΅ΠΊΠΎΡΠΎΡΡΡ Π΄ΡΡΠ³ΠΈΡ ΠΎΠΏΠ΅Π½ΡΠΎΡΡΠ½ΡΡ ΡΠ΅ΠΊΠ»ΠΈΡΡΠΎΠ².
ΠΠΎΠΌΠΎΠ³ΠΈ ΡΠ°ΡΠΏΡΠΎΡΡΡΠ°Π½ΠΈΡΡ Front-End Checklist ΠΏΡΠΎΠ³ΠΎΠ»ΠΎΡΠΎΠ²Π°Π² ΠΈ ΠΏΠΎΡΠ΅ΠΊΠΎΠΌΠ΅Π½Π΄ΠΎΠ²Π°Π² Π΅Π³ΠΎ Π½Π° Product Hunt
- Head
- HTML
- ΠΠ΅Π±-ΡΡΠΈΡΡΡ
- CSS
- ΠΠ·ΠΎΠ±ΡΠ°ΠΆΠ΅Π½ΠΈΡ
- JavaScript
- ΠΠ΅Π·ΠΎΠΏΠ°ΡΠ½ΠΎΡΡΡ
- ΠΡΠΎΠΈΠ·Π²ΠΎΠ΄ΠΈΡΠ΅Π»ΡΠ½ΠΎΡΡΡ
- ΠΠΎΡΡΡΠΏΠ½ΠΎΡΡΡ
- SEO
ΠΠ»Ρ Π±ΠΎΠ»ΡΡΠΈΠ½ΡΡΠ²Π° ΠΏΡΠΎΠ΅ΠΊΡΠΎΠ² ΡΡΠ΅Π±ΡΡΡΡΡ Π²ΡΠ΅ ΡΠ»Π΅ΠΌΠ΅Π½ΡΡ ΠΊΠΎΠ½ΡΡΠΎΠ»ΡΠ½ΠΎΠ³ΠΎ ΡΠΏΠΈΡΠΊΠ°, Π½ΠΎ Π½Π΅ΠΊΠΎΡΠΎΡΡΠ΅ ΡΠ»Π΅ΠΌΠ΅Π½ΡΡ ΠΌΠΎΠ³ΡΡ Π±ΡΡΡ ΠΎΠΏΡΡΠ΅Π½Ρ ΠΈΠ»ΠΈ Π½Π΅ Π±ΡΡΡ ΡΡΡΠ΅ΡΡΠ²Π΅Π½Π½ΡΠΌΠΈ (Π½Π°ΠΏΡΠΈΠΌΠ΅Ρ, Π² ΡΠ»ΡΡΠ°Π΅ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΈΠ²Π½ΠΎΠ³ΠΎ Π²Π΅Π± ΠΏΡΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΡ, Π²Π°ΠΌ ΠΌΠΎΠΆΠ΅Ρ Π½Π΅ ΠΏΠΎΠ½Π°Π΄ΠΎΠ±ΠΈΡΡΡΡ Π»Π΅Π½ΡΠ° RSS). ΠΡ ΡΠ΅ΡΠΈΠ»ΠΈ ΠΈΡΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΡ 3 ΡΡΠΎΠ²Π½Ρ Π΄Π»Ρ Π³ΠΈΠ±ΠΊΠΎΡΡΠΈ:
ΠΎΠ·Π½Π°ΡΠ°Π΅Ρ, ΡΡΠΎ ΡΠ»Π΅ΠΌΠ΅Π½Ρ ΡΠ΅ΠΊΠΎΠΌΠ΅Π½Π΄ΡΠ΅ΡΡΡ ΠΈΡΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΡ, Π½ΠΎ ΠΎΠ½ ΠΌΠΎΠΆΠ΅Ρ Π±ΡΡΡ ΠΎΠΏΡΡΠ΅Π½ Π² Π½Π΅ΠΊΠΎΡΠΎΡΡΡ ΠΊΠΎΠ½ΠΊΡΠ΅ΡΠ½ΡΡ ΡΠ»ΡΡΠ°ΡΡ .
ΠΎΠ·Π½Π°ΡΠ°Π΅Ρ, ΡΡΠΎ ΡΠ»Π΅ΠΌΠ΅Π½Ρ Π½Π°ΡΡΠΎΡΡΠ΅Π»ΡΠ½ΠΎ ΡΠ΅ΠΊΠΎΠΌΠ΅Π½Π΄ΠΎΠ²Π°Π½ΠΎ ΠΈΡΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΡ ΠΈ ΠΎΠ½ ΠΌΠΎΠΆΠ΅Ρ Π±ΡΡΡ ΠΎΠΏΡΡΠ΅Π½ Π² ΠΏΠΎ-Π½Π°ΡΡΠΎΡΡΠ΅ΠΌΡ ΡΠ°ΡΡΠ½ΡΡ ΡΠ»ΡΡΠ°ΡΡ . ΠΠ΅ΠΊΠΎΡΠΎΡΡΠ΅ ΡΠ»Π΅ΠΌΠ΅Π½ΡΡ, Π΅ΡΠ»ΠΈ ΠΈΡ ΠΏΡΠΎΠΏΡΡΡΠΈΡΡ, ΠΌΠΎΠ³ΡΡ ΠΏΠΎΠ²Π»Π΅ΡΡ Π·Π° ΡΠΎΠ±ΠΎΠΉ ΠΏΠ»ΠΎΡ ΠΈΠ΅ ΠΏΠΎΡΠ»Π΅Π΄ΡΡΠ²ΠΈΡ Ρ ΡΠΎΡΠΊΠΈ Π·ΡΠ΅Π½ΠΈΡ ΠΏΡΠΎΠΈΠ·Π²ΠΎΠ΄ΠΈΡΠ΅Π»ΡΠ½ΠΎΡΡΠΈ ΠΈΠ»ΠΈ SEO.
ΠΎΠ·Π½Π°ΡΠ°Π΅Ρ, ΡΡΠΎ ΡΠ»Π΅ΠΌΠ΅Π½Ρ Π² Π»ΡΠ±ΠΎΠΌ ΡΠ»ΡΡΠ°Π΅ Π½Π΅ ΠΌΠΎΠΆΠ΅Ρ Π±ΡΡΡ ΠΎΠΏΡΡΠ΅Π½. ΠΡ ΠΌΠΎΠΆΠ΅ΡΠ΅ ΠΏΠΎΠ»ΡΡΠΈΡΡ Π½Π΅ΠΊΠΎΡΡΠ΅ΠΊΡΠ½ΡΡ ΡΠ°Π±ΠΎΡΡ ΡΠ²ΠΎΠ΅ΠΉ ΡΡΡΠ°Π½ΠΈΡΡ ΠΈΠ»ΠΈ ΠΏΡΠΎΠ±Π»Π΅ΠΌΡ Ρ Π΄ΠΎΡΡΡΠΏΠ½ΠΎΡΡΡΡ ΠΈΠ»ΠΈ SEO. Π ΠΏΠ΅ΡΠ²ΡΡ ΠΎΡΠ΅ΡΠ΅Π΄Ρ ΠΏΡΠΈΠΎΡΠΈΡΠ΅Ρ ΡΠ΅ΡΡΠΈΡΠΎΠ²Π°Π½ΠΈΡ Π΄ΠΎΠ»ΠΆΠ΅Π½ Π±ΡΡΡ Π½Π° ΡΡΠΈΡ ΡΠ»Π΅ΠΌΠ΅Π½ΡΠ°Ρ .
Π£ Π½Π΅ΠΊΠΎΡΠΎΡΡΡ ΡΠ΅ΡΡΡΡΠΎΠ² Π΅ΡΡΡ ΠΈΠΊΠΎΠ½ΠΊΠ°, ΠΊΠΎΡΠΎΡΠ°Ρ ΠΏΠΎΠΌΠΎΠΆΠ΅Ρ Π²Π°ΠΌ ΠΏΠΎΠ½ΡΡΡ, ΠΊΠ°ΠΊΠΎΠΉ ΡΠΈΠΏ ΠΊΠΎΠ½ΡΠ΅Π½ΡΠ° / ΠΏΠΎΠΌΠΎΡΠΈ Π²Ρ ΠΌΠΎΠΆΠ΅ΡΠ΅ Π½Π°ΠΉΡΠΈ Π² ΠΊΠΎΠ½ΡΡΠΎΠ»ΡΠ½ΠΎΠΌ ΡΠΏΠΈΡΠΊΠ΅:
- π: Π΄ΠΎΠΊΡΠΌΠ΅Π½ΡΠ°ΡΠΈΡ ΠΈΠ»ΠΈ ΡΡΠ°ΡΡΡ
- π : ΠΎΠ½Π»Π°ΠΉΠ½ ΠΈΠ½ΡΡΡΡΠΌΠ΅Π½Ρ / ΠΈΠ½ΡΡΡΡΠΌΠ΅Π½Ρ ΡΠ΅ΡΡΠΈΡΠΎΠ²Π°Π½ΠΈΡ
- πΉ: ΠΌΠ΅Π΄ΠΈΠ° ΠΈΠ»ΠΈ Π²ΠΈΠ΄Π΅ΠΎ ΠΊΠΎΠ½ΡΠ΅Π½Ρ
Notes: You can find a list of everything that could be found in the
<head>of an HTML document.
- Doctype:
<!-- Doctype HTML5 -->
<!doctype html>The next 3 meta tags (Charset, X-UA Compatible and Viewport) need to come first in the head.
- Charset:
<!-- Set character encoding for the document -->
<meta charset="utf-8">- X-UA-Compatible:
<!-- Instruct Internet Explorer to use its latest rendering engine -->
<meta http-equiv="x-ua-compatible" content="ie=edge">- Viewport:
<!-- Viewport for responsive web design -->
<meta name="viewport" content="width=device-width, initial-scale=1">- Title:
<!-- Document Title -->
<title>Page Title less than 55 characters</title>
- π Title - HTML - MDN
- π SERP Snippet Generator
- Description:
<!-- Meta Description -->
<meta name="description" content="Description of the page less than 150 characters">- Favicons:
favicon.ico, put it at the root of your site. Normally you won't need to use any markup. However, it's still good practice to link to it using the example below. Today, PNG format is recommended over.icoformat (dimensions: 32x32px).
<!-- Standard favicon -->
<link rel="icon" type="image/x-icon" href="https://example.com/favicon.ico">
<!-- Recommended favicon format -->
<link rel="icon" type="image/png" href="https://example.com/favicon.png">- Apple Touch Icon:
<!-- Apple Touch Icon -->
<link rel="apple-touch-icon" href="/custom-icon.png">- Windows Tiles:
<!-- Microsoft Tiles -->
<meta name="msapplication-config" content="browserconfig.xml" />Minimum required xml markup for the browserconfig.xml file is as follows:
<?xml version="1.0" encoding="utf-8"?>
<browserconfig>
<msapplication>
<tile>
<square70x70logo src="small.png"/>
<square150x150logo src="medium.png"/>
<wide310x150logo src="wide.png"/>
<square310x310logo src="large.png"/>
</tile>
</msapplication>
</browserconfig>- Canonical:
rel="canonical"to avoid duplicate content.
<!-- Helps prevent duplicate content issues -->
<link rel="canonical" href="http://example.com/2017/09/a-new-article-to-red.html">- Language attribute:
langattribute of your website is specified and related to the language of the current page.
<html lang="en">- Direction attribute:
<html dir="rtl">
- π dir - HTML - MDN
- Alternate language:
<link rel="alternate" href="https://es.example.com/" hreflang="es">- Conditional comments:
-
RSS feed:
-
Inline critical CSS:
<style></style>in a single line (minified).
- π Critical by Addy Osmani on GitHub automates this
- CSS order:
<head>. (Except the case where sometimes JS files are loaded asynchronously on top of your page).
Facebook OG and Twitter Cards are, for any website, highly recommended. The other social media tags can be considered if you target a particular presence on those and want to ensure the display.
- Facebook Open Graph:
Notes: Using use
og:image:widthandog:image:heightwill specify the image dimensions to the crawler so that it can render the image immediately without having to asynchronously download and process it.
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/page.html">
<meta property="og:title" content="Content Title">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:description" content="Description Here">
<meta property="og:site_name" content="Site Name">
<meta property="og:locale" content="en_US">
<!-- Next tags are optional but recommended -->
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
- π A Guide to Sharing for Webmasters
- π Best Practices - Sharing
- π Test your page with the Facebook OG testing
- Twitter Card:
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@site_account">
<meta name="twitter:creator" content="@individual_account">
<meta name="twitter:url" content="https://example.com/page.html">
<meta name="twitter:title" content="Content Title">
<meta name="twitter:description" content="Content description less than 200 characters">
<meta name="twitter:image" content="https://example.com/image.jpg">
- π Getting started with cards β Twitter Developers
- π Test your page with the Twitter card validator
- HTML5 Semantic Elements:
- π HTML Reference
-
Error pages:
-
Noopener:
target="_blank", your link should have arel="noopener"attribute to prevent tab nabbing. If you need to support older versions of Firefox, userel="noopener noreferrer".
- π About rel=noopener
- Clean up comments:
- W3C compliant:
- π W3C validator
- HTML Lint:
- π Dirty markup
- Link checker:
- π W3C Link Checker
- Adblockers test:
Notes: Using webfonts may cause Flash Of Unstyled Text/Flash Of Invisible Text - consider having fallback fonts and/or utilizing webfont loaders to control behavior.
- Webfont format:
-
Webfont size:
-
Webfont loader:
Notes: Take a look at CSS guidelines and Sass Guidelines followed by most Front-End developers. If you have a doubt about CSS properties, you can visit CSS Reference. There is also a short Code Guide for consistency.
- Responsive Web Design:
- CSS Print:
- Preprocessors:
- Unique ID:
- Reset CSS:
- π Reset.css
- π Normalize.css
- π Reboot
- JS prefix:
<div id="js-slider" class="my-slider">
<!-- Or -->
<div id="id-used-by-cms" class="js-slider my-slider">- Embedded or inline CSS:
<style>tags or using inline CSS: only use for valid reasons (e.g. background-image for slider, critical CSS). - Vendor prefixes:
- Concatenation:
- Minification:
- Non-blocking:
- Unused CSS:
- π UnCSS Online π
- π PurifyCSS
- π Chrome DevTools Coverage
- Stylelint:
- π stylelint, a CSS linter
- π Sass guidelines
-
Responsive web design:
-
CSS Validator:
- π CSS Validator
- Desktop Browsers:
- Mobile Browsers:
- OS:
- Pixel perfect:
- Reading direction:
Notes: For a complete understanding of image optimization, check the free ebook Essential Image Optimization from Addy Osmani.
- Optimization:
- π Imagemin
- π Use ImageOptim to optimise your images for free.
- π Use Kraken.io awesome alternative for both png and jpg optimization. Up to 1mb per files on free plan.
- Picture/Srcset:
- Retina:
- Sprite:
- Width and Height:
widthandheightattributes on<img>if the final rendered image size is known (can be omitted for CSS sizing). - Alternative text:
<img>have an alternative text which describe the image visually.
- Lazy loading:
- JavaScript Inline:
- Concatenation:
- Minification:
.minsuffix).
- JavaScript security:
- Non-blocking:
asyncor deferred usingdeferattribute.
- Modernizr:
<html>tag.
- ESLint:
- HTTPS:
- HTTP Strict Transport Security (HSTS):
- Cross Site Request Forgery (CSRF):
- Cross Site Scripting (XSS):
- Content Type Options
- X-Frame-Options (XFO)
- Content Security Policy
- Weight page:
- Minified:
- π W3C Validator
-
Lazy loading:
-
Cookie size: If you are using cookies be sure each cookie doesn't exceed 4096 bytes and your domain name doesn't have more than 20 cookies.
- π Cookie specification: RFC 6265
- π Cookies
- π Browser Cookie Limits
- Third party components:
- DNS resolution:
dns-prefetch.
<link rel="dns-prefetch" href="https://example.com">- Preconnection:
preconnect.
<link rel="preconnect" href="https://example.com">- Prefetching:
prefetch.
<link rel="prefetch" href="image.png">- Preloading:
<body>) in advance usingpreload.
<link rel="preload" href="app.js">- Google PageSpeed:
Notes: You can watch the playlist A11ycasts with Rob Dodson πΉ
- Progressive enhancement:
- Color contrast:
- π Contrast ratio
- H1:
- Headings:
- Role banner:
<header>hasrole="banner". - Role navigation:
<nav>hasrole="navigation". - Role main:
<main>hasrole="main".
- Specific HTML5 input types are used:
- π Mobile Input Types
- Label:
aria-labelinstead.
- Accessibility standards testing:
- π Wave testing
- Keyboard navigation:
- Screen-reader:
- Focus style:
- Google Analytics:
- Headings logic:
- sitemap.xml:
- robots.txt:
- π Test your robots.txt with Google Robots Testing Tool
- Structured Data:
- π Introduction to Structured Data - Search - Google Developers
- π Test your page with the Structured Data Testing Tool
- π Complete list of vocabularies that can be used as structured data. Schema.org Full Heirarchy
- Sitemap HTML:
The Front-End Checklist is also available in other languages. Thanks for all translators and their awesome work!
- π―π΅ Japanese: miya0001/Front-End-Checklist
- πͺπΈ Spanish: eoasakura/Front-End-Checklist-ES
- π¨π³ Chinese: JohnsenZhou/Front-End-Checklist
- π°π· Korean: kesuskim/Front-End-Checklist
- π§π· Portuguese: jcezarms/Front-End-Checklist
- π»π³ Vietnamese: euclid1990/Front-End-Checklist
- πΉπΌ Traditional Chinese: EngineLin/Front-End-Checklist
If you want to show you are following the rules of the Front-End Checklist, put this badge on your README file!
β
[](https://github.com/thedaviddias/Front-End-Checklist/)Open an issue or a pull request to suggest changes or additions.
The Front-End Checklist repository consists of two branches:
This branch consists of the README.md file that is automatically reflected on the Front-End Checklist website.
This branch will be used to make some significant changes to the structure, content if needed. It is preferable to use the master branch to fix small errors or add a new item.
Check out all the super awesome contributors.
If you have any question or suggestion, don't hesitate to use Gitter or Twitter:
