Replace this paragraph with a description of your SPA.
Designed and produced by Penrith Beacon Communications (PBC).
This Settings modal is a standard WCP settings screen, part of the Widget Context Protocol (WCP) theme and settings system.
More about the Widget Context Protocol can be found at widgetcontextprotocol.com.
The Widget Context Protocol is an open protocol for embedding containerised widgets into any host application — free to implement. It defines a lightweight runtime communication layer between widget and host, covering theming, data exchange, and widget lifecycle management. The four pillars of the WCP ecosystem are outlined below.
While WCP is designed with containerised widgets at its core, many of its design patterns — CSS token systems, portable theme formats, and interface constructions — translate naturally to any web-delivered environment. These conventions apply equally within a containerised widget and across conventional websites and intranets, requiring no containerisation to deliver their value.
The umbrella site for the entire WCP ecosystem:
widgetcontextprotocol.comWCP
The canonical specification. Covers all mandatory endpoints, the postMessage theme API, the widget manifest format, WCP versions, and the full CSS custom-property token set that drives WCP-compliant theming.
WCPP
The WCP Portability Protocol. Defines how WCP artefacts — themes and application distributables — are packaged, transported, and reconstructed on a different machine. The .wcpt theme file format used by this application is defined here.
Dev
Practical implementation reference for widget authors. Endpoint scaffolding, theme adoption patterns, the user theme management panel, worked examples, and compliance checklists for building WCP-compliant widgets.
dev.widgetcontextprotocol.comAI
An AI-assisted build chain guiding developers through design, Docker publication, and GitHub release workflows for WCP-compliant widgets — from concept to distributable in a single pipeline.
ai.widgetcontextprotocol.com