Builder supports Server-Side Rendering (SSR) and Static Site Generation (SSG) out-of-the-box for all components.
To leverage SSR and SSG with Builder, you must be using a framework that supports these features.
Tip: The Angular SDK does not support SSR and SSG with custom components. For more information, read Angular workarounds for SSR and SSG custom components at the end of this document.
Angular's default is client-side rendering, where components and pages are rendered in the browser. This means that Angular's architecture is optimized for dynamic and interactive applications that rely heavily on client-side JavaScript execution.
On the other hand, SSR and SSG require the generation of fully rendered HTML on the server before it's sent to the client. This approach is critical for SEO, performance, and usability, especially for content-rich pages.
If you need to use SSR with your Angular custom components and Builder, there are a couple of workarounds worth considering:
- Using a prerendering tool: Consider leveraging a prerendering tool like prerender.io. This can help generate pre-rendered versions of your custom components so search engines and users receive fully rendered content.
- Using Symbols for your components: To facilitate server-side rendering and static site generation, consider building out your custom components as Symbols. This approach helps with smoother integration with Builder's rendering process.
For more context on Angular and SSR, visit Angular's document SSR with Angular Universal.
For more information on server-side data, refer to the getAsyncProps README.
