Repository: plone/documentation
Pull request #1903: Add  /@@test-rendering views to docs
Author: login: Manas-Kenge
Created: 2025-03-13T07:07:44Z | Merged: 2025-03-22T06:44:23Z

## Issue number

- Fixes #1871

## Description

This is a WIP, need an initial review to keep working. As per https://github.com/plone/documentation/issues/1871#issuecomment-2717865542 a mention of both test-rendering and Storyboard docs in the migration docs under [Migrating from Plone Classic UI to Volto](https://6.docs.plone.org/backend/upgrading/version-specific-migration/migrate-to-volto.html) is remaining.




<!-- readthedocs-preview plone6 start -->
----
📚 Documentation preview 📚: https://plone6--1903.org.readthedocs.build/classic-ui/theming/create-add-on.html#styles-test-rendering

<!-- readthedocs-preview plone6 end -->

Linked issue #1871: Add a mention of the /@@test-rendering views to the developer documentation for Classic UI
### Hidden Design Elements Previews in Plone
In the ClassicUI we have a @@test_rendering view
This renders **examples of most UI elements using the active CSS styling.**

This useful hidden feature is **not mentioned or searchable in the docs or trainings.**

### How to enter these pages

- in a Plone ClassicUI site append  /@@test-rendering to any url
- from there you can enter three tabs:
        - [Test Rendering] ./@@test-rendering
        - [Bootstrap Cheatsheet]./@@test-rendering-cheatsheet
        - [Icons] ./@@test-rendering-icons

### ToDo
Add a chapter or notes to the docs and trainings for people in need to look up styling and available elements in Plone

### Related Questions

1. Is this feature deprecated and or unsupported? It was present since at least Plone 3 (in Plone 2.5 we had /test_rendering)
2. Is there any related view for Volto?
3. How are the Storybook attempts in e.g. Mockup related to this?
Linked issue comments: user: login: acsr
created_at: 2025-02-20T14:18:44Z
body: the source is in https://github.com/plone/Products.CMFPlone/tree/master/Products/CMFPlone/browser/templates
- Products/CMFPlone/browser/templates/test_rendering.pt
- Products/CMFPlone/browser/templates/test_rendering_cheatsheet.pt
- Products/CMFPlone/browser/templates/test_rendering_icons.pt
author_association: CONTRIBUTOR
user: login: Manas-Kenge
created_at: 2025-03-08T05:39:24Z
body: Hey @acsr, I reproduced the view as you mentioned and saw the three tabs. Should I start working on the documentation, or is there any ongoing discussion with other maintainers?
author_association: CONTRIBUTOR
user: login: acsr
created_at: 2025-03-08T18:14:57Z
body: Hey @Manas-Kenge I reformatted my questions as ordered list and answer myself. I do not know of a discussion elsewhere.

1. I think you can ignore the deprecation question until someone points us to a state. The templates were updated for Plone 5 in 2019 and are maintained as necessary until 2 years ago.

- They are still availabe and useful but undocumented. 
- The feature should be documented and this can be helpful. 
- These templates can help during migrations. 
- A deprecation note can be added in a second step or during review of the docs.

Note: I would include at least a note on the presence in older versions because it is not documented there:
> The view @@test-rendering was available since at least Plone 3 (in Plone 2.5 we had /test_rendering)

For the other stuff I will ask in the forum:
2. Since this ticket is explicitly targeting the ClassicUI you can ignore my question related to VoltoUI
3. Off Topic here, just asking if someone knows a relation to connect this. Storybook is an approach to document UI elements (e.g. in plone.mockup) with live code examples.
author_association: CONTRIBUTOR
user: login: acsr
created_at: 2025-03-10T16:30:57Z
body: Addendum: The answer to my points 2. + 3. related to the equivalent to test_rendering in Volto and Storybook were answered in the Forum: pointing to `Plone Documentation v6/VoltoUI/Contributing to Volto` and there `Style Guide`  and `Documentation` mentioning the [Storybook](https://6.docs.plone.org/storybook/) build and a bit hidden: 

in [Storybook entry](http://127.0.0.1:8050/volto/contributing/documentation.html#storybook-entry)
> … When you develop a component, we encourage you to create or update its [Volto Storybook](https://6.docs.plone.org/storybook/) entry.…

This is actually not either Reference Documentation or HowTo.

Ideas & questions how to crosslink both topics can be found in my [comment](https://community.plone.org/t/is-there-something-like-the-test-rendering-examples-page-from-classicui-already-existing-in-volto/21424/3) to the forum post.

This can be part of the next iteration.
author_association: CONTRIBUTOR
user: login: Manas-Kenge
created_at: 2025-03-11T20:03:30Z
body: @acsr I read the discussion about adding a crosslink between the /@@test-rendering documentation and the Volto Storybook. Would you like me to include this crosslink as part of the documentation update, or is this still an idea that needs confirmation?
author_association: CONTRIBUTOR
user: login: acsr
created_at: 2025-03-12T13:20:14Z
body: @Manas-Kenge I am sorry to only offer a discussion with myself (and you). I hope it is helpful to share the considerations.

1. Since we are motivating to a move to Volto I would definitely add a "see also:" to the /@@test-rendering documentation. 
The `see also` could also be pointing at migration hints if we decide to choose that approach (see below).

2. I had currently no final opinion for the Volto counterpart, because the docs for the Storyboard are buried in the `Contributing to Volto` section. The crosslink / tags should go in a unwritten reference in the VoltoUI/Theming story paragraph but this is currently outdated and pointing to Semantic UI styling. Until then it only makes sense in [VoltoUI/Contributing to Volto/Style Guide](https://6.docs.plone.org/volto/contributing/style-guide.html).

While writing this down (rubberducking) I am thinking about an additional approach putting a mention of `@@test-rendering` `test_rendering` and `Storyboard` docs  into a **section on theming in the migration docs** under [Migrating from Plone Classic UI to Volto](https://6.docs.plone.org/backend/upgrading/version-specific-migration/migrate-to-volto.html). 

**This allows to find the terms in context when searching without bloating the docs in detail an avoid being prone to be outdated.**


Example for possible /@@test_rendering documentation only to save you some time
```{seealso}
If you are looking for an overview of UI components in the VoltoUI you can find informations on [Storybook](https://storybook.js.org/) currently under [VoltoUI/Contributing to Volto/Style Guide](https://6.docs.plone.org/volto/contributing/style-guide.html) and in the [documentation of the related make commands ](https://6.docs.plone.org/volto/contributing/documentation.html#storybook-entry)
```


author_association: CONTRIBUTOR
user: login: acsr
created_at: 2025-03-12T13:21:37Z
body: Update: Listening to the ClassicUI team meeting now, @stevepiercy confirmed there the relevance of Storyboard for ClassicUI there and I agree and am seconding.
author_association: CONTRIBUTOR
user: login: acsr
created_at: 2025-03-13T13:55:33Z
body: I accidentially mangled up my correction of spelling of the ids, and reverted all occurrences to the correct wording (hope I did not miss one.

- In Plone 2.5 the url appended was: `/test_rendering` with underscore
- In Plone 3+ the url is /@@test-rendering` with hyphen, the page templates filenames still use underscores
author_association: CONTRIBUTOR

Diff:
diff --git a/docs/_static/test-rendering/bootstrap-cheatsheet.png b/docs/_static/test-rendering/bootstrap-cheatsheet.png
new file mode 100644
index 000000000..86638d462
Binary files /dev/null and b/docs/_static/test-rendering/bootstrap-cheatsheet.png differ
diff --git a/docs/_static/test-rendering/icons.png b/docs/_static/test-rendering/icons.png
new file mode 100644
index 000000000..03983b2df
Binary files /dev/null and b/docs/_static/test-rendering/icons.png differ
diff --git a/docs/_static/test-rendering/test-rendering.png b/docs/_static/test-rendering/test-rendering.png
new file mode 100644
index 000000000..34f1dffce
Binary files /dev/null and b/docs/_static/test-rendering/test-rendering.png differ
diff --git a/docs/classic-ui/theming/create-add-on.md b/docs/classic-ui/theming/create-add-on.md
index 6aba6f935..a3dd5a87a 100644
--- a/docs/classic-ui/theming/create-add-on.md
+++ b/docs/classic-ui/theming/create-add-on.md
@@ -141,3 +141,79 @@ $state-colors: map-merge($state-colors, $custom-colors);
 Inside the file `theme/_custom.scss` you can write all your custom CSS/Sass code to adapt the theme to your needs.
 Feel free to add more files inside the `scss/` folder to make your code more readable.
 Don't forget to import your custom files in `scss/theme.scss`.
+
+
+## Styles test rendering
+
+Plone's Classic UI includes special demonstration views that render ready-made examples of interface components using your site's active theme.
+These views help developers verify styling implementation and explore available UI patterns.
+These views work in any context.
+No special permissions are required.
+
+Append one of the following view names with a leading slash `/` to any Plone site URL.
+
+-   `/@@test-rendering`
+-   `/@@test-rendering-cheatsheet` 
+-   `/@@test-rendering-icons`
+
+Each view name corresponds to a named tab in Plone as described in the following sections.
+
+
+### {guilabel}`Test Rendering`
+
+The {guilabel}`Test Rendering` tab at the view name `@@test-rendering` displays Bootstrap style status message examples.
+It shows all alert variants including:
+
+-   Success, warning, and error notifications
+-   Dismissible alerts
+-   Contextual color examples
+
+````{card}
+```{image} /_static/test-rendering/test-rendering.png
+:alt: Test Rendering
+:target: /_static/test-rendering/test-rendering.png
+```
++++
+_Test Rendering_
+````
+
+### {guilabel}`Bootstrap Cheatsheet`
+
+The {guilabel}`Bootstrap Cheatsheet` tab at the view name `@@test-rendering-cheatsheet` displays the kitchen sink of Bootstrap components.
+It includes the following examples and dozens more:
+
+-   color mode switcher interface, located in the lower right corner of the browser window
+-   grid layout examples
+-   form control variants
+-   navigation components
+-   interactive element states
+  
+````{card}
+```{image} /_static/test-rendering/bootstrap-cheatsheet.png
+:alt: Bootstrap Cheatsheet
+:target: /_static/test-rendering/bootstrap-cheatsheet.png
+```
++++
+_Bootstrap Cheatsheet_
+````
+
+### {guilabel}`Icons`
+
+The {guilabel}`Icons` tab at the view name `@@test-rendering-icons` displays a few icon classes.
+It includes the following examples:
+
+-   icon resolver usage
+-   code samples for both URL and tag generation
+
+````{card}
+```{image} /_static/test-rendering/icons.png
+:alt: Icons
+:target: /_static/test-rendering/icons.png
+```
++++
+_Icons_
+````
+
+```{seealso}
+For an overview of UI components in Volto, see its [Storybook](https://6.docs.plone.org/storybook/).
+```


Reviews:
user: login: stevepiercy
body: I'll do a second review, but for now...

- Please follow https://6.docs.plone.org/contributing/documentation/authors.html#plone-documentation-styleguide, specifically:

  > Headings should be "Sentence cased", not "Title Cased".

- Don't inject content between a target `(classic-ui-template-slots-label)=` and its heading. Keep them close together.
- The correct proper name is "Classic UI" with a space.
- Use 4 spaces indentation in all list items, else they don't render correctly.
- This content breaks flow of the original document. You must consider where it belongs, and not throw it in wherever.
- A picture is worth a thousand words. Screenshots would be nice. See guidance in https://6.docs.plone.org/contributing/documentation/myst-reference.html#images-and-figures
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-13T09:07:34Z
user: login: acsr
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-13T14:03:29Z
user: login: acsr
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-13T14:06:22Z
user: login: petschki
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-13T14:42:35Z
user: login: petschki
body: I'd suggest to put this somewhere into `classic-ui/theming/create-add-on.md` as subsection **Styles Test Rendering**
state: CHANGES_REQUESTED
author_association: MEMBER
submitted_at: 2025-03-13T15:00:43Z
user: login: acsr
body: @Manas-Kenge Thx for this initial iteration. Maybe we need another round. 
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-13T15:55:03Z
user: login: acsr
body: @Manas-Kenge THX! Everything else looks good to me… except the orphaned `Colormode switcher` hint, that needs more love. I suggest taking it out and continue in a seperate iteration issued by @petschki .
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-18T13:22:59Z
user: login: Manas-Kenge
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-18T14:18:34Z
user: login: acsr
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-18T16:42:48Z
user: login: acsr
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-18T16:47:04Z
user: login: petschki
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-19T07:45:46Z
user: login: petschki
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-19T07:48:06Z
user: login: stevepiercy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T08:17:00Z
user: login: stevepiercy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T08:19:11Z
user: login: stevepiercy
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T08:22:12Z
user: login: petschki
body: good!
state: DISMISSED
author_association: MEMBER
submitted_at: 2025-03-19T08:23:51Z
user: login: acsr
body: LGTM @petschki @Manas-Kenge @stevepiercy finally fine…
state: DISMISSED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T12:24:11Z
user: login: stevepiercy
body: I just noticed that these images are too wide to display clearly in the portal. Please see https://6.docs.plone.org/contributing/documentation/myst-reference.html#width-of-media.

You can either crop out the left toolbar or collapse it.

I also found a bug and opened an [issue in plone-sphinx-theme](https://github.com/plone/plone-sphinx-theme/issues/71) for it, but that's beyond the scope of this PR.
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T19:59:47Z
user: login: stevepiercy
body: Please resize the browser such that images are no wider than 760 pixels, as described in https://6.docs.plone.org/contributing/documentation/myst-reference.html#width-of-media
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-20T05:20:38Z
user: login: stevepiercy
body: You need to resize the browser window, then take the screenshot to fit the browser area that matters. Downsizing an image worsens its legibility. Was that not clear in the documentation?

https://6.docs.plone.org/contributing/documentation/myst-reference.html#width-of-media
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-20T22:46:33Z
user: login: stevepiercy
body: There we go! Thank you! Merging when green.
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-03-22T06:43:36Z

Review comments:
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
path: docs/classic-ui/views.md
user: login: stevepiercy
body: No. The URL segment to append to the site URL is `/@@test-rendering`. If I append the provided string, I get a 404.

Also convert this to a bulleted list, not a code block.
created_at: 2025-03-13T09:07:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
path: docs/classic-ui/views.md
user: login: acsr
body: @stevepiercy Yep you are right. I was careless during writing copy pasting the underscore based terms too often. I corrected the terms in all ticket comments to avoid further confusion (And I had to do it twice)
created_at: 2025-03-13T14:03:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
path: docs/classic-ui/views.md
user: login: acsr
body: @Manas-Kenge To make it clear: The part to **append** is e.g. just `/@@test-rendering` etc. and leave out the absolute url prefix.
created_at: 2025-03-13T14:06:22Z
author_association: CONTRIBUTOR
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
+http://localhost:8080/Plone/about/@@test-rendering-cheatsheet
+http://localhost:8080/Plone/@@test-rendering-icons
+```
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    ```
+    http://localhost:8080/Plone/@@test-rendering
+    ```
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    ```
+    http://localhost:8080/Plone/@@test-rendering-cheatsheet
+    ```
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
path: docs/classic-ui/views.md
user: login: petschki
body: I'd also mention the colormode switcher here
created_at: 2025-03-13T14:42:35Z
author_association: MEMBER
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
+http://localhost:8080/Plone/about/@@test-rendering-cheatsheet
+http://localhost:8080/Plone/@@test-rendering-icons
+```
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    ```
+    http://localhost:8080/Plone/@@test-rendering
path: docs/classic-ui/views.md
user: login: acsr
body: same as line 265 here: single line or bullet without code fence, just part to append as inline code, no url prefix.
created_at: 2025-03-13T15:13:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
+http://localhost:8080/Plone/about/@@test-rendering-cheatsheet
+http://localhost:8080/Plone/@@test-rendering-icons
+```
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    ```
+    http://localhost:8080/Plone/@@test-rendering
+    ```
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    ```
+    http://localhost:8080/Plone/@@test-rendering-cheatsheet
path: docs/classic-ui/views.md
user: login: acsr
body: same as line 265 here: single line or bullet without code fence, just part to append as inline code, no url prefix.
created_at: 2025-03-13T15:14:05Z
author_association: CONTRIBUTOR
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
+http://localhost:8080/Plone/about/@@test-rendering-cheatsheet
+http://localhost:8080/Plone/@@test-rendering-icons
+```
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    ```
+    http://localhost:8080/Plone/@@test-rendering
+    ```
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    ```
+    http://localhost:8080/Plone/@@test-rendering-cheatsheet
+    ```
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
+
+3. Icon Showcase (`@@test-rendering-icons`)
+   Presents all icon classes available in the current theme:
+    ```
+    http://localhost:8080/Plone/@@test-rendering-icons
path: docs/classic-ui/views.md
user: login: acsr
body: same as line 265 here: single line or bullet without code fence, just part to append as inline code, no url prefix.
created_at: 2025-03-13T15:14:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
+http://localhost:8080/Plone/about/@@test-rendering-cheatsheet
+http://localhost:8080/Plone/@@test-rendering-icons
+```
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    ```
+    http://localhost:8080/Plone/@@test-rendering
+    ```
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    ```
+    http://localhost:8080/Plone/@@test-rendering-cheatsheet
+    ```
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
path: docs/classic-ui/views.md
user: login: acsr
body: @petschki I cannot find any colormode text in the templates. Any hints?
created_at: 2025-03-13T15:19:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
+http://localhost:8080/Plone/about/@@test-rendering-cheatsheet
+http://localhost:8080/Plone/@@test-rendering-icons
+```
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    ```
+    http://localhost:8080/Plone/@@test-rendering
+    ```
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    ```
+    http://localhost:8080/Plone/@@test-rendering-cheatsheet
+    ```
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
path: docs/classic-ui/views.md
user: login: acsr
body: The page https://6.docs.plone.org/classic-ui/theming/color-mode.html is listed by google, but not present (404).

The Light/dark/auto Toggle Button is mentioned in https://6.docs.plone.org/classic-ui/theming/color-modes.html#toggle-button

I guess you mean "mentioning" means to point out, that the appearance of the examples differs depending on your day/night dark/light theme setting.

This is a halfbaked admonition. @stevepiercy can wordsmith a better one.

```` myst
```{important}
Please take into consideration how to make sure checking the examples includes both the dark and light setting when testing the UI.
```
````
created_at: 2025-03-13T15:33:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -141,3 +141,77 @@ $state-colors: map-merge($state-colors, $custom-colors);
 Inside the file `theme/_custom.scss` you can write all your custom CSS/Sass code to adapt the theme to your needs.
 Feel free to add more files inside the `scss/` folder to make your code more readable.
 Don't forget to import your custom files in `scss/theme.scss`.
+
+## Styles Test Rendering
+
+Plone's Classic UI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+   - /@@test-rendering
+   - /@@test-rendering-cheatsheet 
+   - /@@test-rendering-icons
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    - /@@test-rendering
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+    ````{card}
+    ```{image} /_static/test-rendering/test-rendering.png
+    :alt: Alerts Demo
+    :target: /_static/test-rendering/test-rendering.png
+    ```
+    +++
+    _Alerts Demo_
+    ````
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    - /@@test-rendering-cheatsheet
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
+    - Colormode switcher
path: docs/classic-ui/theming/create-add-on.md
user: login: acsr
body: As I wrote before in my last review: 
**There is no `Colormode switcher` mentioned in the current Plone6.1 cheatsheet at all.** 
Not even the word `color` is present to search on the page. Also no manual dark/light colormode switcher is visible by default in Classic UI, in the personal prefs or as action that could be activated. This needs more explanation or to be removed. 

The `Colormode switcher` item was requested by @petschki very vague [in this review comment](https://github.com/plone/documentation/pull/1903#discussion_r1993683944):
> I'd also mention the colormode switcher here

@petschki  -> Can you please clarify / refine that?

The Light/dark/auto Toggle Button is mentioned in https://6.docs.plone.org/classic-ui/theming/color-modes.html#toggle-button

see also from my comment: https://github.com/plone/documentation/pull/1903#discussion_r1993790568 :

> I guess you mean "mentioning" means to point out, that the appearance of the examples differs depending on your day/night dark/light theme setting.
> 
> This is a halfbaked admonition. @stevepiercy can wordsmith a better one.
> 
> ```{important}
> Please take into consideration how to make sure checking the examples includes both the dark and light setting when testing the UI.
> ```




created_at: 2025-03-18T13:19:53Z
author_association: CONTRIBUTOR
diff_hunk: @@ -141,3 +141,77 @@ $state-colors: map-merge($state-colors, $custom-colors);
 Inside the file `theme/_custom.scss` you can write all your custom CSS/Sass code to adapt the theme to your needs.
 Feel free to add more files inside the `scss/` folder to make your code more readable.
 Don't forget to import your custom files in `scss/theme.scss`.
+
+## Styles Test Rendering
+
+Plone's Classic UI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+   - /@@test-rendering
+   - /@@test-rendering-cheatsheet 
+   - /@@test-rendering-icons
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    - /@@test-rendering
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+    ````{card}
+    ```{image} /_static/test-rendering/test-rendering.png
+    :alt: Alerts Demo
+    :target: /_static/test-rendering/test-rendering.png
+    ```
+    +++
+    _Alerts Demo_
+    ````
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    - /@@test-rendering-cheatsheet
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
+    - Colormode switcher
path: docs/classic-ui/theming/create-add-on.md
user: login: Manas-Kenge
body: @acsr I will remove the `Colormode switcher` point, as for Light/dark/auto Toggle there is no need of a mention right? Or should we wait for @petschki to respond?
created_at: 2025-03-18T14:18:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -141,3 +141,77 @@ $state-colors: map-merge($state-colors, $custom-colors);
 Inside the file `theme/_custom.scss` you can write all your custom CSS/Sass code to adapt the theme to your needs.
 Feel free to add more files inside the `scss/` folder to make your code more readable.
 Don't forget to import your custom files in `scss/theme.scss`.
+
+## Styles Test Rendering
+
+Plone's Classic UI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+   - /@@test-rendering
+   - /@@test-rendering-cheatsheet 
+   - /@@test-rendering-icons
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    - /@@test-rendering
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+    ````{card}
+    ```{image} /_static/test-rendering/test-rendering.png
+    :alt: Alerts Demo
+    :target: /_static/test-rendering/test-rendering.png
+    ```
+    +++
+    _Alerts Demo_
+    ````
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    - /@@test-rendering-cheatsheet
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
+    - Colormode switcher
path: docs/classic-ui/theming/create-add-on.md
user: login: acsr
body: @Manas-Kenge Wait one day and then take it out. I push him ;-)
created_at: 2025-03-18T16:42:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -141,3 +141,77 @@ $state-colors: map-merge($state-colors, $custom-colors);
 Inside the file `theme/_custom.scss` you can write all your custom CSS/Sass code to adapt the theme to your needs.
 Feel free to add more files inside the `scss/` folder to make your code more readable.
 Don't forget to import your custom files in `scss/theme.scss`.
+
+## Styles Test Rendering
+
+Plone's Classic UI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+   - /@@test-rendering
+   - /@@test-rendering-cheatsheet 
+   - /@@test-rendering-icons
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    - /@@test-rendering
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+    ````{card}
+    ```{image} /_static/test-rendering/test-rendering.png
+    :alt: Alerts Demo
+    :target: /_static/test-rendering/test-rendering.png
+    ```
+    +++
+    _Alerts Demo_
+    ````
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    - /@@test-rendering-cheatsheet
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
+    - Colormode switcher
path: docs/classic-ui/theming/create-add-on.md
user: login: acsr
body: It can be added in a next iteration again. I have no clue what to add except my suggested admonition.
created_at: 2025-03-18T16:47:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -141,3 +141,77 @@ $state-colors: map-merge($state-colors, $custom-colors);
 Inside the file `theme/_custom.scss` you can write all your custom CSS/Sass code to adapt the theme to your needs.
 Feel free to add more files inside the `scss/` folder to make your code more readable.
 Don't forget to import your custom files in `scss/theme.scss`.
+
+## Styles Test Rendering
+
+Plone's Classic UI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+   - /@@test-rendering
+   - /@@test-rendering-cheatsheet 
+   - /@@test-rendering-icons
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    - /@@test-rendering
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+    ````{card}
+    ```{image} /_static/test-rendering/test-rendering.png
+    :alt: Alerts Demo
+    :target: /_static/test-rendering/test-rendering.png
+    ```
+    +++
+    _Alerts Demo_
+    ````
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    - /@@test-rendering-cheatsheet
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
+    - Colormode switcher
path: docs/classic-ui/theming/create-add-on.md
user: login: petschki
body: The colormode switcher is on  the second tab in the "bootstrap cheatsheet" at the bottom right ... https://classic.demo.plone.org/@@test-rendering-cheatsheet

the implementation is already documented here https://6.docs.plone.org/classic-ui/theming/color-modes.html
created_at: 2025-03-19T07:45:46Z
author_association: MEMBER
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
+http://localhost:8080/Plone/about/@@test-rendering-cheatsheet
+http://localhost:8080/Plone/@@test-rendering-icons
+```
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    ```
+    http://localhost:8080/Plone/@@test-rendering
+    ```
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    ```
+    http://localhost:8080/Plone/@@test-rendering-cheatsheet
+    ```
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
path: docs/classic-ui/views.md
user: login: petschki
body: I just wanted to mention, that you can see the color mode switcher in action here ... if you want to use it for your project you have to read the doc ...
created_at: 2025-03-19T07:48:06Z
author_association: MEMBER
diff_hunk: @@ -252,6 +252,60 @@ Add the name of the new view `my-view` to the following list:
 
 (classic-ui-template-slots-label)=
 
+### UI Component Demo Views in ClassicUI
+
+Plone's ClassicUI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+#### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+```
+http://localhost:8080/Plone/@@test-rendering
+http://localhost:8080/Plone/about/@@test-rendering-cheatsheet
+http://localhost:8080/Plone/@@test-rendering-icons
+```
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    ```
+    http://localhost:8080/Plone/@@test-rendering
+    ```
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    ```
+    http://localhost:8080/Plone/@@test-rendering-cheatsheet
+    ```
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
path: docs/classic-ui/views.md
user: login: stevepiercy
body: It's a button interface in the lower right corner.
created_at: 2025-03-19T08:17:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -141,3 +141,77 @@ $state-colors: map-merge($state-colors, $custom-colors);
 Inside the file `theme/_custom.scss` you can write all your custom CSS/Sass code to adapt the theme to your needs.
 Feel free to add more files inside the `scss/` folder to make your code more readable.
 Don't forget to import your custom files in `scss/theme.scss`.
+
+## Styles Test Rendering
+
+Plone's Classic UI includes special demonstration views that render ready-made examples of interface components using your site's active theme. These live previews help developers verify styling implementation and explore available UI patterns.
+These views work in any context - append to site root or content URLs. No special permissions are required.
+
+### Accessing Component Demo Views:
+
+Append one of these view names to any Plone site URL:
+
+   - /@@test-rendering
+   - /@@test-rendering-cheatsheet 
+   - /@@test-rendering-icons
+
+Three dedicated preview tabs are available:
+
+1.  Component Alerts Demo (`@@test-rendering`)
+    Displays Bootstrap-style status message examples:  
+    - /@@test-rendering
+    
+    Shows all alert variants including:
+    - Success/warning/error notifications
+    - Dismissible alerts
+    - Contextual color examples
+
+    ````{card}
+    ```{image} /_static/test-rendering/test-rendering.png
+    :alt: Alerts Demo
+    :target: /_static/test-rendering/test-rendering.png
+    ```
+    +++
+    _Alerts Demo_
+    ````
+
+2. Bootstrap Pattern Library (`@@test-rendering-cheatsheet`)
+   Renders a comprehensive component reference based on Bootstrap's official cheatsheet:
+    - /@@test-rendering-cheatsheet
+    
+    Includes:
+    - Grid layout examples
+    - Form control variants
+    - Navigation components
+    - Interactive element states
+    - Colormode switcher
path: docs/classic-ui/theming/create-add-on.md
user: login: stevepiercy
body: The color mode switcher interface is located in the lower right corner of the browser window.
created_at: 2025-03-19T08:19:11Z
author_association: CONTRIBUTOR

PR comments:
user: login: stevepiercy
created_at: 2025-03-13T09:11:09Z
body: @plone/classicui-team could I get a review from y'all on content accuracy, and where this documentation should reside? It's in the wrong place at the moment. Thank you!
author_association: CONTRIBUTOR
user: login: jensens
created_at: 2025-03-18T10:47:58Z
body: It is indeed important information for theming Classic UI. 
author_association: MEMBER
user: login: acsr
created_at: 2025-03-18T10:51:51Z
body: I am lost how to review latest changes due to confusion if a test build exists or how to checkout the latest state of the pr locally. If I am the origin of that mess, get me out of the ditch… ;-)
author_association: CONTRIBUTOR
user: login: stevepiercy
created_at: 2025-03-18T12:29:50Z
body: @acsr I'm not sure exactly what you want to review, but to see the rendered HTML, visit the pull request preview at https://plone6--1903.org.readthedocs.build/classic-ui/theming/create-add-on.html#styles-test-rendering. If a repo supports pull request previews, then Read the Docs will insert a link in the PR description, which I then usually modify to point to the affected files for convenience.

To checkout this branch, you first need to add a git remote `https://github.com/Manas-Kenge/documentation.git`, then `git fetch --all`, and finally checkout the branch. You can then view git commit history.
author_association: CONTRIBUTOR
user: login: acsr
created_at: 2025-03-18T12:57:09Z
body: > visit the pull request preview at https://plone6--1903.org.readthedocs.build/classic-ui/theming/create-add-on.html#styles-test-rendering.

I did exactly this (the link at the top of the PR) but it did not work for me. (I had this several times, that these links seem broken. I thought it was due to they were outdated because of changes after a review.)

But it is possible that Github ditches them after some time.
author_association: CONTRIBUTOR
user: login: stevepiercy
created_at: 2025-03-18T13:31:33Z
body: > > visit the pull request preview at https://plone6--1903.org.readthedocs.build/classic-ui/theming/create-add-on.html#styles-test-rendering.
> 
> I did exactly this (the link at the top of the PR) but it did not work for me. (I had this several times, that these links seem broken. I thought it was due to they were outdated because of changes after a review.)
> 
> But it is possible that Github ditches them after some time.

RTD inserts the link immediately when it starts the build, not when the build completes. So if you visit the link within 5 minutes of the PR creation, then you might get a 404. Otherwise, it should always work. It works for me now.
author_association: CONTRIBUTOR
user: login: stevepiercy
created_at: 2025-03-19T08:22:58Z
body: I'm happy with this content after making a few commits. @acsr or @petschki one more pass, please? Thank you!
author_association: CONTRIBUTOR
user: login: acsr
created_at: 2025-03-19T12:30:55Z
body: Background: I was waiting for over 10 years to have this finally in the docs. There is nothing done unless you do it. (Shame on me). In this case I at least wrote the ticket now. And @Manas-Kenge picked it up. 

When Ramon and Albert were working on Barceloneta they were surprised when I showed it to them in Sorrento. But then I left it to others to make it into the docs. 
author_association: CONTRIBUTOR
user: login: jensens
created_at: 2025-03-20T09:11:59Z
body: There is also for any type with image fields the `@@images-test` view from [plone.namedfile](https://github.com/plone/plone.namedfile). 
author_association: MEMBER
user: login: stevepiercy
created_at: 2025-03-20T09:15:30Z
body: > There is also for any type with image fields the `@@images-test` view from [plone.namedfile](https://github.com/plone/plone.namedfile).

https://classic.demo.plone.org/@@images-test 😢 

@jensens got a valid link to view?
author_association: CONTRIBUTOR
user: login: jensens
created_at: 2025-03-20T09:41:53Z
body: in theory this should work, but its broken, hmm, smells like a bug
https://classic.demo.plone.org/en/demo/an-image.jpg/@@images-test
author_association: MEMBER
user: login: stevepiercy
created_at: 2025-03-20T09:48:33Z
body: > in theory this should work, but its broken, hmm, smells like a bug https://classic.demo.plone.org/en/demo/an-image.jpg/@@images-test

And an old one at that https://github.com/plone/plone.namedfile/issues/125.

Until it's resolved, we shouldn't document it.
author_association: CONTRIBUTOR
user: login: stevepiercy
created_at: 2025-03-20T11:39:22Z
body: @mauritsvanrees corrected me, and created a new issue https://github.com/plone/plone.namedfile/issues/173.
author_association: CONTRIBUTOR
user: login: Manas-Kenge
created_at: 2025-03-21T06:16:16Z
body: Hey @stevepiercy, I did as you asked, but the image quality hasn't improved even after taking the screenshots.
author_association: CONTRIBUTOR
user: login: stevepiercy
created_at: 2025-03-21T07:16:41Z
body: You did not resize your browser width. In this screenshot, you can see that I resized my browser width such that the area I want to capture has a width of 760 pixels.

![Screenshot 2025-03-21 at 12 14 14 AM](https://github.com/user-attachments/assets/739d783b-abb9-418d-a78f-d1f8df9dc02c)

I would then get a screenshot of only that area I needed, without all the navigation.

![Screenshot 2025-03-21 at 12 15 33 AM](https://github.com/user-attachments/assets/21585b9e-b08c-4f9b-8957-37420c807db6)


author_association: CONTRIBUTOR
user: login: mauritsvanrees
created_at: 2025-03-25T11:40:37Z
body: > in theory this should work, but its broken, hmm, smells like a bug https://classic.demo.plone.org/en/demo/an-image.jpg/@@images-test

I have released Plone 6.1.1 final, and Philip has updated the Classic demo site and this now works.
author_association: MEMBER