Skip to content

Add Shapes documentation#19354

Open
agriffard wants to merge 3 commits into
mainfrom
ag/shapesDoc
Open

Add Shapes documentation#19354
agriffard wants to merge 3 commits into
mainfrom
ag/shapesDoc

Conversation

@agriffard

Copy link
Copy Markdown
Member

Fixes #19350

Add a sub menu in "Display Management" to explain the concept of Shapes and how it is used in Orchard Core.

Comment thread src/docs/topics/display/shapes.md Outdated

If you come to Orchard Core from classic ASP.NET MVC, the first thing that surprises you is that there are almost no fixed view models. A page is not a single strongly-typed `Model` rendered by a single `.cshtml`. Instead, the page is a **tree of shapes** — small, dynamic objects that each know how they want to be displayed, assembled at runtime and rendered into HTML.

Shapes are the single most important concept in Orchard Core's UI layer. Once they click, the whole theming and customization story makes sense. This page explains what a shape is, how the rendering pipeline turns it into HTML, and why alternates and placement give you so much control without touching code.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be useful to explain why we aren't using static view models for content display, and why we still use them usually otherwise.

Comment thread src/docs/topics/display/shapes.md Outdated
agriffard and others added 2 commits June 8, 2026 10:41
Co-authored-by: Zoltán Lehóczky <zoltan.lehoczky@lombiq.com>
Co-authored-by: Zoltán Lehóczky <zoltan.lehoczky@lombiq.com>
@sebastienros sebastienros added this to the 3.x milestone Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Shapes documentation

3 participants