thedaviddias/front-end-checklist

★ 72,556Audience · developerComplexity · 1/5Setup · easy

Mindmap

mindmap
  root((repo))
    What it Does
      Pre-launch checklist
      Priority-labeled items
      Launch quality gate
    Sections
      HTML head tags
      CSS and fonts
      JavaScript
      Accessibility
      SEO and performance
    Use Cases
      Pre-launch review
      Developer onboarding
      Code review aid
    Audience
      Frontend developers
      Web teams

mindmap root((repo)) What it Does Pre-launch checklist Priority-labeled items Launch quality gate Sections HTML head tags CSS and fonts JavaScript Accessibility SEO and performance Use Cases Pre-launch review Developer onboarding Code review aid Audience Frontend developers Web teams

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Run through the checklist before launching a website to catch missing meta tags, favicon issues, and accessibility problems.

USE CASE 2

Use as onboarding material to teach new front-end developers what quality standards to check before shipping.

USE CASE 3

Review a colleague's code against the checklist to ensure nothing important was overlooked before a release.

Tech stack

HTMLCSSJavaScript

Getting it running

Difficulty · easy Time to first run · 5min

No license information is specified in the repository description.

In plain English

The Front-End Checklist is a comprehensive reference document for web developers to verify that a website is properly built before launching it to the public. The problem it solves is ensuring nothing important gets forgotten: when building a website there are dozens of technical details that are easy to overlook, like setting the correct character encoding, adding a favicon, configuring meta tags for search engines, ensuring accessibility for screen readers, and optimizing performance. This checklist compiles all of those requirements in one place. The repository is organized into sections covering the HTML document head (meta tags, favicons, canonical links), HTML structure, web fonts, CSS, JavaScript, and accessibility. Each item is labeled with one of three priority levels: high (must not be omitted or the page may break or fail SEO), medium (highly recommended but occasionally skippable), or low (best practice but can be omitted in certain contexts). The items are accompanied by explanations, links to relevant documentation, and links to online tools for testing each requirement. This makes it both a checklist to run through before launch and a learning resource for understanding why each item matters. You would use this repository as a pre-launch quality checklist when shipping a website, as onboarding material for new front-end developers on your team, or as a reference when reviewing someone else's code. It is particularly useful for developers who are building sites without a dedicated QA team. The repository itself is not software, it is documentation written in Markdown and HTML. There is no runtime or framework to install. The companion website and additional checklists (performance and design) are linked from the README.

Copy-paste prompts

Prompt 1

Based on the front-end-checklist high-priority items, audit this HTML page for me and list any missing meta tags, Open Graph tags, or favicon configuration.

Prompt 2

I'm about to launch my website. Walk me through only the must-have items from the front-end-checklist, the ones where skipping them will break SEO or functionality.

Prompt 3

My website scores poorly on accessibility. Which items from the front-end-checklist relate to screen reader support and what do I need to add to my HTML?

Prompt 4

Use the front-end-checklist performance section to identify what I should optimize on my site before launch, focus on items that affect page load speed.

Open on GitHub → Explain another repo

← thedaviddias on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.