In complex business scenarios, page rendering is no longer a binary choice between SSR and CSR, but a systemic design problem concerning experience, stability, and engineering governance.
View the page-oriented BFF as a server-side pipeline. Requests first pass through the static and module layer, then through site-wide middleware, hit a specific page for data aggregation, and finally the rendering template decides how to output HTML, stream, or CSR fallback.
Many teams go through a seemingly natural phase: build a React component library with buttons, carousels, etc., then expect page building to be solved as components increase.
View the page-oriented BFF as a server-side pipeline. Requests first pass through the static and module layer, then through site-wide middleware, hit a specific page for data aggregation, and finally the rendering template decides how to output HTML, stream, or CSR fallback.
This article documents a plugin-based refactoring in our BFF page system: pages only declare a single `config.toml`, while page discovery, template matching, virtual entry generation, route mounting, and hot reload during development are all handled by Vite plugins.
In complex business scenarios, page rendering is no longer a binary choice between SSR and CSR, but a systemic design problem concerning experience, stability, and engineering governance.
This project's core value lies in turning a tedious visual translation task into a clear layout tree reconstruction algorithm problem. The following is a detailed breakdown of the implementation.
Treat merchant differences not as scattered conditional branches, but as objects that need governance.
In MultipleSite, what truly stabilizes the entire chain is not React components or a backend page, but a protocol consumed by multiple subsystems.