Add glossary terms and Vale spellings Public UI and CMSUI.

See #7385.

plone/documentation#1975 must be merged before this PR, so that it can pull in the glossary terms via Intersphinx

Author: stevepiercy

docs/conceptual-guides/add-on-styles-loader.md

@@ -10,23 +10,23 @@ myst:
 # Add-ons styles loader
 
 Add-ons that are compatible with the `@plone/registry` may declare styles that should be loaded by the app.
-Currently the loader loads styles for both the end user interface (public UI) part, which displays content to both authenticated and anonymous users, and the content management system user interface (CMS UI) part of the app.
+Currently the loader loads styles for both the end user interface (Public UI) part, which displays content to both authenticated and anonymous users, and the content management system user interface (CMSUI) part of the app.
 
 ## Public UI styles
 
-To load public UI styles, create a file {file}`styles/main.css` at the root of your add-on package to serve as the entry point.
-This file is a `.css` file containing the styles that you want your app to load for the public UI.
+To load Public UI styles, create a file {file}`styles/main.css` at the root of your add-on package to serve as the entry point.
+This file is a `.css` file containing the styles that you want your app to load for the Public UI.
 
-## CMS UI styles
+## CMSUI styles
 
-Similar to the public UI, you can create a file {file}`styles/cmsui.css` at the root of your add-on package to serve as the entry point for the CMS UI styles.
-This file is also a CSS file containing the styles that you want your app to load for the CMS UI.
+Similar to the Public UI, you can create a file {file}`styles/cmsui.css` at the root of your add-on package to serve as the entry point for the CMSUI styles.
+This file is also a CSS file containing the styles that you want your app to load for the CMSUI.
 
 `@plone/registry` has a helper utility `createAddonsStyleLoader` which generates an add-ons loader file.
 That file contains the aggregated files from all the registered add-ons, keeping the order in which they were defined.
 
 This loader is also a `.css` file and is placed in the root of your application.
-By default, it's called {file}`publicui.css` for the public UI and {file}`cmsui.css` for the CMS UI.
+By default, it's called {file}`publicui.css` for the Public UI and {file}`cmsui.css` for the CMSUI.
 
 ```{important}
 This file is generated and maintained by `@plone/registry`.

docs/how-to-guides/routes.md

@@ -202,7 +202,7 @@ The following diagram illustrates the file structure of the `@plone/cmsui` edit
 
 In `@plone/cmsui/`, each of the files shown in the above diagram performs a specific function.
 
--   {file}`routes/layout.tsx` serves as a shared layout used as a base for CMS UI views.
+-   {file}`routes/layout.tsx` serves as a shared layout used as a base for CMSUI views.
 -   {file}`routes/edit.tsx` is the component used for `/edit` and all its subpaths.
 -   {file}`index.ts` is where the default configuration loader of the add-on calls `config.registerRoute()`.
 

docs/reference/conventions.md

@@ -22,12 +22,12 @@ We follow the mantra, "If it works, don't change it."
 
 This document highlights the differences and additions compared to Volto conventions.
 
-## Separate builds for public and CMSUI
+## Separate builds for Public UI and CMSUI
 
-We are aiming for the possibility of having two separate builds: one for the public theme and another for the CMS UI.
+We are aiming for the possibility of having two separate builds: one for the public theme called {term}`Public UI` and another for the {term}`CMSUI`.
 Thus, we need to ensure that the codebase can support this separation and have this in mind when developing new features.
 This will impose some constraints, such as avoiding the use of Tailwind CSS classes in structural components, since the public theme might not use Tailwind CSS.
-Also, the public UI cannot rely on any CMSUI-specific styles or components.
+Also, the Public UI cannot rely on any CMSUI-specific styles or components.
 
 ## Storybook
 
@@ -74,7 +74,7 @@ These styles are very simple ("vanilla") and easy to override with your own styl
 You can also use these in Volto projects by installing the `@plone/components` package.
 
 The Tailwind-based components are meant for public themes that also use Tailwind CSS, like the default Seven theme (`@plone/agave`).
-They're also used in the CMS UI, which is based on Tailwind CSS.
+They're also used in the CMSUI, which is based on Tailwind CSS.
 
 Check out the Storybook for this package at [@plone/components Storybook](https://plone-components.readthedocs.io/latest/?path=/docs/introduction--docs).
 

packages/registry/docs/conceptual-guides/add-on-styles-loader.md

@@ -10,23 +10,23 @@ myst:
 # Add-ons styles loader
 
 Add-ons that are compatible with the `@plone/registry` may declare styles that should be loaded by the app.
-Currently the loader loads styles for both the end user interface (public UI) part, which displays content to both authenticated and anonymous users, and the content management system user interface (CMS UI) part of the app.
+Currently, the loader loads styles for both the end user interface (Public UI) part, which displays content to both authenticated and anonymous users, and the content management system user interface (CMSUI) part of the app.
 
 ## Public UI Styles
 
-To load public UI styles, create a file {file}`styles/main.css` at the root of your add-on package to serve as the entry point.
-This file is a `.css` file containing the styles that you want your app to load for the public UI.
+To load Public UI styles, create a file {file}`styles/main.css` at the root of your add-on package to serve as the entry point.
+This file is a `.css` file containing the styles that you want your app to load for the Public UI.
 
-## CMS UI Styles
+## CMSUI Styles
 
-Similar to the public UI, you can create a file {file}`styles/cmsui.css` at the root of your add-on package to serve as the entry point for the CMS UI styles.
-This file is also a CSS file containing the styles that you want your app to load for the CMS UI.
+Similar to the Public UI, you can create a file {file}`styles/cmsui.css` at the root of your add-on package to serve as the entry point for the CMSUI styles.
+This file is also a CSS file containing the styles that you want your app to load for the CMSUI.
 
 `@plone/registry` has a helper utility `createAddonsStyleLoader` which generates an add-ons loader file.
 That file contains the aggregated files from all the registered add-ons, keeping the order in which they were defined.
 
 This loader is also a `.css` file and is placed in the root of your application.
-By default, it's called {file}`publicui.css` for the public UI and {file}`cmsui.css` for the CMS UI.
+By default, it's called {file}`publicui.css` for the Public UI and {file}`cmsui.css` for the CMSUI.
 
 ```{important}
 This file is generated and maintained by `@plone/registry`.

packages/registry/news/7375.documentation

@@ -0,0 +1 @@
+Use `Public UI` and `CMSUI` as official spellings. @stevepiercy