Fix broken link to GenericSetup, add a placeholder for config-registry docs

Author: MrTango

docs/backend/config-registry.md

@@ -0,0 +1,25 @@
+---
+myst:
+  html_meta:
+    "description": ""
+    "property=og:description": ""
+    "property=og:title": "Config Registry"
+    "keywords": ""
+---
+
+(backend-config-registry-label)=
+
+# Config Registry
+
+```{todo}
+Explain how plone.registry / plone.app.registry and GenericSetup work together.
+Provide examples how to import and export Plone settings.
+```
+
+(backend-config-registry-generic-setup-label)=
+
+## GenericSetup
+
+```{todo}
+Explain how GenericSetup works.
+```

docs/classic-ui/layers.md

@@ -59,6 +59,10 @@ Then views and viewlets from your product can be enabled on the site instance us
 
 If you want to override a view or a viewlet unconditionally for all sites without the add-on product installer support, you need to use `overrides.zcml`.
 
+```{todo}
+Explain how to use an `overrides.zcml`.
+```
+
 
 (classic-ui-creating-a-layer-label)=
 

docs/classic-ui/views.md

@@ -173,7 +173,8 @@ You need to declare the `browser` namespace in your `configure.zcml` to use `bro
 ```
 
 The view in question is registered against a {ref}`layer <classic-ui-layers-label>`.
-It will be available after restart, after you run {doc}`Add/remove in Site setup </develop/addons/components/genericsetup>`.
+It will be available after restart, after running the {ref}`GenericSetup profile <backend-config-registry-generic-setup-label>`.
+
 
 ```{todo}
 Fix the preceding link to "Add/remove in Site setup".
@@ -508,7 +509,7 @@ If you need to override templates in core Plone or in an existing add-on, you ca
     To override a particular file, first determine its canonical filename.
     It is defined as the path relative to the package within which the file is located.
     Directory separators are replaced with dots.
-    
+
     Suppose you want to override `plone/app/layout/viewlets/logo.pt`.
 
     You would use the filename `plone.app.layout.viewlets.logo.pt`.
@@ -540,7 +541,7 @@ As such, you will have the following browser layer interface and its registratio
 
     ```python
     from plone.theme.interfaces import IDefaultPloneLayer
-    
+
     class ICollectiveAwesomeaddon(IDefaultPloneLayer):
       """ A marker interface for the theme layer
       """
@@ -564,15 +565,15 @@ As such, you will have the following browser layer interface and its registratio
         xmlns="http://namespaces.zope.org/zope"
         xmlns:browser="http://namespaces.zope.org/browser"
         i18n_domain="collective.awesomeaddon">
-    
+
       <browser:page
           name="register"
           class=".customregistration.CustomRegistrationForm"
           permission="cmf.AddPortalMember"
           for="plone.app.layout.navigation.interfaces.INavigationRoot"
           layer="collective.awesomeaddon.interfaces.ICollectiveAwesomeaddon"
           />
-    
+
     </configure>
     ```
 
@@ -585,7 +586,7 @@ As such, you will have the following browser layer interface and its registratio
 
     ```
     from plone.app.users.browser.register import RegistrationForm
-    
+
     class CustomRegistrationForm(RegistrationForm):
       """ Subclass the standard registration form
       """