Resources

A short, opinionated list of references worth bookmarking. These are the primary sources the articles on this site lean on, and the ones worth checking before trusting a tutorial or a forum answer. The list is deliberately small: a handful of high-quality, well-maintained references beats a long bookmark folder you never open.

The split below is simple. The first group is for everyday answers, the second is for when you need to know how something is actually specified to behave, and the third points back to the relevant material on this site. Every external link opens in a new tab.

References

Start here for day-to-day questions about the language, the DOM, and browser APIs.

• MDN Web Docs — the reference for the language, the DOM, and browser APIs.
• web.dev — practical guidance on performance, accessibility, and modern platform features.
• Can I use — browser support tables for web platform features.

Standards & specifications

When behaviour is surprising and you need the definitive answer, the specs are the source of truth that the references above are built on.

• ECMAScript Language Specification — the formal definition of JavaScript.
• TC39 proposals — features moving through the standards process.
• WHATWG HTML & DOM standards — how the DOM and HTML actually behave.

Playgrounds & experimentation

Reading about JavaScript only goes so far; the fastest way to understand a feature is to run it. For quick checks, the browser console is always one keystroke away and needs no setup. For something you want to save or share, a scratchpad environment is handy.

• MDN Playground — a no-setup scratchpad on the same site as the reference docs.
• Can I use — before relying on a newer feature, confirm it is supported where your users are.

Whichever you reach for, the habit matters more than the tool: when a claim about the language surprises you, reproduce it in isolation before building on it. A two-line experiment settles most arguments faster than a search does.

Evaluating what you read

The web is full of JavaScript advice, and a lot of it is out of date the day it is published. A few quick checks save a lot of wasted effort. Look at the date: a technique from 2015 may have a one-line modern replacement. Prefer the primary source over a summary of it; when a blog post and MDN disagree, MDN is almost always right. Be wary of any answer that adds a library to solve something the platform now does natively, and be just as wary of clever one-liners that trade readability for brevity.

Above all, run it. The fastest way to confirm a claim about JavaScript is to paste it into the browser console and watch what actually happens. The references below are reliable precisely because they are tested against the real implementations rather than against someone’s memory of them.

On this site

• Guides — ordered reading tracks through the articles.
• Cheatsheets — quick reference for arrays, async, fetch, and devtools.
• Tools — private, in-browser developer utilities.
• Glossary — plain definitions of common terms.

If you only keep three of these, make them MDN for reference, Can I use for support questions, and the ECMAScript spec for the rare moment you need to settle an argument about how the language really works.

Why the list is short

It would be easy to turn this into a wall of links, but a reference list is only useful if you actually trust every entry on it. Each source here is included because it is accurate, actively maintained, and primary rather than a rehash of something else. A long list of mediocre links is worse than a short list of excellent ones, because it pushes the burden of judging quality back onto you at exactly the moment you are trying to get an answer.

That is also why there are no video courses, paid platforms, or framework-specific tutorials here. Those have their place, but they date quickly and their quality varies enormously. The references above change slowly, document the platform itself rather than one library’s take on it, and will still be correct long after this year’s popular framework has been replaced. When something genuinely belongs on this list, it gets added; until then, the list stays short on purpose.