Remove references to old WoltLab Suite versions

The fact that a feature was introduced in 3.1 is no longer relevant when
referencing the documentation for WoltLab Suite 5.5. Removing these references
makes the documentation easier to read by removing unnecessary words.

see #219

diff --git a/docs/getting-started.md b/docs/getting-started.md
index 0103989ca95825549fa738c7c4b8f0fc509af778..37a08824217a49fe12832ed0777efa8d01bbd9ba 100644 (file)
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -198,8 +198,6 @@ Congratulations, you have just created your first package!
 
 ## Developer Tools
 
-!!! warning "This feature is available with WoltLab Suite 3.1 or newer only."
-
 The developer tools provide an interface to synchronize the data of an installed package with a bare repository on the local disk. You can re-import most PIPs at any time and have the changes applied without crafting a manual update. This process simulates a regular package update with a single PIP only, and resets the cache after the import has been completed.
 
 ### Registering a Project

diff --git a/docs/javascript/general-usage.md b/docs/javascript/general-usage.md
index 8b2b520073de7d2b5124fb89a0a91334ce6f6d01..9353634daa51b373d8b5ebe079fa3486f297da9c 100644 (file)
--- a/docs/javascript/general-usage.md
+++ b/docs/javascript/general-usage.md
@@ -87,10 +87,8 @@ the minified and optimized file to the average visitor. You should use the
 
 !!! info "You can learn more on the [Accelerated Guest View](../migration/wsc30/javascript.md) in the migration docs."
 
-The "Accelerated Guest View" was introduced in WoltLab Suite 3.1 and aims to
-decrease page size and to improve responsiveness by enabling a read-only mode
-for visitors. If you are providing a separate compiled build for this mode, you'll
-need to include yet another switch to serve the right version to the visitor.
+The “Accelerated Guest View” aims to decrease page size and to improve responsiveness by enabling a read-only mode for visitors.
+If you are providing a separate compiled build for this mode, you'll need to include yet another switch to serve the right version to the visitor.
 
 ```html
 <script data-relocate="true" src="{@$__wcf->getPath('app')}js/App{if !ENABLE_DEBUG_MODE}{if VISITOR_USE_TINY_BUILD}.tiny{/if}.min{/if}.js?t={@LAST_UPDATE_TIME}"></script>

diff --git a/docs/javascript/new-api_events.md b/docs/javascript/new-api_events.md
index 83a85f1e136e88573fc84a4226cc25ac6b8cb6ce..1273b567bcd1cc6caacbb8880a75d3954f4d37dc 100644 (file)
--- a/docs/javascript/new-api_events.md
+++ b/docs/javascript/new-api_events.md
@@ -56,9 +56,8 @@ events or trigger events itself at any time.
 
 ### Identifiying Events with the Developer Tools
 
-The Developer Tools in WoltLab Suite 3.1 offer an easy option to identify existing
-events that are fired while code is being executed. You can enable this watch
-mode through your browser's console using `Devtools.toggleEventLogging()`:
+The Developer Tools offer an easy option to identify existing events that are fired while code is being executed.
+You can enable this watch mode through your browser's console using `Devtools.toggleEventLogging()`:
 
 ```
 > Devtools.toggleEventLogging();

diff --git a/docs/package/database-php-api.md b/docs/package/database-php-api.md
index 26a84eefc3940f4cd579b6dcf67616cb4a0e2ac9..0876f41727aff7fc57156e53f88ee7e281f32539 100644 (file)
--- a/docs/package/database-php-api.md
+++ b/docs/package/database-php-api.md
@@ -1,7 +1,5 @@
 # Database PHP API
 
-!!! info "Available since WoltLab Suite 5.2."
-
 While the [sql](pip/sql.md) package installation plugin supports adding and removing tables, columns, and indices, it is not able to handle cases where the added table, column, or index already exist.
 We have added a new PHP-based API to manipulate the database scheme which can be used in combination with the [script](pip/script.md) package installation plugin that skips parts that already exist:
 

diff --git a/docs/package/pip/media-provider.md b/docs/package/pip/media-provider.md
index 9d43f53698f94503f9c29a1c5af5416576b8bb0c..9fc4c952e2d8143f4fb6e3484692ce453b3440f0 100644 (file)
--- a/docs/package/pip/media-provider.md
+++ b/docs/package/pip/media-provider.md
@@ -1,7 +1,5 @@
 # Media Provider Package Installation Plugin
 
-!!! info "Available since WoltLab Suite 3.1"
-
 Media providers are responsible to detect and convert links to a 3rd party service inside messages.
 
 ## Components

diff --git a/docs/php/api/sitemaps.md b/docs/php/api/sitemaps.md
index 68fce681edff2a06a7914cc698c992ec36c8c977..d7eabd3cb7626a60f890ab7cd2f67a58bf3665d4 100644 (file)
--- a/docs/php/api/sitemaps.md
+++ b/docs/php/api/sitemaps.md
@@ -1,8 +1,6 @@
 # Sitemaps
 
-!!! warning "This feature is available with WoltLab Suite 3.1 or newer only."
-
-Since version 3.1, WoltLab Suite Core is capable of automatically creating a sitemap.
+WoltLab Suite is capable of automatically creating a sitemap.
 This sitemap contains all static pages registered via the page package installation plugin and which may be indexed by search engines (checking the `allowSpidersToIndex` parameter and page permissions) and do not expect an object ID.
 Other pages have to be added to the sitemap as a separate object.
 
@@ -51,4 +49,4 @@ The `priority` should be `0.5` by default, unless there is an important reason t
 The parameter `rebuildTime` specifies the number of seconds after which the sitemap should be regenerated.
 
 Finally, you have to create the language variable for the sitemap object.
-The language variable follows the pattern `wcf.acp.sitemap.objectType.{objectTypeName}` and is in the category `wcf.acp.sitemap`.
\ No newline at end of file
+The language variable follows the pattern `wcf.acp.sitemap.objectType.{objectTypeName}` and is in the category `wcf.acp.sitemap`.

diff --git a/docs/php/gdpr.md b/docs/php/gdpr.md
index 4f1faf33ba98dbfe15fece35894cbb829de7fe7d..0aba064810cc046e112f13116f1d59459adc04cf 100644 (file)
--- a/docs/php/gdpr.md
+++ b/docs/php/gdpr.md
@@ -12,9 +12,7 @@ on woltlab.com.
 
 ## Including Data in the Export
 
-The `wcf\acp\action\UserExportGdprAction` introduced with WoltLab Suite 3.1.3
-already includes the Core itself as well as all official apps, but you'll need to
-include any personal data stored for your plugin or app by yourself.
+The `wcf\acp\action\UserExportGdprAction` already includes WoltLab Suite Core itself as well as all official apps, but you'll need to include any personal data stored for your plugin or app by yourself.
 
 The event `export` is fired before any data is sent out, but after any Core data
 has been dumped to the `$data` property.