liveBook · Manning

Vanilla web

As explained in Vanilla Web

An approach to building websites and web applications with core web technologies and browser APIs without a framework defining the application architecture.

Vanilla web builds websites and web applications with HTML, CSS, JavaScript, and browser APIs, without letting a framework define the architecture or development flow. It is a requirements-first choice, not a rule against libraries: add a tool when it solves a specific problem. section 1.2 section 1.1

Start with the platform, then add only what the application needs:

  • Use semantic HTML for structure and content, modern CSS for presentation, and JavaScript with the DOM, events, and browser APIs for behavior. section 1.2
  • Keep responsibilities and project conventions explicit. Modular code, reusable components, tests, and lightweight tooling are compatible with vanilla web; a build step is not required merely to start or deploy. section 1.1 section 2.5 section 2.5.1
  • Treat advanced capabilities as requirements, not reasons to adopt a framework automatically. Browser-based apps can be installable, offline-capable, data-driven, and hardware-integrated. section 2.4

Good candidates include content sites, landing pages, long-lived applications with infrequent changes, and performance-critical interfaces. Fewer dependencies can simplify auditing and maintenance, but direct DOM work is not automatically fast or secure: performance still depends on sound design, and the team must enforce its own organization and guidelines. Large teams, complex state or rendering, and a need for ready-made routing or server-side rendering may make a framework the better choice. section 1.5 section 2.3.1 section 2.5.1 section 1.8

Use a framework only where it earns its place

A mostly vanilla site can mount a React component in one section without rewriting the rest. Similarly, GitHub uses custom elements for features such as timestamps and dialogs while also using libraries in selected parts. The boundary is the feature’s need, not an all-or-nothing stack decision. section 2.5.2 section 1.5.1

Judge the result by user-facing goals—usability, accessibility, performance, and maintainability—rather than by how few tools it uses. Native APIs provide control, not an imposed architecture; choose conventions deliberately, measure performance, and introduce a library when its benefits outweigh its added dependency and maintenance costs. section 1.4 section 1.8 section 2.3.1

How Vanilla Web covers it

How deep it goes
Defines the approach, identifies native building blocks and project candidates, and examines tooling and trade-offs without prescribing one application architecture.
Examples
Uses landing pages and content sites as candidates, and GitHub’s custom elements and selective library use as a large-scale example.
What it assumes
Assumes solid HTML, CSS, and JavaScript fundamentals rather than prior experience with a particular framework.
What you can do after
Build it from scratch with web standards, adding libraries selectively and taking responsibility for architecture and performance.
How it connects
Connects semantic HTML, modern CSS, JavaScript, DOM APIs, Web Components, web performance, and progressive enhancement.

Also explained in

Compare how 2 books explain vanilla web →

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.