liveBook · Manning

Web platform

As explained in Vanilla Web

The collection of browser-provided standards and technologies, including HTML, CSS, and JavaScript, that support web application development.

A web application does not need a framework as its starting point. The web platform supplies the browser runtime and the standards that applications use: HTML, CSS, JavaScript, protocols, and browser APIs. Libraries and frameworks add abstractions over those capabilities; use one when it solves a project requirement, not merely because a template includes it. section 1.1 section 1.5 section 2.6

Choose the platform features that fit the application:

  • Choose navigation and rendering independently: an MPA, SPA, SSR, CSR, SSG, or hybrid architecture need not be dictated by a framework. section 2.6
  • Use native capabilities where they meet the need: browser APIs provide storage, sensors, performance metrics, and hardware access; HTTPS, WebSockets, and WebRTC cover communication needs. section 2.6
  • Check browser support with Baseline before relying on a feature across browsers. Add build tools or a package manager only when needed. section 2.6

A content-focused site

For a blog, wiki, or landing page, begin with HTML, CSS, and only the JavaScript its interactions require. This avoids maintaining a complex client-side architecture where the requirements do not call for one. A small helper library can still be a deliberate choice; a platform-first approach is not a ban on dependencies. section 1.5 section 1.1

The platform also supports dynamic, installable, offline-capable, and hardware-integrated applications. JavaScript and browser APIs can extend a UI beyond HTML and CSS; service workers, Cache Storage, and a manifest are options for offline and installable behavior. Keep those additions tied to requirements, while weighing performance, accessibility, security, and maintenance against the convenience of extra abstractions. section 2.6 section 3.8 section 14.0 section 1.0

How Vanilla Web covers it

How deep it goes
Surveys rendering engines, protocols, browser APIs, architectures, and compatibility guidance without detailing their implementations.
Examples
Uses blogs, wikis, landing pages, and performance-critical applications to illustrate platform-first choices.
What it assumes
Starts with browsers, rendering engines, protocols, and APIs rather than requiring commitment to a framework.
What you can do after
Evaluate/understand when native platform capabilities suffice and when a library or framework addresses a specific requirement.
How it connects
Connects HTML, CSS, JavaScript, browser APIs, progressive web apps, application architecture, and Baseline compatibility guidance.

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.