docs: Move content about Pelican frontend to that repository

docs/tasks/checks/compiled-release.rst

@@ -1,9 +1,6 @@
 Compiled release-level
 ======================
 
-Backend
--------
-
 #. Determine the type of check (see :ref:`repository-structure`).
 #. Find a check under the corresponding ``contracting_process/resource_level`` sub-directory to copy as a starting point.
 #. Add the check to the ``contracting_process/resource_level/definitions.py`` file. For example:
@@ -57,13 +54,13 @@ An empty ``result`` dict looks like:
    :end-at: }
 
 Example
-~~~~~~~
+-------
 
 .. literalinclude:: ../../../contracting_process/resource_level/coherent/milestone_status.py
    :language: python
 
 Storage
-~~~~~~~
+-------
 
 The results for each item are stored in a single row in the ``resource_level_check`` table. A stored ``result`` value looks like (only two entries in the ``checks`` array are shown):
 
@@ -106,9 +103,3 @@ The results for each item are stored in a single row in the ``resource_level_che
            }
        }
    }
-
-Frontend
---------
-
-Pelican frontend automatically supports new compiled release-level checks with known check types.
-

docs/tasks/checks/dataset.rst

@@ -1,9 +1,6 @@
 Dataset-level
 =============
 
-Backend
--------
-
 #. Determine the type of check (see :ref:`repository-structure`).
 #. Find a check under the corresponding ``dataset`` sub-directory to copy as a starting point.
 #. Add the check to the ``dataset/definitions.py`` file. For example:
@@ -54,13 +51,6 @@ An empty ``result`` dict looks like:
    :end-at: }
 
 Storage
-~~~~~~~
+-------
 
 The result of each check for a given dataset is stored in a single row in the ``dataset_level_check`` table.
-
-Frontend
---------
-
-#. Update ``frontend/src/components/DatasetLevelSection.vue`` and register the check.
-#. Register the check in ``frontend/src/plugins/datasetMixins.js``.
-

docs/tasks/checks/field.rst

@@ -1,9 +1,6 @@
 Field-level
 ===========
 
-Backend
--------
-
 #. Determine the type of check (see :ref:`repository-structure`).
 #. Find a check under the corresponding ``contracting_process/field_level`` sub-directory to copy as a starting point.
 #. Update the ``_definitions()`` function to assign the check to fields in the ``contracting_process/field_level/definitions.py`` file.
@@ -33,13 +30,13 @@ An empty ``result`` dict looks like:
    :end-at: }
 
 Example
-~~~~~~~
+-------
 
 .. literalinclude:: ../../../contracting_process/field_level/coverage/exists.py
    :language: python
 
 Storage
-~~~~~~~
+-------
 
 The results for each item are stored in a single row in the ``field_level_check`` table. A stored ``result`` value looks like (only one entry in the ``checks`` array is shown):
 
@@ -81,8 +78,3 @@ The results for each item are stored in a single row in the ``field_level_check`
            ]
        }
    }
-
-Frontend
---------
-
-Pelican frontend automatically supports new field-level checks.

docs/tasks/checks/index.rst

@@ -1,8 +1,6 @@
 Add checks
 ==========
 
-In all cases, you must update the ``frontend/src/messages/en.js`` file in `Pelican frontend <https://pelican-frontend.readthedocs.io/en/latest/>`__.
-
 .. toctree::
    :maxdepth: 1
 

docs/tasks/checks/time-based.rst

@@ -1,9 +1,6 @@
 Time-based
 ==========
 
-Backend
--------
-
 #. Find a check under the ``time_variance`` directory to copy as a starting point.
 #. Add the check to the ``time_variance/definitions.py`` file. For example:
 
@@ -40,11 +37,6 @@ The accumulator is initialized as:
    :end-at: }
 
 Storage
-~~~~~~~
+-------
 
 The result of each check for a given dataset is stored in a single row in the ``time_variance_level_check`` table.
-
-Frontend
---------
-
-Pelican frontend automatically supports new time-based checks.