The following article describes how Sitefinity CMS integrates with Sitefinity .NET Core Renderer to process user requests. After a user requests a page on the public domain, Sitefinity .NET Core Renderer and Sitefinity CMS work together to render the HTML of page to the user, whether it is a .NET Core page or a .NET MVC, a frontend or a backend Sitefinity page.
The following flowchart illustrates the page request handling process:
The process is the following:
The .NET Core Renderer has the .NET Core page templates and the .NET Core widgets; Sitefinity CMS has the page structure. To render a page, the Renderer uses its .NET Core widgets and templates together with Sitefinity's JSON with the structure.
When the user requests a page that is not a .NET Core page, the Renderer serves as a proxy for Sitefinity CMS, fetches the HTML from Sitefinity CMS, and serves it to the user as it is coming from Sitefinity CMS.
The Renderer does not store any resources for pages other than .NET Core pages. Therefore, the rendering of the HTML of such pages is done by Sitefinity CMS and just proxies by the Renderer to the user.
Sign up for our free beginner training. Boost your credentials through advanced courses and certification. Register for Sitefinity training and certification.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important