liveBook · Manning

Chapter 1: Hello Vanilla Web

What you will learn in chapter 1 of Vanilla Web

The introduction argues for choosing web tools based on project needs, explains the appeal of working directly with the browser, and distinguishes libraries from frameworks.

After this chapter you will be able to

Section by section

Introduction

The introduction argues for choosing web tools based on project needs, explains the appeal of working directly with the browser, and distinguishes libraries from frameworks.

Key terms: technology stack, requirements, libraries, frameworks, dependencies, Vanilla Web, web platform, browser, hidden abstractions, technical autonomy

1.1 What Vanilla Web is not

The section dispels myths about Vanilla Web by presenting it as a modern, tool-compatible approach that can support efficient development and production apps.

Key terms: Vanilla Web, web platform, HTML, CSS, JavaScript, framework, modular code, design patterns, reusable components, architecture

1.2 What Vanilla Web is

Defines Vanilla Web as building web experiences directly with web standards, identifies its main building blocks, and clarifies that it does not require rejecting useful tools.

Key terms: Vanilla Web, core web technologies, DOM, browser features, tooling, abstraction layers, micro-libraries, pre-processors, Semantic HTML, Vanilla CSS

1.3 How it works

This section maps the layers of a typical Vanilla Web project and identifies the book’s focus on the frontend.

Key terms: frontend development, Semantic HTML, CSS, JavaScript, Browser APIs, WebAssembly, Network protocols, Web Server, Backend development, Additional Services

1.4 Remembering our goals

This section argues for choosing web tools by user and product outcomes rather than by novelty, and explains why simple Vanilla Web projects may suit AI-assisted development.

Key terms: goals, conversion rates, usability, accessibility, performance, tool set, Developer Experience (DX), Vanilla Web, Web platform, AI coding agents

1.5 Using Vanilla Web

The section explains where Vanilla Web is a good fit while distinguishing technical feasibility from project suitability and acknowledging minimal use of helper libraries.

Key terms: Vanilla Web, Web platform, frameworks, libraries, content-oriented websites, landing pages, Core Web Vitals, performance-critical applications, DOM updates, vanilla-ish

1.5.1 Mixing Vanilla with libraries

This section explains that Vanilla Web code and frameworks can coexist in one application, and illustrates the approach with a small React-related fix and GitHub’s frontend.

Key terms: Vanilla Web, framework, browser APIs, custom elements, web components, web standards

1.6 Enhancing your skills

This section explains how working directly with web technologies strengthens developers’ skills, makes application behavior easier to understand, and offers a deliberate alternative to using a framework.

Key terms: Vanilla Web, DOM, events, state, frameworks, Vanilla JS/CSS, markup, call stack, real DOM, browser inspectors

1.7 Characteristics

This section contrasts Vanilla Web with large libraries and frameworks by listing its main characteristics and noting a developer-experience trade-off.

Key terms: Vanilla Web, Developer Experience (DX), web standards, third-party dependencies

1.8 Challenges

This section explains the convenience-versus-control trade-off of Vanilla Web and identifies situations where its lack of built-in solutions can be a challenge.

Key terms: Vanilla Web, short-term comforts, pre-built solutions, framework, structured architecture, complex DOM diffing, server-side rendering, strong typing

1.9 Summary

Where this is used later

Concepts explained in this chapter

Chapter 2: Understanding the web platform →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.