@bluedynamics/cdk8s-plone 0.1.41 → 0.1.42

package/.jsii

@@ -108,7 +108,7 @@
   },
   "name": "@bluedynamics/cdk8s-plone",
   "readme": {
-    "markdown": "# CDK8S Plone\n\n> TypeScript and Python library for deploying Plone CMS to Kubernetes using CDK8S\n\n[![npm version](https://badge.fury.io/js/%40bluedynamics%2Fcdk8s-plone.svg)](https://www.npmjs.com/package/@bluedynamics/cdk8s-plone)\n[![PyPI version](https://badge.fury.io/py/cdk8s-plone.svg)](https://pypi.org/project/cdk8s-plone/)\n[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)\n\n## Overview\n\ncdk8s-plone provides CDK8S constructs for deploying [Plone CMS](https://plone.org/) on Kubernetes. Define your infrastructure using TypeScript or Python and generate Kubernetes manifests automatically.\n\n**Key Features:**\n- 🚀 Supports Volto (modern React frontend) and Classic UI\n- 📦 High availability with configurable replicas\n- ⚡ Optional Varnish HTTP caching via kube-httpcache (`PloneHttpcache`) or cloud-vinyl VinylCache operator (`PloneVinylCache`)\n- 🔧 Fine-grained resource and probe configuration\n- 🌍 Multi-language support (TypeScript/JavaScript and Python)\n- ✅ Type-safe infrastructure as code\n\n## Quick Start\n\n### Installation\n\n**TypeScript/JavaScript:**\n```bash\nnpm install @bluedynamics/cdk8s-plone\n```\n\n**Python:**\n```bash\npip install cdk8s-plone\n```\n\n### Basic Example\n\n```typescript\nimport { App, Chart } from 'cdk8s';\nimport { Plone, PloneVariant } from '@bluedynamics/cdk8s-plone';\n\nconst app = new App();\nconst chart = new Chart(app, 'PloneDeployment');\n\nnew Plone(chart, 'my-plone', {\n  variant: PloneVariant.VOLTO,\n  backend: {\n    image: 'plone/plone-backend:6.1.3',\n    replicas: 3,\n  },\n  frontend: {\n    image: 'plone/plone-frontend:16.0.0',\n    replicas: 2,\n  },\n});\n\napp.synth();\n```\n\nGenerate Kubernetes manifests:\n```bash\ncdk8s synth\nkubectl apply -f dist/\n```\n\n## Documentation\n\n**📚 Full documentation:** https://bluedynamics.github.io/cdk8s-plone/\n\n- [Quick Start Tutorial](https://bluedynamics.github.io/cdk8s-plone/tutorials/01-quick-start.html)\n- [Configuration Reference](https://bluedynamics.github.io/cdk8s-plone/reference/configuration-options.html)\n- [Architecture Overview](https://bluedynamics.github.io/cdk8s-plone/explanation/architecture.html)\n- [Complete API Documentation](./API.md)\n\n## Examples\n\nComplete working examples are available in the [`examples/`](examples/) directory:\n\n- **[Production Volto](examples/production-volto/)** - Production-ready Plone 6 deployment with modern UI:\n  - Volto frontend (React) + REST API backend\n  - PostgreSQL with RelStorage (CloudNativePG or Bitnami)\n  - Varnish HTTP caching with kube-httpcache\n  - Ingress support (Traefik/Kong) with TLS\n\n- **[Classic UI](examples/classic-ui/)** - Traditional Plone deployment with server-side rendering:\n  - Classic UI (traditional Plone interface)\n  - PostgreSQL with RelStorage (CloudNativePG or Bitnami)\n  - Varnish HTTP caching with kube-httpcache\n  - Ingress support (Traefik/Kong) with TLS\n  - Simpler architecture (no separate frontend)\n\n### Prometheus Metrics\n\nEnable Prometheus ServiceMonitor for metrics collection (requires Prometheus Operator):\n\n```typescript\nnew Plone(chart, 'my-plone', {\n  backend: {\n    servicemonitor: true,\n    metricsPath: '/metrics',  // optional, defaults to '/metrics'\n  },\n  frontend: {\n    servicemonitor: true,\n    metricsPort: 9090,  // optional, defaults to service port\n  },\n});\n```\n\n**Note:** You must instrument your Plone backend/frontend to expose metrics at the configured endpoint. For Volto/Node.js frontends, consider using [prom-client](https://www.npmjs.com/package/prom-client) or [express-prometheus-middleware](https://www.npmjs.com/package/express-prometheus-middleware).\n\n## Requirements\n- **kubectl** - [Install kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl)\n- **Node.js 16+** (for TypeScript/JavaScript) - [Install Node.js](https://nodejs.org/)\n- **Python 3.8+** (for Python) - [Install Python](https://www.python.org/)\n- **Kubernetes cluster** (local or cloud)\n\nFor detailed setup instructions, see [Setup Prerequisites](https://bluedynamics.github.io/cdk8s-plone/how-to/setup-prerequisites.html).\n\n## Development\n\nThis project uses [Projen](https://projen.io/) for project management.\n\n```bash\n# Install dependencies\nnpm install\n\n# Run tests\nnpm test\n\n# Build\nnpm run build\n\n# Update project configuration\n# Edit .projenrc.ts, then run:\nnpx projen\n```\n\nFor detailed development instructions, see [CONTRIBUTING.md](./CONTRIBUTING.md) (if available).\n\n## Resources\n\n- [CDK8S Documentation](https://cdk8s.io/)\n- [Plone CMS](https://plone.org/)\n- [kube-httpcache](https://github.com/mittwald/kube-httpcache) (for HTTP caching)\n- [CloudNativePG](https://cloudnative-pg.io/) (for PostgreSQL management)\n\n## License\n\n[Apache 2.0](LICENSE)\n\n## Maintainers\n\nMaintained by [Blue Dynamics Alliance](https://github.com/bluedynamics)\n\n**Author:** Jens W. Klein (jk@kleinundpartner.at)\n"
+    "markdown": "# CDK8S Plone\n\n> TypeScript and Python library for deploying Plone CMS to Kubernetes using CDK8S\n\n[![npm version](https://badge.fury.io/js/%40bluedynamics%2Fcdk8s-plone.svg)](https://www.npmjs.com/package/@bluedynamics/cdk8s-plone)\n[![PyPI version](https://badge.fury.io/py/cdk8s-plone.svg)](https://pypi.org/project/cdk8s-plone/)\n[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)\n\n## Overview\n\ncdk8s-plone provides CDK8S constructs for deploying [Plone CMS](https://plone.org/) on Kubernetes. Define your infrastructure using TypeScript or Python and generate Kubernetes manifests automatically.\n\n**Key Features:**\n- 🚀 Supports Volto (React frontend) and Blicca (formerly Classic UI)\n- 📦 High availability with configurable replicas\n- ⚡ Optional Varnish HTTP caching via kube-httpcache (`PloneHttpcache`) or cloud-vinyl VinylCache operator (`PloneVinylCache`)\n- 🔧 Fine-grained resource and probe configuration\n- 🌍 Multi-language support (TypeScript/JavaScript and Python)\n- ✅ Type-safe infrastructure as code\n\n## Quick Start\n\n### Installation\n\n**TypeScript/JavaScript:**\n```bash\nnpm install @bluedynamics/cdk8s-plone\n```\n\n**Python:**\n```bash\npip install cdk8s-plone\n```\n\n### Basic Example\n\n```typescript\nimport { App, Chart } from 'cdk8s';\nimport { Plone, PloneVariant } from '@bluedynamics/cdk8s-plone';\n\nconst app = new App();\nconst chart = new Chart(app, 'PloneDeployment');\n\nnew Plone(chart, 'my-plone', {\n  variant: PloneVariant.VOLTO,\n  backend: {\n    image: 'plone/plone-backend:6.1.3',\n    replicas: 3,\n  },\n  frontend: {\n    image: 'plone/plone-frontend:16.0.0',\n    replicas: 2,\n  },\n});\n\napp.synth();\n```\n\nGenerate Kubernetes manifests:\n```bash\ncdk8s synth\nkubectl apply -f dist/\n```\n\n## Documentation\n\n**📚 Full documentation:** https://bluedynamics.github.io/cdk8s-plone/\n\n- [Quick Start Tutorial](https://bluedynamics.github.io/cdk8s-plone/tutorials/01-quick-start.html)\n- [Configuration Reference](https://bluedynamics.github.io/cdk8s-plone/reference/configuration-options.html)\n- [Architecture Overview](https://bluedynamics.github.io/cdk8s-plone/explanation/architecture.html)\n- [Complete API Documentation](./API.md)\n\n## Examples\n\nComplete working examples are available in the [`examples/`](examples/) directory:\n\n- **[Production Volto](examples/production-volto/)** - Production-ready Plone 6 deployment with the React single-page frontend:\n  - Volto frontend (React) + REST API backend\n  - PostgreSQL with RelStorage (CloudNativePG or Bitnami)\n  - Varnish HTTP caching with kube-httpcache\n  - Ingress support (Traefik/Kong) with TLS\n\n- **[Blicca](examples/blicca/)** - Plone deployment with server-side rendering (formerly Classic UI):\n  - Blicca (backend renders the UI, no separate frontend)\n  - PostgreSQL with RelStorage (CloudNativePG or Bitnami)\n  - Varnish HTTP caching with kube-httpcache\n  - Ingress support (Traefik/Kong) with TLS\n  - Simpler architecture (no separate frontend)\n\n### Prometheus Metrics\n\nEnable Prometheus ServiceMonitor for metrics collection (requires Prometheus Operator):\n\n```typescript\nnew Plone(chart, 'my-plone', {\n  backend: {\n    servicemonitor: true,\n    metricsPath: '/metrics',  // optional, defaults to '/metrics'\n  },\n  frontend: {\n    servicemonitor: true,\n    metricsPort: 9090,  // optional, defaults to service port\n  },\n});\n```\n\n**Note:** You must instrument your Plone backend/frontend to expose metrics at the configured endpoint. For Volto/Node.js frontends, consider using [prom-client](https://www.npmjs.com/package/prom-client) or [express-prometheus-middleware](https://www.npmjs.com/package/express-prometheus-middleware).\n\n## Requirements\n- **kubectl** - [Install kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl)\n- **Node.js 16+** (for TypeScript/JavaScript) - [Install Node.js](https://nodejs.org/)\n- **Python 3.8+** (for Python) - [Install Python](https://www.python.org/)\n- **Kubernetes cluster** (local or cloud)\n\nFor detailed setup instructions, see [Setup Prerequisites](https://bluedynamics.github.io/cdk8s-plone/how-to/setup-prerequisites.html).\n\n## Development\n\nThis project uses [Projen](https://projen.io/) for project management.\n\n```bash\n# Install dependencies\nnpm install\n\n# Run tests\nnpm test\n\n# Build\nnpm run build\n\n# Update project configuration\n# Edit .projenrc.ts, then run:\nnpx projen\n```\n\nFor detailed development instructions, see [CONTRIBUTING.md](./CONTRIBUTING.md) (if available).\n\n## Resources\n\n- [CDK8S Documentation](https://cdk8s.io/)\n- [Plone CMS](https://plone.org/)\n- [kube-httpcache](https://github.com/mittwald/kube-httpcache) (for HTTP caching)\n- [CloudNativePG](https://cloudnative-pg.io/) (for PostgreSQL management)\n\n## License\n\n[Apache 2.0](LICENSE)\n\n## Maintainers\n\nMaintained by [Blue Dynamics Alliance](https://github.com/bluedynamics)\n\n**Author:** Jens W. Klein (jk@kleinundpartner.at)\n"
   },
   "repository": {
     "type": "git",
@@ -268,7 +268,7 @@
       "base": "constructs.Construct",
       "docs": {
         "example": "new Plone(chart, 'my-plone', {\n  variant: PloneVariant.VOLTO,\n  backend: {\n    image: 'plone/plone-backend:6.0.10',\n    replicas: 3,\n  },\n  frontend: {\n    image: 'plone/plone-frontend:16.0.0',\n  },\n});",
-        "remarks": "This construct creates all necessary Kubernetes resources for running Plone:\n- Deployment(s) for backend (and optionally frontend)\n- Service(s) for network access\n- Optional PodDisruptionBudget for high availability\n\nSupports two deployment variants:\n- VOLTO: Modern React frontend with REST API backend (default)\n- CLASSICUI: Traditional server-side rendered Plone",
+        "remarks": "This construct creates all necessary Kubernetes resources for running Plone:\n- Deployment(s) for backend (and optionally frontend)\n- Service(s) for network access\n- Optional PodDisruptionBudget for high availability\n\nSupports two deployment variants:\n- VOLTO: React single-page frontend talking to the REST API backend (default)\n- BLICCA: the Plone backend renders the UI server-side and serves HTML directly",
         "stability": "stable",
         "summary": "Plone construct for deploying Plone CMS to Kubernetes."
       },
@@ -279,7 +279,7 @@
         },
         "locationInModule": {
           "filename": "src/plone.ts",
-          "line": 408
+          "line": 417
         },
         "parameters": [
           {
@@ -306,7 +306,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "src/plone.ts",
-        "line": 385
+        "line": 394
       },
       "name": "Plone",
       "properties": [
@@ -319,7 +319,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 390
+            "line": 399
           },
           "name": "backendServiceName",
           "type": {
@@ -334,7 +334,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 406
+            "line": 415
           },
           "name": "siteId",
           "type": {
@@ -344,12 +344,12 @@
         {
           "docs": {
             "stability": "stable",
-            "summary": "The deployment variant being used (VOLTO or CLASSICUI)."
+            "summary": "The deployment variant being used (VOLTO or BLICCA)."
           },
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 401
+            "line": 410
           },
           "name": "variant",
           "type": {
@@ -365,7 +365,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 396
+            "line": 405
           },
           "name": "frontendServiceName",
           "optional": true,
@@ -1471,7 +1471,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "src/plone.ts",
-        "line": 318
+        "line": 327
       },
       "name": "PloneOptions",
       "properties": [
@@ -1485,7 +1485,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 343
+            "line": 352
           },
           "name": "backend",
           "optional": true,
@@ -1504,7 +1504,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 350
+            "line": 359
           },
           "name": "frontend",
           "optional": true,
@@ -1524,7 +1524,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 358
+            "line": 367
           },
           "name": "imagePullSecrets",
           "optional": true,
@@ -1548,7 +1548,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 331
+            "line": 340
           },
           "name": "siteId",
           "optional": true,
@@ -1566,7 +1566,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 337
+            "line": 346
           },
           "name": "variant",
           "optional": true,
@@ -1585,7 +1585,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/plone.ts",
-            "line": 324
+            "line": 333
           },
           "name": "version",
           "optional": true,
@@ -1996,7 +1996,7 @@
           "docs": {
             "remarks": "Deploys both frontend and backend services.",
             "stability": "stable",
-            "summary": "Volto variant: ReactJS frontend (Volto) with REST API backend."
+            "summary": "Volto variant: ReactJS single-page frontend (Volto) talking to the Plone REST API."
           },
           "name": "VOLTO"
         },
@@ -2004,7 +2004,15 @@
           "docs": {
             "remarks": "Deploys only the backend service.",
             "stability": "stable",
-            "summary": "Classic UI variant: Traditional Plone with server-side rendering."
+            "summary": "Blicca variant: the Plone backend renders the UI server-side and serves the HTML directly."
+          },
+          "name": "BLICCA"
+        },
+        {
+          "docs": {
+            "deprecated": "Renamed to {@link BLICCA }. Kept for backward compatibility and selects the\nsame backend-only deployment. Existing configuration using `CLASSICUI` (or the literal\nvalue `'classicui'`) keeps working unchanged. Will be removed in a future major release.",
+            "stability": "deprecated",
+            "summary": "Deprecated alias for the Blicca variant (formerly \"Classic UI\")."
           },
           "name": "CLASSICUI"
         }
@@ -3110,6 +3118,6 @@
       "symbolId": "src/vinylcache:VinylCacheToleration"
     }
   },
-  "version": "0.1.41",
-  "fingerprint": "9JNj9g1Gsl0Yh2odzC98CZU0Me9K8FN1awRs39FwVc0="
+  "version": "0.1.42",
+  "fingerprint": "D9/SxjjIZbxf8BCRqRbR2qAlxXiZY5YCDvyQS6+zHXQ="
 }

package/API.md

@@ -12,8 +12,8 @@ This construct creates all necessary Kubernetes resources for running Plone:
 - Optional PodDisruptionBudget for high availability
 
 Supports two deployment variants:
-- VOLTO: Modern React frontend with REST API backend (default)
-- CLASSICUI: Traditional server-side rendered Plone
+- VOLTO: React single-page frontend talking to the REST API backend (default)
+- BLICCA: the Plone backend renders the UI server-side and serves HTML directly
 
 *Example*
 
@@ -150,7 +150,7 @@ Any object.
 | <code><a href="#@bluedynamics/cdk8s-plone.Plone.property.node">node</a></code> | <code>constructs.Node</code> | The tree node. |
 | <code><a href="#@bluedynamics/cdk8s-plone.Plone.property.backendServiceName">backendServiceName</a></code> | <code>string</code> | Name of the backend Kubernetes service. |
 | <code><a href="#@bluedynamics/cdk8s-plone.Plone.property.siteId">siteId</a></code> | <code>string</code> | The Plone site ID in ZODB. |
-| <code><a href="#@bluedynamics/cdk8s-plone.Plone.property.variant">variant</a></code> | <code><a href="#@bluedynamics/cdk8s-plone.PloneVariant">PloneVariant</a></code> | The deployment variant being used (VOLTO or CLASSICUI). |
+| <code><a href="#@bluedynamics/cdk8s-plone.Plone.property.variant">variant</a></code> | <code><a href="#@bluedynamics/cdk8s-plone.PloneVariant">PloneVariant</a></code> | The deployment variant being used (VOLTO or BLICCA). |
 | <code><a href="#@bluedynamics/cdk8s-plone.Plone.property.frontendServiceName">frontendServiceName</a></code> | <code>string</code> | Name of the frontend Kubernetes service. |
 
 ---
@@ -201,7 +201,7 @@ public readonly variant: PloneVariant;
 
 - *Type:* <a href="#@bluedynamics/cdk8s-plone.PloneVariant">PloneVariant</a>
 
-The deployment variant being used (VOLTO or CLASSICUI).
+The deployment variant being used (VOLTO or BLICCA).
 
 ---
 
@@ -2835,25 +2835,37 @@ Plone deployment variants.
 
 | **Name** | **Description** |
 | --- | --- |
-| <code><a href="#@bluedynamics/cdk8s-plone.PloneVariant.VOLTO">VOLTO</a></code> | Volto variant: ReactJS frontend (Volto) with REST API backend. |
-| <code><a href="#@bluedynamics/cdk8s-plone.PloneVariant.CLASSICUI">CLASSICUI</a></code> | Classic UI variant: Traditional Plone with server-side rendering. |
+| <code><a href="#@bluedynamics/cdk8s-plone.PloneVariant.VOLTO">VOLTO</a></code> | Volto variant: ReactJS single-page frontend (Volto) talking to the Plone REST API. |
+| <code><a href="#@bluedynamics/cdk8s-plone.PloneVariant.BLICCA">BLICCA</a></code> | Blicca variant: the Plone backend renders the UI server-side and serves the HTML directly. |
+| <code><a href="#@bluedynamics/cdk8s-plone.PloneVariant.CLASSICUI">CLASSICUI</a></code> | Deprecated alias for the Blicca variant (formerly "Classic UI"). |
 
 ---
 
 ##### `VOLTO` <a name="VOLTO" id="@bluedynamics/cdk8s-plone.PloneVariant.VOLTO"></a>
 
-Volto variant: ReactJS frontend (Volto) with REST API backend.
+Volto variant: ReactJS single-page frontend (Volto) talking to the Plone REST API.
 
 Deploys both frontend and backend services.
 
 ---
 
 
-##### `CLASSICUI` <a name="CLASSICUI" id="@bluedynamics/cdk8s-plone.PloneVariant.CLASSICUI"></a>
+##### `BLICCA` <a name="BLICCA" id="@bluedynamics/cdk8s-plone.PloneVariant.BLICCA"></a>
 
-Classic UI variant: Traditional Plone with server-side rendering.
+Blicca variant: the Plone backend renders the UI server-side and serves the HTML directly.
 
 Deploys only the backend service.
 
 ---
 
+
+##### ~~`CLASSICUI`~~ <a name="CLASSICUI" id="@bluedynamics/cdk8s-plone.PloneVariant.CLASSICUI"></a>
+
+- *Deprecated:* Renamed to {@link BLICCA }. Kept for backward compatibility and selects the
+same backend-only deployment. Existing configuration using `CLASSICUI` (or the literal
+value `'classicui'`) keeps working unchanged. Will be removed in a future major release.
+
+Deprecated alias for the Blicca variant (formerly "Classic UI").
+
+---
+

package/CLAUDE.md

@@ -4,7 +4,7 @@ This document provides context and guidelines for Claude Code when working on th
 
 ## Project Overview
 
-**cdk8s-plone** is a TypeScript/Python library for deploying Plone CMS to Kubernetes using CDK8S constructs. It provides type-safe infrastructure as code with support for Volto (React frontend) and Classic UI deployments.
+**cdk8s-plone** is a TypeScript/Python library for deploying Plone CMS to Kubernetes using CDK8S constructs. It provides type-safe infrastructure as code with support for Volto (React frontend) and Blicca (server-side rendered, formerly Classic UI) deployments.
 
 ## Git Workflow
 

package/README.md

@@ -11,7 +11,7 @@
 cdk8s-plone provides CDK8S constructs for deploying [Plone CMS](https://plone.org/) on Kubernetes. Define your infrastructure using TypeScript or Python and generate Kubernetes manifests automatically.
 
 **Key Features:**
-- 🚀 Supports Volto (modern React frontend) and Classic UI
+- 🚀 Supports Volto (React frontend) and Blicca (formerly Classic UI)
 - 📦 High availability with configurable replicas
 - ⚡ Optional Varnish HTTP caching via kube-httpcache (`PloneHttpcache`) or cloud-vinyl VinylCache operator (`PloneVinylCache`)
 - 🔧 Fine-grained resource and probe configuration
@@ -75,14 +75,14 @@ kubectl apply -f dist/
 
 Complete working examples are available in the [`examples/`](examples/) directory:
 
-- **[Production Volto](examples/production-volto/)** - Production-ready Plone 6 deployment with modern UI:
+- **[Production Volto](examples/production-volto/)** - Production-ready Plone 6 deployment with the React single-page frontend:
   - Volto frontend (React) + REST API backend
   - PostgreSQL with RelStorage (CloudNativePG or Bitnami)
   - Varnish HTTP caching with kube-httpcache
   - Ingress support (Traefik/Kong) with TLS
 
-- **[Classic UI](examples/classic-ui/)** - Traditional Plone deployment with server-side rendering:
-  - Classic UI (traditional Plone interface)
+- **[Blicca](examples/blicca/)** - Plone deployment with server-side rendering (formerly Classic UI):
+  - Blicca (backend renders the UI, no separate frontend)
   - PostgreSQL with RelStorage (CloudNativePG or Bitnami)
   - Varnish HTTP caching with kube-httpcache
   - Ingress support (Traefik/Kong) with TLS

package/documentation/sources/explanation/architecture.md

@@ -21,19 +21,20 @@ cdk8s-plone provides CDK8S constructs for deploying Plone CMS on Kubernetes. The
 
 cdk8s-plone supports two deployment variants:
 
-**Volto (Modern)**
+**Volto (React single-page frontend)**
 - React-based frontend (Volto)
 - REST API backend (Plone)
 - Separate services for frontend and backend
-- Modern user experience
 - Headless CMS architecture
 
-**Classic UI (Traditional)**
-- Server-side rendered Plone
+**Blicca (server-side rendered)**
+- The Plone backend renders the UI and serves HTML directly
 - Single integrated service
-- Traditional Plone experience
 - Simpler deployment model
 
+Blicca is the new name for the variant Plone formerly called "Classic UI".
+Both approaches are equally current; they differ in where rendering happens, not in how modern they are.
+
 ### High availability
 
 **Replica Management**
@@ -251,7 +252,7 @@ For a typical Volto deployment, cdk8s-plone creates:
 - Better resource utilization
 - Clear separation of concerns
 
-**When to use Classic UI:**
+**When to use Blicca:**
 - Simpler deployment model
 - Lower resource requirements
 - Legacy integrations

package/documentation/sources/explanation/features.md

@@ -19,17 +19,19 @@ Complete overview of cdk8s-plone features and capabilities.
 
 cdk8s-plone supports two deployment modes to match your requirements:
 
-**Volto (Modern React Frontend)**
-- Modern React-based user interface
+**Volto (React single-page frontend)**
+- React-based user interface
 - Headless CMS architecture
 - Separate frontend and backend services
-- Best for: New projects, modern UX requirements, API-first architectures
+- Best for: API-first architectures, SPA frontends
 
-**Classic UI (Traditional Plone)**
-- Server-side rendered interface
+**Blicca (server-side rendered Plone)**
+- The Plone backend renders the UI and serves HTML directly
 - Integrated single-service deployment
-- Traditional Plone experience
-- Best for: Legacy migrations, existing add-ons, simpler deployments
+- Best for: single-service setups, legacy migrations, existing add-ons
+
+Blicca is the new name for the variant Plone formerly called "Classic UI".
+Both are equally current; they differ in their rendering approach.
 
 See {doc}`architecture` for a deeper architectural comparison of the two variants.
 

package/documentation/sources/how-to/{deploy-classic-ui.md → deploy-blicca.md}

@@ -1,37 +1,40 @@
 ---
 myst:
   html_meta:
-    "description": "Deploy the Classic UI example: server-side rendered Plone with PostgreSQL, Varnish caching, and ingress with TLS."
-    "property=og:description": "Deploy the Classic UI example: server-side rendered Plone with PostgreSQL, Varnish caching, and ingress with TLS."
-    "property=og:title": "Deploy Classic UI example"
-    "keywords": "Plone, cdk8s, Kubernetes, Classic UI, PostgreSQL, Varnish, ingress"
+    "description": "Deploy the Blicca example: server-side rendered Plone with PostgreSQL, Varnish caching, and ingress with TLS."
+    "property=og:description": "Deploy the Blicca example: server-side rendered Plone with PostgreSQL, Varnish caching, and ingress with TLS."
+    "property=og:title": "Deploy Blicca example"
+    "keywords": "Plone, cdk8s, Kubernetes, Blicca, Classic UI, PostgreSQL, Varnish, ingress"
 ---
 
-# Deploy Classic UI example
+# Deploy Blicca example
 
-This guide shows you how to deploy the Classic UI example to your Kubernetes cluster.
+This guide shows you how to deploy the Blicca example to your Kubernetes cluster.
+
+Blicca is the new name for what Plone formerly called "Classic UI".
 
 ## What you'll deploy
 
-The [Classic UI example](https://github.com/bluedynamics/cdk8s-plone/tree/main/examples/classic-ui) provides traditional Plone with server-side rendering:
+The [Blicca example](https://github.com/bluedynamics/cdk8s-plone/tree/main/examples/blicca) provides Plone with server-side rendering:
 
-- **Plone 6.1 Classic UI** (traditional interface, no separate frontend)
+- **Plone 6.1 Blicca** (backend renders the UI, no separate frontend)
 - **PostgreSQL** with RelStorage (CloudNativePG or Bitnami)
 - **Varnish HTTP caching** with kube-httpcache
 - **Ingress** with TLS (Traefik or Kong)
 - **Simpler architecture** (single backend service)
 
-## Classic UI vs Volto
+## Blicca vs Volto
 
-| Feature | Classic UI | Volto |
+| Feature | Blicca | Volto |
 |---------|-----------|-------|
 | **Architecture** | Single backend | Frontend + Backend |
 | **Rendering** | Server-side | Client-side (React) |
 | **Deployment** | Simpler | More complex |
-| **Best for** | Migrations, intranets | Modern projects |
+| **Best for** | Single-service setups, migrations | API-first projects, SPA frontends |
 
 :::{tip}
-Choose Classic UI if you're migrating from older Plone versions or need specific Classic UI add-ons. For new projects, consider [Volto](deploy-production-volto.md).
+Choose Blicca if you want a single backend service without a separate frontend, or if you need Blicca-specific add-ons.
+For the React single-page frontend approach, consider [Volto](deploy-production-volto.md).
 :::
 
 ## Prerequisites
@@ -49,7 +52,7 @@ See [Setup Prerequisites](setup-prerequisites.md) for detailed instructions.
 
 ```shell
 git clone https://github.com/bluedynamics/cdk8s-plone.git
-cd cdk8s-plone/examples/classic-ui
+cd cdk8s-plone/examples/blicca
 ```
 
 ## Step 2: Install dependencies
@@ -91,7 +94,8 @@ DATABASE=cloudnativepg
 ```
 
 :::{note}
-Classic UI only needs one image (backend). There's no frontend image configuration.
+Blicca only needs one image (backend).
+There's no frontend image configuration.
 :::
 
 ## Step 5: Generate manifests
@@ -100,28 +104,28 @@ Classic UI only needs one image (backend). There's no frontend image configurati
 npm run synth
 ```
 
-Creates `dist/plone-classic.k8s.yaml` (~27 KB, smaller than Volto's 32 KB).
+Creates `dist/plone-blicca.k8s.yaml` (~27 KB, smaller than Volto's 32 KB).
 
 ## Step 6: Review manifests
 
 ```shell
 # Count resources
-grep "^kind:" dist/plone-classic.k8s.yaml | sort | uniq -c
+grep "^kind:" dist/plone-blicca.k8s.yaml | sort | uniq -c
 
 # Dry run
-kubectl apply --dry-run=client -f dist/plone-classic.k8s.yaml
+kubectl apply --dry-run=client -f dist/plone-blicca.k8s.yaml
 ```
 
 ## Step 7: Deploy
 
 ```shell
-kubectl apply -f dist/plone-classic.k8s.yaml
+kubectl apply -f dist/plone-blicca.k8s.yaml
 ```
 
 Or to a specific namespace:
 
 ```shell
-kubectl apply -f dist/plone-classic.k8s.yaml -n plone
+kubectl apply -f dist/plone-blicca.k8s.yaml -n plone
 ```
 
 ## Step 8: Monitor deployment
@@ -137,7 +141,7 @@ kubectl wait --for=condition=ready pod \
 ```
 
 :::{note}
-Classic UI deploys fewer pods than Volto (no frontend pods).
+Blicca deploys fewer pods than Volto (no frontend pods).
 :::
 
 ## Step 9: Verify services
@@ -147,7 +151,7 @@ kubectl get svc -l app.kubernetes.io/part-of=plone
 ```
 
 You should see:
-- `plone-backend` (Classic UI service)
+- `plone-backend` (Blicca service)
 - `plone-httpcache` (Varnish cache)
 - Database service
 
@@ -174,17 +178,17 @@ Once DNS and TLS are ready:
    - **Site ID**: `Plone`
    - **Title**: Your site name
    - **Language**: Select language
-   - **Add-ons**: Choose Classic UI add-ons
+   - **Add-ons**: Choose Blicca add-ons
 4. Click "Create Plone Site"
 
 ## Key differences from Volto
 
 ### Architecture
 
-Classic UI routing is simpler - all traffic goes to the backend:
+Blicca routing is simpler - all traffic goes to the backend:
 
 ```
-Traffic → Ingress → Varnish → Plone Backend (Classic UI)
+Traffic → Ingress → Varnish → Plone Backend (Blicca)
 ```
 
 Compared to Volto:
@@ -195,7 +199,7 @@ Traffic → Ingress → {Varnish → Frontend, Backend}
 
 ### Ingress routes
 
-Classic UI uses virtual host rewriting for direct backend access:
+Blicca uses virtual host rewriting for direct backend access:
 
 - **Cached**: Routes through Varnish to backend
 - **Uncached**: Direct to backend with VirtualHostBase rewrite
@@ -225,7 +229,7 @@ Common issues:
 - Memory limits too low
 - Image pull errors
 
-### Classic UI interface not loading
+### Blicca interface not loading
 
 1. Check if backend pods are running:
    ```shell
@@ -244,14 +248,14 @@ Common issues:
 
 ### Add-on compatibility
 
-Some add-ons are Volto-specific. For Classic UI:
-- Use Classic UI themes (not Volto themes)
-- Check add-on compatibility with Plone 6 Classic UI
+Some add-ons are Volto-specific. For Blicca:
+- Use Blicca themes (not Volto themes)
+- Check add-on compatibility with Plone 6 Blicca
 - Avoid Volto-specific frontend add-ons
 
 ## Migrating to Volto
 
-If you want to migrate from Classic UI to Volto later:
+If you want to migrate from Blicca to Volto later:
 
 1. Keep your backend deployment (same configuration)
 2. Add Volto frontend from the [Volto example](deploy-production-volto.md)
@@ -268,7 +272,7 @@ Edit `main.ts` to customize:
 
 ```typescript
 const plone = new Plone(this, 'plone', {
-  variant: PloneVariant.CLASSICUI,
+  variant: PloneVariant.BLICCA,
   backend: {
     image: 'plone/plone-backend:6.1.3',
     replicas: 2,
@@ -281,9 +285,9 @@ const plone = new Plone(this, 'plone', {
 
 ### Varnish caching
 
-Edit `config/varnish.tpl.vcl` for caching rules specific to Classic UI.
+Edit `config/varnish.tpl.vcl` for caching rules specific to Blicca.
 
-Classic UI VCL is simpler than Volto's - all traffic routes to one backend.
+Blicca VCL is simpler than Volto's - all traffic routes to one backend.
 
 ## Scaling
 
@@ -298,14 +302,14 @@ backend: {
 Then:
 ```shell
 npm run synth
-kubectl apply -f dist/plone-classic.k8s.yaml
+kubectl apply -f dist/plone-blicca.k8s.yaml
 ```
 
 ## Performance
 
-Classic UI performance characteristics:
+Blicca performance characteristics:
 
-- **Server-side rendering** can be slower than Volto's client-side
+- **Server-side rendering** moves rendering work to the backend, so Varnish caching matters
 - **Varnish caching** is critical for performance
 - **Database** is the main bottleneck (use CloudNativePG for HA)
 - **Fewer HTTP requests** than Volto (no separate frontend API calls)
@@ -313,18 +317,18 @@ Classic UI performance characteristics:
 ## Cleanup
 
 ```shell
-kubectl delete -f dist/plone-classic.k8s.yaml
+kubectl delete -f dist/plone-blicca.k8s.yaml
 ```
 
 ## Next steps
 
 - Follow {doc}`enable-prometheus-monitoring` to add Prometheus monitoring.
 - Configure [CloudNativePG backups](https://cloudnative-pg.io/documentation/).
-- Customize the Classic UI theme through [Plone 6 Classic UI documentation](https://6.docs.plone.org/classic-ui/).
+- Customize the theme through the [Plone 6 Classic UI documentation](https://6.docs.plone.org/classic-ui/) (upstream docs; Blicca is the new name for Classic UI).
 
 ## See also
 
-- {doc}`deploy-production-volto` — For the modern React UI.
+- {doc}`deploy-production-volto` — For the React single-page frontend.
 - {doc}`setup-prerequisites` — Cluster requirements.
 - {doc}`/reference/configuration-options` — API reference.
 - [Plone 6 Classic UI documentation](https://6.docs.plone.org/classic-ui/)

package/documentation/sources/how-to/deploy-production-volto.md

@@ -324,6 +324,6 @@ kubectl delete -f dist/plone-example.k8s.yaml
 
 ## See also
 
-- {doc}`deploy-classic-ui` — For the traditional Plone interface.
+- {doc}`deploy-blicca` — For the server-side rendered Plone UI.
 - {doc}`setup-prerequisites` — Detailed cluster setup.
 - {doc}`/reference/configuration-options` — API reference.

package/documentation/sources/how-to/index.md

@@ -40,7 +40,7 @@ maxdepth: 1
 titlesonly: true
 ---
 deploy-production-volto
-deploy-classic-ui
+deploy-blicca
 deploy-with-vinyl-cache
 ```
 

package/documentation/sources/reference/api/index.md

@@ -15,7 +15,7 @@ Complete API reference for cdk8s-plone constructs, generated from TypeScript sou
 
 The cdk8s-plone library provides the following main constructs:
 
-- **Plone**: Main construct for deploying Plone CMS with support for both Volto (React frontend) and Classic UI variants
+- **Plone**: Main construct for deploying Plone CMS with support for both Volto (React frontend) and Blicca (server-side rendered) variants
 - **PloneHttpcache**: HTTP caching layer using Varnish for improved performance
 
 ## Language support