liveBook · Manning

Web standards

As explained in Vanilla Web

A public technical specification defining interoperable web languages, APIs, protocols, or platform behavior.

Web standards are public specifications for the languages, APIs, protocols, and behavior that make websites work across browsers. They provide a foundation for an application without requiring a framework to define its architecture. The practical choice is not “standards or tools”: use browser capabilities directly where they meet the requirement, and add tools or small libraries when they help. section 1.2 section 1.9

A standards-based application can assign each concern to a native building block:

  • Use semantic HTML for structure and content, including Custom Elements or Web Components where appropriate. section 1.2
  • Use CSS for layout, themes, animation, and suitable UI components; use JavaScript, the DOM, events, and browser APIs for application logic and interaction. section 1.2
  • Communicate with a backend through HTTP and other standard protocols rather than requiring a particular server stack. section 1.2 section 1.9

Standards are developed through open discussion, testing, and refinement involving organizations such as the W3C, WHATWG, and IETF, alongside browser vendors and other contributors. That process favors interoperability and backward compatibility. It can reduce the upgrade pressure associated with versioned frameworks, but it does not remove the need to make architectural choices, set project guidelines, or consider compatibility and accessibility. section 2.1 section 1.9 section 2.0

Longevity as a design consideration

A website created in 1997 can still render in contemporary browsers and on newer devices. That longevity illustrates the value of a carefully evolving platform; it is a reason to consider standards when an application may outlive today's framework releases, not a reason to reject every framework. section 2.1

How Vanilla Web covers it

How deep it goes
Defines the role of standards, identifies their platform components and development process, and stops short of an individual specification's internals.
Examples
Uses semantic page structure, native UI features, HTTP endpoints, and a 1997 website still rendered by modern browsers.
What you can do after
Build it from scratch with HTML, CSS, JavaScript, browser APIs, and HTTP, adding small libraries when requirements warrant them.
How it connects
Connects semantic HTML, CSS, JavaScript, browser APIs, Web Components, HTTP, interoperability, and backward compatibility.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vanilla Web. The section links point to the parts of the book it draws on.