pom://theme/modules: active POM module summary
This JSON resource reports the POM Theme module configuration visible to the connected site. Use it to answer a different question from the shortcode catalog: not merely “which tags exist?”, but “which POM modules are enabled and which assets do they declare?”
Each item can contain:
| Field | Meaning |
|---|---|
module |
POM Theme module identifier. |
label |
Human-readable module name. |
icon |
Builder icon metadata when declared. |
shortcode |
Tag that renders the module. |
deps |
Declared script and style handles. |
enabled |
Whether the module is active in the runtime. |
If the active theme does not expose the module runtime, the resource returns an empty array. That is a compatibility signal, not permission to assume every web_* component is available.
Selecting a component
Use this resource when a request depends on a specific POM capability such as a gallery, listing, map, carousel, or form. Confirm that the module is enabled, then read its shortcode resource for authoring parameters. Asset handles are descriptive runtime metadata; clients do not enqueue them or write them into page content.
An enabled module can still require site configuration or meaningful content before it renders usefully. Conversely, a registered shortcode with no matching module entry may come from WordPress or another plugin. The source field in the shortcode schema resolves that distinction.
Re-read the summary after module or theme configuration changes. Do not cache it as a cross-site product catalog.
Related guides: shortcode catalog, one shortcode schema, and layout guide.