Redeon.SuperSiteEngineCore.Web.Eltheon.Core.Features.Renderer.Demo
Renderer.Demo is a small DemoCMS consumer for the Eltheon Renderer foundation.
Scope
- Public demo route:
/demo-cms/view/{**path} - UserArea management pages under
/User/RendererDemo - JSON persistence in the private
renderer-demoStorage space - Demo components: info panel, warning panel, table of contents, latest pages
- Public rendering is served by an RCL Razor Page that uses the template main layout.
- Preview and public rendering use the same
DemoCmsRouteResolver+IRenderServicepipeline. - Page content is expanded into the selected template before Renderer component parsing, so component markup in page content is rendered.
- Editors expose registered renderer engines and stored DemoCMS templates as select lists.
- Page and template changes publish neutral DemoCMS domain events when an
IEventBusis registered. - New DemoCMS pages use
elyraby default. elyrais not an alias. It composes Fluid/Liquid expressions, renderer components, Markdown conversion and final HTML sanitizing.fluidis for pure Fluid/HTML test pages.markdownis for pure Markdown test pages.plaintextis for plain text output.- Component syntax remains
[[component:...]].
Renderer.Demo is not a product CMS. It has no database persistence, media library, workflow, visual page builder or production publishing model.
When Eltheon Storage is available, pages, templates, and seed content are written only to the renderer-demo space. A completely empty space may read the legacy DataAssets/demosites content until it is migrated. As soon as the space contains an object, the complete space is authoritative and legacy content is no longer merged into either collection.