Server-side rendering
Rendering a UI on the server before it reaches the browser — first paint without waiting for a client framework to boot, and markup a crawler can read.
Overview
CAP ships no UI technology of its own. Its Node.js server mounts the project's app folder as static content and serves the CDS services for a client to read; what turns that into a screen is whatever framework the browser loads.
Not covered: Rendering is left to the client. Neither capire's UI guide nor the documented bootstrap of the built-in server describes producing markup for a request, so a first response that already carries the data is not something the core answers.
ui5-cap-serverside-rendering-pluginui5-cap-serverside-rendering-pluginA CAP plugin that fills UI5 views and fragments with entity data on the server through Handlebars and streams them as XML, and renders a Vue app to HTML on a route of its own.independent, cap substitutes entity data into a UI5 XML view or fragment on the CAP server through Handlebars and serves it as that entity's media content; a route of its own renders a Vue app to HTML.
No core answer is documented.
Not covered: SAPUI5's own documentation says the framework is not involved in creating the HTML page sent to the client, so rendering happens entirely in the browser and the first paint is left to whatever technology sits in front of it.
Unmapped on the ui5 door: ui5-cap-serverside-rendering-pluginui5-cap-serverside-rendering-pluginA CAP plugin that fills UI5 views and fragments with entity data on the server through Handlebars and streams them as XML, and renders a Vue app to HTML on a route of its own.independent, cap is catalogued under the cap ecosystem, so it answers this capability's cap assessment and is not a ui5-door artifact.
No artifact is documented here yet.
Artifacts
Details
Coverage
For your agent
- Ref
capability:server-side-rendering- JSON
- /capabilities/server-side-rendering.json
- MCP
- Connecting an agent