liveBook · Manning

Client-side rendering

As explained in Vanilla Web

Client-side rendering is the generation or updating of a web interface in the user's browser using client-side code.

Client-side rendering (CSR) puts most interface logic in browser-side JavaScript. The code uses DOM APIs to render the UI and can request content, authentication, or other services from RESTful APIs. section 2.1.4

Choose a rendering model by where the work needs to happen:

  • With server-side rendering, the server merges data into HTML on each request; with CSR, most logic runs in the browser. section 2.1.4
  • With universal rendering, the server supplies initial HTML and the client hydrates it for interactivity. section 2.1.4

Most single-page applications use CSR. WebAssembly may supplement JavaScript; HTTPS carries most API communication, with WebRTC or WebSockets available for specific purposes. section 2.1.4

How Vanilla Web covers it

How deep it goes
Defines the division of work and names DOM APIs and network requests, without walking through an implementation.
Examples
Uses single-page applications and requests for content or authentication as concrete use cases.
What it assumes
Assumes familiarity with JavaScript and browser APIs; does not teach either from zero.
What you can do after
Evaluate/understand where browser-side rendering fits among web application architectures.
How it connects
Contrasts CSR with server-side rendering and universal rendering, and links it to DOM APIs and RESTful APIs.

Also explained in

Compare how 5 books explain client-side rendering →

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.