Added related content to backend docs (#2032)

* Added related content to backend docs

* Added related content to classic ui docs

* Apply suggestions from code review

Co-authored-by: Steve Piercy <web@stevepiercy.com>

* Remove related content section from zodb.md

* Remove  content types from documentation

Removed duplicate related content references.

* changed see also label to doc

---------

Co-authored-by: Steve Piercy <web@stevepiercy.com>

Author: boss6825

docs/backend/indexing.md

@@ -226,3 +226,7 @@ Indexes the object path, such as `/news/news-item-1`.
 ## `Subject` (`KeywordIndex`)
 
 Indexes the `Subject` field which contains a list of object categories.
+
+## Related content
+
+-   {doc}`/backend/search`

docs/backend/search.md

@@ -35,3 +35,6 @@ Help us [Migrate content from v5 "Queries, Search And Indexing" #1730](https://g
 
 ## Querystring
 
+## Related content
+
+-   {doc}`/backend/indexing`

docs/backend/subscribers.md

@@ -170,3 +170,9 @@ The DCWorkflow events are low-level events that can tell you a lot about the pre
 `zope.processlifetime.IProcessStarting` is triggered after the component registry has been loaded and Zope is starting up.
 
 `zope.processlifetime.IDatabaseOpened` is triggered after the main ZODB database has been opened.
+
+## Related content
+
+-   {doc}`/backend/behaviors`
+-   {doc}`/backend/content-types/index`
+

docs/backend/traversal-acquisition.md

@@ -30,7 +30,7 @@ If not explicitly given, at the end a default view is looked up.
 This can be a registered page template, a callable view class, or a REST API endpoint.
 
 ```{seealso}
-{ref}`Chapter Views <classic-ui-views-label>`
+{doc}`/classic-ui/views`
 ```
 
 In code, traversal can be achieved by using the `restrictedTraverse` and `unrestrictedTraverse` methods of content objects.
@@ -87,3 +87,10 @@ For example, if object `A` contains object `B`, and object `A` has a property `x
 -   About traversal: [Zope Developers Handbook, Chapter Object Publishing](https://zope.readthedocs.io/en/latest/zdgbook/ObjectPublishing.html)
 -   About acquisition: [Zope Developers Handbook, Chapter Acquisition](https://zope.readthedocs.io/en/latest/zdgbook/Acquisition.html)
 ```
+
+## Related content
+
+-   {doc}`/backend/portal-actions`
+-   {doc}`/backend/security`
+-   {doc}`/classic-ui/views`
+

docs/classic-ui/forms.md

@@ -273,3 +273,9 @@ In your `configure.zcml`:
 
 </configure>
 ```
+
+## Related content
+    
+-   {doc}`/backend/fields`
+-   {doc}`/backend/schemas`
+-   {doc}`/backend/widgets`

docs/classic-ui/layers.md

@@ -314,3 +314,10 @@ from zope.interface import directlyProvides
 
 directlyProvides(self.portal.REQUEST, IThemeLayer)
 ```
+
+## Related content
+    
+-   {doc}`/classic-ui/theming/index`
+-   {doc}`/classic-ui/theming/create-add-on`
+-   {doc}`/classic-ui/templates`
+-   {doc}`/classic-ui/viewlets`

docs/classic-ui/viewlets.md

@@ -1048,3 +1048,11 @@ def fix_tinymce_viewlets(site):
     hidden = (x for x in hidden if x != "tinymce.configuration")
     storage.setHidden(manager, skinname, hidden)
 ```
+
+## Related content
+   
+-   {doc}`/classic-ui/layers`
+-   {doc}`/classic-ui/templates`
+-   {doc}`/classic-ui/views`
+
+

docs/classic-ui/views.md

@@ -1121,3 +1121,9 @@ return self.obj.absolute_url()  # Acquistion chain messed up, getPhysicalPath()
 ```
 
 One workaround to avoid this mess is to use `aq_inner` when accessing `self.obj` values, as described in [Dealing with view implicit acquisition problems in Plone](https://stackoverflow.com/questions/11753940/dealing-with-view-implicit-acquisition-problems-in-plone/11755348#11755348).
+
+## Related content
+
+-   {doc}`/classic-ui/layers`
+-   {doc}`/classic-ui/templates`
+-   {doc}`/classic-ui/viewlets`