├── .editorconfig ├── .github ├── FUNDING.yml ├── ISSUE_TEMPLATE.md ├── PULL_REQUEST_TEMPLATE.md └── workflows │ ├── links-checker.yml │ ├── readme-check.yml │ └── stale.yml ├── .gitignore ├── .husky └── pre-push ├── .markdownlint.json ├── .prettierrc ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── data └── images │ ├── logo-front-end-checklist.jpg │ └── priority │ ├── high.svg │ ├── low.svg │ └── medium.svg ├── lychee.toml ├── package.json └── pnpm-lock.yaml /.editorconfig: -------------------------------------------------------------------------------- 1 | root = true 2 | 3 | [*] 4 | charset = utf-8 5 | indent_style = space 6 | indent_size = 2 7 | end_of_line = lf 8 | insert_final_newline = true 9 | trim_trailing_whitespace = true 10 | -------------------------------------------------------------------------------- /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | open_collective: front-end-checklist 2 | github: thedaviddias 3 | thanks_dev: thedaviddias 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 3 | 4 | **Fixes**: # 5 | 6 | 🚨 Please review the [guidelines for contributing](CONTRIBUTING.md) and our [code of conduct](../CODE_OF_CONDUCT.md) to this repository. 🚨 7 | **Please complete these steps and check these boxes (by putting an x inside the brackets) before filing your PR:** 8 | 9 | - [ ] Check the commit's or even all commits' message styles matches our requested structure. 10 | - [ ] Check your code additions will fail neither code linting checks nor unit test. 11 | 12 | #### Short description of what this resolves: 13 | 14 | 15 | #### Proposed changes: 16 | 17 | - 18 | - 19 | - 20 | 21 | 👍 Thank you! 22 | -------------------------------------------------------------------------------- /.github/workflows/links-checker.yml: -------------------------------------------------------------------------------- 1 | name: Links Checker 2 | 3 | on: 4 | repository_dispatch: 5 | workflow_dispatch: 6 | schedule: 7 | - cron: '0 0 * * 1' # bi weekly on Monday 8 | 9 | env: 10 | HUSKY: 0 11 | 12 | jobs: 13 | links-checker: 14 | runs-on: ubuntu-latest 15 | name: Links Checker 16 | permissions: 17 | issues: write 18 | 19 | steps: 20 | - uses: actions/checkout@v4 21 | 22 | - name: Link Checker 23 | id: lychee 24 | uses: lycheeverse/lychee-action@v2.0.2 25 | with: 26 | args: --config ./lychee.toml --verbose --no-progress README.md 27 | fail: true 28 | 29 | - name: Create Issue From File 30 | if: env.exit_code != 0 31 | uses: peter-evans/create-issue-from-file@v5 32 | with: 33 | title: Link Checker Report 34 | content-filepath: ./lychee-out.md 35 | labels: report, automated issue 36 | -------------------------------------------------------------------------------- /.github/workflows/readme-check.yml: -------------------------------------------------------------------------------- 1 | name: Readme Check 2 | 3 | on: 4 | pull_request: 5 | paths: 6 | - 'README.md' 7 | 8 | env: 9 | HUSKY: 0 10 | 11 | jobs: 12 | readme-check: 13 | runs-on: ubuntu-latest 14 | name: Readme Check 15 | 16 | steps: 17 | - uses: actions/checkout@v4 18 | 19 | - name: Setup Node.js 20 | uses: actions/setup-node@v4 21 | with: 22 | node-version: '22' 23 | 24 | - name: Setup pnpm 25 | uses: pnpm/action-setup@v4 26 | with: 27 | version: 9 28 | 29 | - name: Install dependencies 30 | run: pnpm i 31 | 32 | - name: Check Markdown formatting 33 | run: pnpm format:check 34 | 35 | - name: Link Checker 36 | uses: lycheeverse/lychee-action@v2.0.2 37 | with: 38 | args: --config ./lychee.toml --verbose --no-progress README.md 39 | fail: true 40 | -------------------------------------------------------------------------------- /.github/workflows/stale.yml: -------------------------------------------------------------------------------- 1 | name: 'Close stale issues and PRs' 2 | 3 | on: 4 | schedule: 5 | - cron: '30 1 * * 6' 6 | workflow_dispatch: 7 | 8 | permissions: 9 | issues: write 10 | pull-requests: write 11 | 12 | env: 13 | HUSKY: 0 14 | 15 | jobs: 16 | stale: 17 | runs-on: ubuntu-latest 18 | 19 | steps: 20 | - uses: actions/stale@v8 21 | with: 22 | stale-issue-message: 'This issue has been automatically marked as stale because it has been open 40 days with no activity. Remove stale label or comment or this will be closed in 10 days. Thank you for your contributions!' 23 | stale-pr-message: 'This PR has been automatically marked as stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.' 24 | close-issue-message: 'This issue was closed because it has been stalled for 10 days with no activity. You can always contact the maintainers directly for more information.' 25 | close-pr-message: 'This PR was closed because it has been stalled for 10 days with no activity. You can always contact the maintainers directly for more information.' 26 | days-before-stale: 40 27 | days-before-pr-stale: 45 28 | days-before-close: 10 29 | exempt-issue-assignees: 'thedaviddias' 30 | exempt-pr-assignees: 'thedaviddias' 31 | exempt-all-pr-assignees: true 32 | stale-issue-label: 'stale' 33 | stale-pr-label: 'stale' 34 | exempt-pr-labels: 'keep-unstale,security,dependabot,wip,need-help' 35 | exempt-issue-labels: 'keep-unstale,security' 36 | close-issue-label: 'wontfix' 37 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | node_modules 3 | .lycheecache 4 | lychee-out.md 5 | -------------------------------------------------------------------------------- /.husky/pre-push: -------------------------------------------------------------------------------- 1 | pnpm format:fix 2 | -------------------------------------------------------------------------------- /.markdownlint.json: -------------------------------------------------------------------------------- 1 | { 2 | "MD013": false, 3 | "MD024": false, 4 | "MD033": false 5 | } 6 | -------------------------------------------------------------------------------- /.prettierrc: -------------------------------------------------------------------------------- 1 | { 2 | "trailingComma": "none", 3 | "tabWidth": 2, 4 | "semi": true, 5 | "singleQuote": true, 6 | "printWidth": 150, 7 | "endOfLine": "lf", 8 | "overrides": [ 9 | { 10 | "files": "*.md", 11 | "options": { 12 | "htmlWhitespaceSensitivity": "ignore", 13 | "proseWrap": "preserve", 14 | "embeddedLanguageFormatting": "off" 15 | } 16 | } 17 | ] 18 | } 19 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at thedaviddias@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contribute 2 | 3 | ## Introduction 4 | 5 | First, thank you for considering contributing to front-end-checklist! It's people like you that make the open source community such a great community! 😊 6 | 7 | We welcome any type of contribution, not only code. You can help with 8 | - **QA**: file bug reports, the more details you can give the better (e.g. screenshots with the console open) 9 | - **Marketing**: writing blog posts, howto's, printing stickers, ... 10 | - **Community**: presenting the project at meetups, organizing a dedicated meetup for the local community, ... 11 | - **Code**: take a look at the [open issues](https://github.com/thedaviddias/Front-End-Checklist/issues). Even if you can't write code, commenting on them, showing that you care about a given issue matters. It helps us triage them. 12 | - **Money**: we welcome financial contributions in full transparency on our [open collective](https://opencollective.com/front-end-checklist). 13 | 14 | ## Your First Contribution 15 | 16 | Working on your first Pull Request? You can learn how from this *free* series, [How to Contribute to an Open Source Project on GitHub](https://app.egghead.io/playlists/how-to-contribute-to-an-open-source-project-on-github). 17 | 18 | ## Submitting code 19 | 20 | Any code change should be submitted as a pull request. The description should explain what the code does and give steps to execute it. The pull request should also contain tests. 21 | 22 | ## Code review process 23 | 24 | The bigger the pull request, the longer it will take to review and merge. Try to break down large pull requests in smaller chunks that are easier to review and merge. 25 | It is also always helpful to have some context for your pull request. What was the purpose? Why does it matter to you? 26 | 27 | ## Financial contributions 28 | 29 | We also welcome financial contributions in full transparency on our [open collective](https://opencollective.com/front-end-checklist). 30 | Anyone can file an expense. If the expense makes sense for the development of the community, it will be "merged" in the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed. 31 | 32 | ## Questions 33 | 34 | If you have any questions, create an [issue](https://github.com/thedaviddias/Front-End-Checklist/issues) (protip: do a quick search first to see if someone else didn't ask the same question before!). 35 | You can also reach us at hello@front-end-checklist.opencollective.com. 36 | 37 | ## Credits 38 | 39 | ### Contributors 40 | 41 | Thank you to all the people who have already contributed to front-end-checklist! 42 | 43 | 44 | 45 | ### Backers 46 | 47 | Thank you to all our backers! [[Become a backer](https://opencollective.com/front-end-checklist#backer)] 48 | 49 | 50 | 51 | 52 | ### Sponsors 53 | 54 | Thank you to all our sponsors! (please ask your company to also support this open source project by [becoming a sponsor](https://opencollective.com/front-end-checklist#sponsor)) 55 | 56 | 57 | 58 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 🗂 Front-End Checklist 2 | 3 | The Front-End Checklist is an exhaustive list of all elements you need to have / to test before launching your website / 4 | HTML page to production. 5 | 6 | **Other Checklists:** 7 | 8 | - [🎮 Front-End Performance Checklist](https://github.com/thedaviddias/Front-End-Performance-Checklist#---------front-end-performance-checklist-) 9 | - [💎 Front-End Design Checklist](https://github.com/thedaviddias/Front-End-Design-Checklist#front-end-design-checklist) 10 | 11 | > [!TIP] 12 | > ⭐️ Dev-friendly UX patterns you wish you knew. 👉 [UX Patterns for Devs](https://uxpatterns.dev/en) ⭐️ 13 | 14 | ## 📚 Table of Contents 15 | 16 | - [How to use](#how-to-use) 17 | - [Head](#head) 18 | - [HTML](#html) 19 | - [Webfonts](#webfonts) 20 | - [CSS](#css) 21 | - [JavaScript](#javascript) 22 | - [Accessibility](#accessibility) 23 | 24 | ## How to use? 25 | 26 | 27 | > [!IMPORTANT] 28 | > **Disclaimer:** This checklist is based on Front-End developers' years of experience, with additions from other open-source checklists. 29 | 30 | 31 | All items in the **Front-End Checklist** are required for the majority of the projects, but some elements can be omitted 32 | or are not essential (in the case of an administration web app, you may not need RSS feed for example). We choose to use 33 | 3 levels of flexibility: 34 | 35 | - ![Low][low_img] indicates that the item is recommended but can be omitted in certain situations. 36 | - ![Medium][medium_img] indicates that the item is highly recommended but can potentially be omitted in very specific 37 | cases. However, omitting these elements can negatively impact performance or SEO. 38 | - ![High][high_img] indicates that the item cannot be omitted under any circumstances. Removing these elements may 39 | result in page malfunctions or cause accessibility and SEO issues. Testing should prioritize these elements first. 40 | 41 | Some resources possess an emoticon to help you understand which type of content / help you may find on the checklist: 42 | 43 | - 📖: documentation or article 44 | - 🛠: online tool / testing tool 45 | - 📹: media or video content 46 | 47 | ## Head 48 | 49 | 50 | > [!NOTE] 51 | > You can find [a list of everything](https://github.com/joshbuchea/HEAD) that could be found in the `` of an HTML document. 52 | 53 | 54 | ### Meta tag 55 | 56 | - [ ] **Doctype:** ![High][high_img] The Doctype is HTML5 and is at the top of all your HTML pages. 57 | 58 | 59 | ```html 60 | 61 | ``` 62 | 63 | 64 | - 📖 65 | [Determining the character encoding - HTML5 W3C](https://www.w3.org/TR/html5/syntax.html#determining-the-character-encoding) 66 | 67 | _The next 2 meta tags (Charset and Viewport) need to come first in the head._ 68 | 69 | - [ ] **Charset:** ![High][high_img] The charset (UTF-8) is declared correctly. 70 | 71 | 72 | ```html 73 | 74 | 75 | ``` 76 | 77 | 78 | - [ ] **Viewport:** ![High][high_img] The viewport is declared correctly. 79 | 80 | 81 | ```html 82 | 83 | 84 | ``` 85 | 86 | 87 | - [ ] **Title:** ![High][high_img] A title is used on all pages (SEO: Google calculates the pixel width of the characters used in the title, and it cuts off between 472 and 482 pixels. The average character limit would be around 55-characters). 88 | 89 | ```html 90 | 91 | Page Title less than 55 characters 92 | ``` 93 | 94 | - 📖 [Title - HTML - MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/title) 95 | - 🛠 [SERP Snippet Generator](https://www.sistrix.com/serp-snippet-generator/) 96 | 97 | - [ ] **Description:** ![High][high_img] A meta description is provided, it is unique and doesn't possess more than 150 98 | characters. 99 | 100 | 101 | ```html 102 | 103 | 104 | ``` 105 | 106 | 107 | - 📖 108 | [Meta Description - HTML - MDN](https://developer.mozilla.org/en-US/docs/Learn/HTML/Introduction_to_HTML/The_head_metadata_in_HTML#Adding_an_author_and_description) 109 | 110 | - [ ] **Favicons:** ![Medium][medium_img] Each favicon has been created and displays correctly. If you have only a 111 | `favicon.ico`, put it at the root of your site. Normally you won't need to use any markup. However, it's still 112 | good practice to link to it using the example below. Today, **PNG format is recommended** over `.ico` format 113 | (dimensions: 32x32px). 114 | 115 | 116 | ```html 117 | 118 | 119 | 120 | 121 | 122 | 123 | ``` 124 | 125 | 126 | - 🛠 [Favicon Generator](https://www.favicon-generator.org/) 127 | - 🛠 [RealFaviconGenerator](https://realfavicongenerator.net/) 128 | - 📖 [Favicon Cheat Sheet](https://github.com/audreyr/favicon-cheat-sheet) 129 | - 📖 [Favicons, Touch Icons, Tile Icons, etc. Which Do You Need? - CSS Tricks](https://css-tricks.com/favicon-quiz/) 130 | - 📖 [PNG favicons - caniuse](https://caniuse.com/link-icon-png) 131 | 132 | - [ ] **Apple Web App Meta:** ![Low][low_img] Apple meta-tags are present. 133 | 134 | 135 | ```html 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | ``` 146 | 147 | 148 | - 📖 [Configuring Web Applications](https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html) 149 | - 📖 [Supported Meta Tags](https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariHTMLRef/Articles/MetaTags.html) 150 | 151 | - [ ] **Windows Tiles:** ![Low][low_img] Windows tiles are present and linked. 152 | 153 | 154 | ```html 155 | 156 | 157 | ``` 158 | 159 | 160 | Minimum required xml markup for the `browserconfig.xml` file is as follows: 161 | 162 | ```xml 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | ``` 175 | 176 | 177 | - 📖 [Browser configuration schema reference](https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/dn320426(v=vs.85)) 178 | 179 | 180 | - [ ] **Canonical:** ![Medium][medium_img] Use `rel="canonical"` to avoid duplicate content. 181 | 182 | 183 | ```html 184 | 185 | 186 | ``` 187 | 188 | 189 | - 📖 190 | [Use canonical URLs - Search Console Help - Google Support](https://support.google.com/webmasters/answer/139066?hl=en) 191 | - 📖 192 | [5 common mistakes with rel=canonical - Google Webmaster Blog](https://webmasters.googleblog.com/2013/04/5-common-mistakes-with-relcanonical.html) 193 | 194 | ### HTML tags 195 | 196 | - [ ] **Language attribute:** ![High][high_img] The `lang` attribute of your website is specified and related to the 197 | language of the current page. 198 | 199 | ```html 200 | 201 | ``` 202 | 203 | - [ ] **Direction attribute:** ![Medium][medium_img] The direction of lecture is specified on the html tag (It can be 204 | used on another HTML tag). 205 | 206 | ```html 207 | 208 | 209 | 210 | ``` 211 | 212 | - 📖 [dir - HTML - MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/dir) 213 | 214 | - [ ] **Alternate language:** ![Low][low_img] The language tag of your website is specified and related to the language 215 | of the current page. 216 | 217 | 218 | ```html 219 | 220 | ``` 221 | 222 | 223 | - [ ] **x-default:** ![Low][low_img] The language tag of your website for international landing pages. 224 | 225 | ```html 226 | 227 | ``` 228 | 229 | - 📖 [x-default - Google](https://webmasters.googleblog.com/2013/04/x-default-hreflang-for-international-pages.html) 230 | 231 | - [ ] **Conditional comments:** ![Low][low_img] Conditional comments are present for IE if needed. 232 | 233 | - 📖 234 | [About conditional comments (Internet Explorer) - MSDN - Microsoft]() 235 | 236 | - [ ] **RSS feed:** ![Low][low_img] If your project is a blog or has articles, an RSS link was provided. 237 | 238 | - [ ] **CSS Critical:** ![Medium][medium_img] The CSS critical (or "above the fold") collects all the CSS used to render 239 | the visible portion of the page. It is embedded before your principal CSS call and between `` in a 240 | single line (minified). 241 | 242 | - 🛠 [Critical by Addy Osmani on GitHub](https://github.com/addyosmani/critical) automates this. 243 | 244 | - [ ] **CSS order:** ![High][high_img] All CSS files are loaded before any JavaScript files in the ``. (Except the 245 | case where sometimes JS files are loaded asynchronously on top of your page). 246 | 247 | ### Social meta 248 | 249 | Visualize and generate automatically our social meta tags with [Meta Tags](https://metatags.io/) 250 | 251 | **_Facebook OG_** and **_Twitter Cards_** are, for any website, highly recommended. The other social media tags can be 252 | considered if you target a particular presence on those and want to ensure the display. 253 | 254 | - [ ] **Facebook Open Graph:** ![Low][low_img] All Facebook Open Graph (OG) are tested and no one is missing or with 255 | false information. Images need to be at least 600 x 315 pixels, although 1200 x 630 pixels is recommended. 256 | 257 | 258 | > [!NOTE] 259 | > Using `og:image:width` and `og:image:height` will specify the image dimensions to the crawler so that it can render the image immediately without having to asynchronously download and process it. 260 | 261 | 262 | 263 | ```html 264 | 265 | 266 | 267 | 268 | 269 | 270 | 271 | 272 | 273 | 274 | ``` 275 | 276 | 277 | - 📖 [A Guide to Sharing for Webmasters](https://developers.facebook.com/docs/sharing/webmasters/) 278 | - 📖 [Best Practices - Sharing](https://developers.facebook.com/docs/sharing/best-practices/) 279 | - 🛠 Test your page with the [Facebook OG testing](https://developers.facebook.com/tools/debug/) 280 | 281 | - [ ] **Twitter Card:** ![Low][low_img] 282 | 283 | 284 | ```html 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | ``` 293 | 294 | 295 | - 📖 296 | [Getting started with cards — Twitter Developers](https://developer.twitter.com/en/docs/tweets/optimize-with-cards/guides/getting-started) 297 | - 🛠 Test your page with the [Twitter card validator](https://cards-dev.twitter.com/validator) 298 | 299 | **[⬆ back to top](#-table-of-contents)** 300 | 301 | ## HTML 302 | 303 | ### Best practices 304 | 305 | - [ ] **HTML5 Semantic Elements:** ![High][high_img] HTML5 Semantic Elements are used appropriately (header, section, 306 | footer, main...). 307 | 308 | - 📖 [HTML Reference](http://htmlreference.io/) 309 | 310 | - [ ] **Error pages:** ![High][high_img] Error 404 page and 5xx exist. Remember that the 5xx error pages need to have 311 | their CSS integrated (no external call on the current server). 312 | 313 | - [ ] **Noopener:** ![Medium][medium_img] In case you are using external links with `target="_blank"`, your link should 314 | have a `rel="noopener"` attribute to prevent tab nabbing. If you need to support older versions of Firefox, use 315 | `rel="noopener noreferrer"`. 316 | 317 | - 📖 [About rel=noopener](https://mathiasbynens.github.io/rel-noopener/) 318 | 319 | - [ ] **Clean up comments:** ![Low][low_img] Unnecessary code needs to be removed before sending the page to production. 320 | 321 | ### HTML testing 322 | 323 | - [ ] **W3C compliant:** ![High][high_img] All pages need to be tested with the W3C validator to identify possible 324 | issues in the HTML code. 325 | 326 | - 🛠 [W3C validator](https://validator.w3.org/) 327 | 328 | - [ ] **HTML Lint:** ![High][high_img] I use tools to help me analyze any issues I could have on my HTML code. 329 | 330 | - 🛠 [Dirty markup](https://www.10bestdesign.com/dirtymarkup/) 331 | 332 | - 🛠 [webhint](https://webhint.io/) 333 | 334 | - [ ] **Link checker:** ![High][high_img] There are no broken links in my page, verify that you don't have any 404 335 | error. 336 | 337 | - 🛠 [W3C Link Checker](https://validator.w3.org/checklink) 338 | 339 | - [ ] **Adblockers test:** ![Medium][medium_img] Your website shows your content correctly with adblockers enabled (You 340 | can provide a message encouraging people to disable their adblocker). 341 | 342 | - 📖 343 | [Use AdBlocking in your Dev Environment](https://andreicioara.com/use-adblocking-in-your-dev-environment-48db500d9b86) 344 | 345 | **[⬆ back to top](#-table-of-contents)** 346 | 347 | --- 348 | 349 | ## Webfonts 350 | 351 | > [!NOTE] 352 | > Using web fonts may cause Flash Of Unstyled Text/Flash Of Invisible Text - consider having fallback fonts 353 | > and/or utilizing web font loaders to control behavior. 354 | 355 | - 📖 [Google Technical considerations about webfonts](https://developers.google.com/fonts/docs/technical_considerations) 356 | 357 | - [ ] **Webfont format:** ![High][high_img] WOFF, WOFF2 and TTF are supported by all modern browsers. 358 | 359 | - 📖 [WOFF - Web Open Font Format - Caniuse](https://caniuse.com/woff). 360 | - 📖 [WOFF 2.0 - Web Open Font Format - Caniuse](https://caniuse.com/woff2). 361 | - 📖 [TTF/OTF - TrueType and OpenType font support](https://caniuse.com/ttf) 362 | - 📖 [Using @font-face - CSS-Tricks](https://css-tricks.com/snippets/css/using-font-face/) 363 | 364 | - [ ] **Webfont size:** ![High][high_img] Webfont sizes don't exceed 2 MB (all variants included). 365 | 366 | - [ ] **Webfont loader:** ![Low][low_img] Control loading behavior with a webfont loader 367 | 368 | - 🛠 [Typekit Web Font Loader](https://github.com/typekit/webfontloader) 369 | 370 | **[⬆ back to top](#-table-of-contents)** 371 | 372 | --- 373 | 374 | ## CSS 375 | 376 | > **Notes:** Take a look at [CSS guidelines](https://cssguidelin.es/) and [Sass Guidelines](https://sass-guidelin.es/) 377 | > followed by most Front-End developers. If you have a doubt about CSS properties, you can visit 378 | > [CSS Reference](http://cssreference.io/). There is also a short [Code Guide](http://codeguide.co/) for consistency. 379 | 380 | - [ ] **Responsive Web Design:** ![High][high_img] The website is using responsive web design. 381 | - [ ] **CSS Print:** ![Medium][medium_img] A print stylesheet is provided and is correct on each page. 382 | - [ ] **Preprocessors:** ![Low][low_img] Your project is using a CSS preprocessor (e.g [Sass](http://sass-lang.com/), 383 | [Less](http://lesscss.org/), [Stylus](http://stylus-lang.com/)). 384 | - [ ] **Unique ID:** ![High][high_img] If IDs are used, they are unique to a page. 385 | - [ ] **Reset CSS:** ![High][high_img] A CSS reset (reset, normalize or reboot) is used and up to date. _(If you are 386 | using a CSS Framework like Bootstrap or Foundation, a Normalize is already included into it.)_ 387 | 388 | - 📖 [Reset.css](https://meyerweb.com/eric/tools/css/reset/) 389 | - 📖 [Normalize.css](https://necolas.github.io/normalize.css/) 390 | - 📖 [Reboot](https://getbootstrap.com/docs/4.0/content/reboot/) 391 | 392 | - [ ] **JS prefix:** ![Low][low_img] All classes (or id- used in JavaScript files) begin with **js-** and are not styled 393 | into the CSS files. 394 | 395 | ```html 396 |
397 | 398 |
399 |
400 | ``` 401 | 402 | - [ ] **embedded or inline CSS:** ![High][high_img] Avoid at all cost embedding CSS in `