From 0781e13ba9209e817d5a35df87e05018a7a71655 Mon Sep 17 00:00:00 2001
From: Lina Wolf <48202465+linawolf@users.noreply.github.com>
Date: Tue, 19 Nov 2024 16:29:03 +0100
Subject: [PATCH] [TASK] Allow sets to be excluded from site configuration GUI
 (#576)

resolves: https://github.com/TYPO3-Documentation/Changelog-To-Doc/issues/1081
releases: main, 13.4
---
 Documentation/UserTsconfig/Options.rst | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/Documentation/UserTsconfig/Options.rst b/Documentation/UserTsconfig/Options.rst
index 99ff050..2e80979 100644
--- a/Documentation/UserTsconfig/Options.rst
+++ b/Documentation/UserTsconfig/Options.rst
@@ -1006,3 +1006,23 @@ Properties
         :typoscript:`options.showHistory.[tableName]`.
         Any value set for a single table will override the default value set for
         :typoscript:`showHistory`.
+
+    ..  confval:: hideSets
+        :name: useroptions-hideSets
+        :type: comma separated list
+
+        Hides existing :ref:`Site sets <t3coreapi:site-sets>` from the list of available
+        sets for backend users, in case only a curated list of sets
+        shall be selectable:
+
+        ..  code-block:: typoscript
+            :caption: EXT:my_extension/Configuration/user.tsconfig
+
+            options.sites.hideSets := addToList(typo3/fluid-styled-content)
+
+        The :guilabel:`Site Management > Sites` GUI will not show hidden sets,
+        but makes one exception if a hidden set has already been applied to a site
+
+        In this case a set
+        marked as hidden will be shown in the list of currently activated sets (that means
+        it can be introspected and removed via backend UI).