Skip to content

Commit 4e334b6

Browse files
committed
Glossary termify configuration registry and update definition
1 parent dddecb7 commit 4e334b6

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

docs/glossary.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -168,15 +168,19 @@ Add-on
168168
169169
Volto configuration loader
170170
A function with signature `config => config`.
171-
It gets the Volto Configuration registry, and it must return it back after mutating it.
172-
It is similar to `GenericSetup` profiles in Plone Backend.
171+
It gets the Volto configuration registry, and it must return it back after mutating it.
172+
It is similar to `GenericSetup` profiles in the Plone backend.
173173
An add-on must provide a default configuration loader that is always loaded when Volto runs.
174174
An add-on can have multiple configuration loaders, and they can be loaded optionally from the Volto configuration.
175175
176-
Configuration registry (Volto)
177-
A singleton object modeled using JavaScript modules.
176+
Configuration registry
177+
In Plone and in general, the configuration registry is where resources are registered for an application.
178+
179+
In Volto, it is a singleton object modeled using JavaScript modules.
178180
It is accessible from the Volto project by importing the module `@plone/volto/config` with `import registry from '@plone/volto/config'`.
179181
It contains the configuration of the Volto app.
182+
183+
In Plone core, [`plone.app.registry`](https://pypi.org/project/plone.app.registry/) provides Plone UI and `GenericSetup` integration for [`plone.registry`](https://pypi.org/project/plone.registry/), which in turn implements a configuration registry for Zope applications.
180184
181185
Shadowing (Volto)
182186
Webpack provides an "alias" mechanism, where the path for a module can be aliased to another module.

0 commit comments

Comments
 (0)