Web Technologies reference data

Standards, protocols, and APIs for web development.

  • 13 datasets
  • JSON · YAML · TOON
  • CC0 — public domain

Topic guide

What Web Technologies covers

Web-technology reference data covers the platform that browsers and servers share: the HTTP protocol and its evolution, the request and response headers that carry control information, the browser APIs that give pages access to storage, networking and hardware, the CSS layout systems that arrange content, and the JavaScript frameworks that structure applications. Standards come from several bodies (IETF for protocols, WHATWG and W3C for the platform) and support arrives browser by browser, so almost every entry needs the qualifier 'supported in which browsers, since which version'. Behavior also differs between secure contexts (HTTPS) and plain pages, which gate many APIs.

Key ideas

Web standard
A specification maintained by a body such as the IETF, W3C or WHATWG. Browsers implement them at different times and with different completeness.
Secure context
A page served over HTTPS (or localhost). Many powerful APIs, such as service workers and geolocation, are available only there.
Progressive enhancement
Building a page that works with basic features and adds capabilities where the browser supports them.
Same-origin policy
A browser rule that restricts how a document from one origin may interact with resources from another; CORS relaxes it deliberately.
Request and response headers
Key-value metadata that accompanies every HTTP message: content type, caching, authentication, cookies and security policy.
Flexbox and Grid
CSS layout systems: Flexbox arranges items along one axis, Grid in two dimensions.
Framework vs library
A library is called by your code; a framework calls your code and imposes structure. React is usually described as a library, Angular as a framework.

Common pitfalls

  • Assuming a feature works everywhere because it works in one browser. Check compatibility data and have a fallback.
  • Setting security headers (CSP, HSTS) without testing; a restrictive policy can break the site or a permissive one gives false comfort.
  • Choosing a framework by popularity alone instead of by the team's skills and the app's needs.
  • Treating localStorage as secure storage. Any script on the page can read it.

Using it from an agent

  • Give the specification or MDN reference for a feature and state the support level (baseline, experimental).
  • Recommend security headers as a set (HSTS, CSP, X-Content-Type-Options, Referrer-Policy) and explain each one's purpose.
  • When comparing frameworks, state the criteria (learning curve, ecosystem, performance model) and avoid declaring a winner.

Start with: HTTP Request Headers · CSS Layout Systems Reference

Datasets in Web Technologies

Fetch this category

One request returns the category with all of its dataset summaries. Append ?format=yaml or ?format=toon for the other encodings.

GET https://yjtoon.yunusemrevurgun.com/api/category/web-technologies?format=json

Search the library

Search by a topic, title, or keyword.

Start with a collection

Browse all 205 datasets