Browser compatibility sits behind every decision, which is why MDN’s support tables matter more than tutorials. When choosing tools, start from the need: for most content sites a static site generator (Hugo, Docusaurus) is less work than a single-page app framework. CSS and UI kits have their own heading.
69 links
Code snippets short enough to read and understand in thirty seconds, for JavaScript, Python, React and CSS. Against Stack Overflow, each one is explained, tested and filed by topic — you browse it rather than search it.
A list of components, tools and tutorials for the Angular application framework. Unlike the official docs it gathers community libraries and real examples.
A list of plugins and configs for ESLint, the JavaScript linter. Unlike the ESLint docs, it gathers community-shared configs and plugins specific to frameworks such as React and Vue.
A list of libraries for geographic information systems (maps) in the browser. Unlike general mapping-API lists, it focuses on libraries that run in the browser rather than on a server — rendering, data conversion, spatial analysis.
A list of HTML5 APIs — Canvas, WebSocket, storage — plus tools and resources. Unlike general web lists, it focuses only on the browser APIs that came with the HTML5 standard.
A resource list for building a good mobile web experience — touch events, performance, offline. Unlike native-app lists, it targets mobile sites running in the browser.
A list of tips, tools and resources for npm, the Node package manager. Unlike the npm docs, it gathers the tools around it — package search sites, publishing helpers, CLI add-ons.
A resource list for using npm scripts as a task runner. Unlike task runners such as Gulp or Grunt, it teaches making do with package.json scripts and no extra dependency.
A list of ponyfill libraries that add native behaviour without overriding it. Unlike polyfills they never patch globals: you import the feature as a separate module.
A list of components, tools and examples for Preact, the 3 KB lightweight React alternative. Unlike React lists, it collects only libraries that work with Preact and keep its small size.
A list of libraries, tools and learning resources for the React ecosystem. Unlike the official docs, it gathers the surrounding ecosystem — state management, routing, component libraries, testing — in one list.
A list of libraries, examples and articles for React Hooks. Unlike general React lists, it gathers only hook-based patterns and custom-hook packages, not class components.
A resource list for Standard, the zero-config JS style guide and linter. Unlike configuring ESLint by hand, the rules are fixed and not up for debate; the list gathers editor plugins and compatible tools.
A list of components and tools for Svelte and SvelteKit. Unlike React-heavy lists it shows the ecosystem specific to this compile-time framework.
A resource list for building cross-browser add-ons (WebExtensions). Unlike single-browser docs it focuses on the common API that works across Chrome, Firefox and Safari.
A resource list for WebXR, enabling virtual/augmented reality in the browser. Unlike native XR SDKs, these experiences open in a browser with nothing to install; the list gathers frameworks, samples and tools.
A resource list for WP-CLI, managing WordPress from the command line. Unlike the admin dashboard it offers bulk, scriptable operations: updating plugins on a hundred sites is one command.
A guide of concrete tips for improving web performance. Unlike automated audits such as Lighthouse, the advice is hand-written by experts with its reasoning; part of it dates from the HTTP/1 era.
A table showing which email client supports an HTML/CSS feature. Unlike the web’s Can I use it looks at the quirky, limited support of email clients.
Up-to-date one-line answers to everyday JavaScript questions like "how do I reverse an array". The difference from Stack Overflow is that the answer is not from 2012 — they use modern syntax; but the newest snippets date from February 2024, so upkeep is slow.
Ready-to-copy HTML, CSS and JavaScript code examples. Unlike documentation, it gives small working snippets rather than explanations.
Meta’s React-based documentation-site generator, with versioning and translation built in. Unlike general static generators it is docs-first: it ships ready-made pieces like version archives and i18n aimed specifically at software documentation.
A build of Firefox for web developers, with advanced debugging tools built in. Unlike Chrome DevTools, its CSS Grid and Flexbox inspectors and its fonts panel are notably strong.
A checklist of items to verify before launching a web page across HTML, CSS, JS, accessibility, performance and SEO, with priority labels. Unlike general guides it is a tickable, prioritised checklist.
A newsletter rounding up frontend news, articles and tools weekly. Unlike scattered following it gives a single, filtered digest.
A practice platform that gives realistic design files and asks you to turn them into code. Unlike random projects it comes with professional designs and community feedback.
Every HTML element and attribute with a visual example, scannable on one page. It lacks MDN’s depth but answers “what did this tag do again” faster.
Addy Osmani’s free online book on JavaScript design patterns. Unlike general design-pattern books it focuses on JavaScript-specific ones such as module, observer and prototype; this is the older edition, with current patterns at patterns.dev.
Measures Google Maps ranking across a grid of locations, showing how the same query shifts block by block. Unlike general SEO tools, it measures exactly their blind spot: local ranking.
The most widely used reference for the web platform. Unlike summary sites such as W3Schools, every page carries a browser-compatibility table — where you check whether a feature works in Safari before shipping it.
Mozilla's recommended security headers and settings for websites: CSP, HSTS, cookie flags, CORS, SRI. It gives a priority and an example configuration for each, making it more actionable than general security articles.
A form-driven generator that builds a ready NGINX config from domain, PHP/Node, security and performance options. Compared with copying sample configs, it adds best-practice settings (TLS, headers, gzip) automatically.
An Obsidian plugin that publishes notes straight into a live digital garden. Unlike generators such as Quartz it needs no build step: you publish from inside a note with one button, with no separate build pipeline to set up.
A free resource explaining design and rendering patterns for modern web apps with examples. Unlike classic design-pattern books, it also covers rendering patterns — SSR, static generation, hydration, islands.
An open-source map stack that serves a world basemap as a single PMTiles file; the file sits on plain storage such as S3 and the browser reads only the parts it needs through HTTP range requests. Unlike hosted map services such as Mapbox there is no tile server and no per-use fee.
A library managing React forms with minimal re-renders and built-in validation. Unlike controlled components it keeps performance high and simplifies the code.
A technical SEO checklist covering heading structure, schema markup and page speed in actionable terms. Unlike marketing-led Turkish SEO articles, it is written as concrete, checkable items.
The object, filter and tag reference for Shopify’s theme language. Unlike generic Liquid docs it covers Shopify-specific objects — where you find which data is reachable from which template.
In-depth articles, books and practical guides on web design and development. Unlike short blog posts, it publishes long, editor-reviewed articles.
A library replacing the browser’s ugly alert box with pretty, customisable modals. Unlike the built-in alert it supports styling, input fields and promises.
A low-code platform that turns a visual interface design into clean React, Vue or HTML. Against Webflow the output is exportable, readable component code — you can take the design over and keep building by hand.
A community-run accessibility site with a plain checklist based on WCAG, articles and lists of tools and resources. Unlike the W3C quick reference it states the criteria as items a developer can follow rather than in standards language.
Works the language front to back without skipping the hard parts: prototype chain, event loop, promises. Unlike MDN it is a tutorial, not a reference; the two complement each other.
Checks HTML against the spec, surfacing unclosed tags and invalid nesting that browsers quietly repair. Unlike linters such as HTMLHint it checks conformance, not style; a share of accessibility problems begins right there.
WebAIM’s accessibility evaluation tool; given an address, or through its browser extension, it overlays errors, alerts and structural information as icons on the page. Unlike scanners that produce a report it shows each problem in place on the page; the extension also checks pages behind a login, locally.
The W3C’s “How to Meet WCAG” page: every success criterion, its level (A, AA, AAA), the techniques that satisfy it and the common failures, filterable by level and topic. Unlike reading the standard itself it takes you from a criterion straight to a technique you can apply.
Microsoft’s 24-lesson curriculum with a quiz before and after each lesson and a project at the end. Unlike scattered tutorials it has that structure, which lets you measure progress when studying alone.
A YouTube channel explaining web development from basics to advanced, simply. Unlike long courses, most videos wrap up a single concept quickly.
The official site of the WebAssembly standard: the specifications, an introduction to the concepts and a feature table showing which proposal is supported in which browser and runtime. Unlike MDN’s WebAssembly pages it looks from the standard and the runtimes rather than from the JavaScript side.
An open-source linter that scans a site for accessibility, speed, security and compatibility problems and explains each rule; it runs as an online scan, a CLI and a VS Code extension. Unlike Lighthouse it documents every rule in detail and is configurable.
The open-source blog and CMS that runs a large share of the web; this is the software you install yourself, not the WordPress.com hosting service. Unlike static-site generators it has an admin panel and a huge plugin ecosystem; the price is ongoing maintenance and security updates.