From 101c734395556bc48541ea376ee8d813b74a7c7d Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 19 Nov 2024 16:30:10 +0100
Subject: [PATCH] [TASK] Allow sets to be excluded from site configuration GUI
 (#577)

resolves: https://github.com/TYPO3-Documentation/Changelog-To-Doc/issues/1081
releases: main, 13.4

Co-authored-by: lina.wolf <lwolf@w-commerce.de>
---
 Documentation/UserTsconfig/Options.rst | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/Documentation/UserTsconfig/Options.rst b/Documentation/UserTsconfig/Options.rst
index d4254d3..fc99173 100644
--- a/Documentation/UserTsconfig/Options.rst
+++ b/Documentation/UserTsconfig/Options.rst
@@ -1043,3 +1043,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).