Server-side rendering
A web-rendering technique in which a server generates a user interface’s markup or other rendered representation before delivering it to a client.
Modern Angular
Server-side rendering is the generation of an application's initial HTML on a server before it is delivered to the browser.
- How it is used
- Improves public Angular pages whose initial-load performance and SEO matter more than internal enterprise-tool startup time.
- How deep it goes
- Walks through CLI creation, generated server architecture, local verification, hydration, and deployment constraints without deeply customizing the server.
- Examples
- Uses an HRMS promotional page, rendered title binding, clickable title-change button, generated configuration, and inspected response HTML.
- What you can do after
- Build it from scratch with Angular CLI, verify server-rendered HTML locally, and deploy dynamic routes to Node.js-capable hosting.
React in Depth
Server-side rendering is the process of producing application interface output on a server before sending it to the client.
- How it is used
- Uses server-generated, data-filled HTML to improve the initial page display of React websites.
- How deep it goes
- Explains first-load and subsequent-navigation data flow, then shows route-data implementations; leaves framework details beyond the examples aside.
- Examples
- Compares an empty Vite root with server-generated HTML and implements a parameterized shop-category route in Next.js and Remix.
- What you can do after
- Apply it via Next.js getServerSideProps or a Remix loader to deliver route data in initial HTML while checking hydration constraints.
ASP.NET Core in Action, 3e
Server-side rendering is the process of generating HTML on the server before sending it to a client.
- How it is used
- Generates browser-facing HTML pages for traditional applications, while allowing APIs and other paradigms to coexist.
- How deep it goes
- Explains request, form, and markup generation, including Tag Helpers and CSRF protection, but stops short of rendering internals.
- Examples
- Uses Razor Pages templates, browser URLs, submitted forms, generated HTML, and Tag Helpers for labels, inputs, selections, and validation.
- What you can do after
- Builds browser-facing Razor Pages applications and selects them appropriately against APIs or client-side frameworks.
Read how ASP.NET Core in Action, 3e explains server-side rendering →
React Quickly, Second Edition
Server-side rendering is the generation of user-interface markup on a server before it is delivered to a client.
- How it is used
- Positions server-side rendering as a way to serve pre-rendered React HTML while retaining client-side interactivity.
- How deep it goes
- Defines the server-to-browser rendering flow and contrasts frameworks, but does not walk through an implementation.
- Examples
- Illustrates a server-rendered list with browser-based filtering and sorting, and names Next.js and Remix.
- What you can do after
- Evaluate/understand it as an option when choosing between server-rendered, static, and client-side React websites.
Read how React Quickly, Second Edition explains server-side rendering →
Rust Servers, Services, and Apps
Server-side rendering is a web application pattern in which a server generates a fully rendered web page and sends it to a browser.
- How it is used
- Builds a Rust web frontend for registration, login, data views, and CRUD operations through web forms.
- How deep it goes
- Traces templates, handlers, forms, and rendered responses; leaves SPA development for later and excludes PWAs.
- Examples
- Uses bank home and account pages, plus tutor course listings and details, to illustrate static and dynamic content.
- What you can do after
- Apply Actix Web and Tera to render dynamic pages, process form submissions, and display data-backed lists.
Read how Rust Servers, Services, and Apps explains server-side rendering →
Build a Frontend Web Framework (From Scratch)
A rendering approach in which the server generates the HTML for an application before sending it to the browser.
- How it is used
- Uses a backend to generate route-specific HTML before the browser handles interactions and state-driven updates.
- How deep it goes
- Defines the request, component, rendering, and hydration pipeline but stops short of implementation details.
- Examples
- Uses URL requests, route-selected components, loaded database data, generated HTML, and hydration flow diagrams as examples.
- What you can do after
- Understand how an SSR request becomes interactive browser markup through server rendering and hydration.
Read how Build a Frontend Web Framework (From Scratch) explains server-side rendering →
Pro Angular 16
Server-side rendering is the technique of executing an application on a server to generate HTML that is sent to a browser before client-side code is ready.
- How it is used
- Improves application delivery by displaying useful HTML while browser JavaScript downloads.
- How deep it goes
- Explains server execution, hydration, navigation changes, URL handling, commands, and testing, while deferring unsupported Angular features.
- Examples
- Uses SportsStore URL configuration, Angular Universal installation, anchor navigation, disabled controls, and JavaScript-disabled browser testing.
- What you can do after
- Operate/configure Angular Universal SSR, adapt browser-dependent code, test HTML-only output, and distinguish SSR from prerendering.
Django in Action
Server-side rendering is the composition of a web page's HTML on the server before it is sent to a browser.
- How it is used
- Explains how Django turns a browser URL visit into completed HTML returned from a server.
- How deep it goes
- Defines the server-browser boundary and request flow, but stops short of implementation code or deployment details.
- Examples
- Uses a Django view selected by a URL and a template engine that combines reusable HTML pieces into a browser response.
- What you can do after
- Apply it via Django by connecting a URL to a view that renders a template and returns HTML to the browser.
Related concepts
- prerenderingalternative to · Prerendering is the generation of web-page HTML before it is requested or served, typically as prebuilt files.
- single-page applicationcontrasts with · A single-page application is a web application that loads a document and dynamically updates its content or interface without full-page navigation for most interactions.
- HTMLproduces · HTML (HyperText Markup Language) is the standard markup language for structuring content and elements in web documents.
- client-side renderingcontrasts with · Client-side rendering is the generation or updating of a web interface in a user's browser by code executed there.
- template engineuses · A template engine is software that combines reusable templates with data and rules to generate rendered output such as text, documents, or user-interface views.
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.