NuGet ยท nuget

Redeon.SuperSiteEngineCore.Web.Eltheon.Core.Features.Renderer.Demo

Demo CMS consumer for the Eltheon Renderer feature.

Install

Install-Kommandos

dotnet add package Redeon.SuperSiteEngineCore.Web.Eltheon.Core.Features.Renderer.Demo --version 2.9.4
<PackageReference Include="Redeon.SuperSiteEngineCore.Web.Eltheon.Core.Features.Renderer.Demo" Version="2.9.4" />
paket add Redeon.SuperSiteEngineCore.Web.Eltheon.Core.Features.Renderer.Demo --version 2.9.4
Install-Package Redeon.SuperSiteEngineCore.Web.Eltheon.Core.Features.Renderer.Demo -Version 2.9.4

README

Vorschau

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-demo Storage 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 + IRenderService pipeline.
  • 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 IEventBus is registered.
  • New DemoCMS pages use elyra by default.
  • elyra is not an alias. It composes Fluid/Liquid expressions, renderer components, Markdown conversion and final HTML sanitizing.
  • fluid is for pure Fluid/HTML test pages.
  • markdown is for pure Markdown test pages.
  • plaintext is 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.