Avoid redirects from master to 5.0 (#3167)

* Avoid redirects from master to 5.0

* Changed link from main/master to 5.0

* Fixed compatibility-layer links

Author: mnocon

docs/administration/back_office/back_office_configuration.md

@@ -8,7 +8,7 @@ description: Configure default upload locations, pagination limits, and more set
 ## Pagination limits
 
 Default pagination limits for different sections of the back office can be defined through respective settings in
-[`ezplatform_default_settings.yaml`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/config/ezplatform_default_settings.yaml#L7).
+[`ezplatform_default_settings.yaml`](https://github.com/ibexa/admin-ui/blob/5.0/src/bundle/Resources/config/ezplatform_default_settings.yaml#L7).
 
 You can set the pagination limit for user settings under the `ibexa.system.<scope>.pagination_user` [configuration key](configuration.md#configuration-files):
 

docs/administration/back_office/back_office_elements/extending_thumbnails.md

@@ -58,7 +58,7 @@ At this point you can go to the back office and check the results.
 !!! note "Thumbnail mechanism "
 
     This strategy overrides all generated thumbnails. You can specify a specific content type.
-    See the example [here](https://github.com/ibexa/user/blob/main/src/lib/Strategy/DefaultThumbnailStrategy.php)
+    See the example [here](https://github.com/ibexa/user/blob/5.0/src/lib/Strategy/DefaultThumbnailStrategy.php)
 
 
 ## Other fields as thumbnails

docs/administration/back_office/back_office_elements/importing_assets_from_bundle.md

@@ -32,7 +32,7 @@ To import CSS files only, use:
 
     After you add new files, run `php bin/console cache:clear`.
 
-    For a full example of importing asset configuration, see [`ibexa.config.js`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/encore/ibexa.config.js)
+    For a full example of importing asset configuration, see [`ibexa.config.js`](https://github.com/ibexa/admin-ui/blob/5.0/src/bundle/Resources/encore/ibexa.config.js)
 
 To edit existing configuration entries, either in the bundle's `Resources/encore/` folder, or in the `encore` folder in the root folder of your project, create an `ibexa.config.manager.js` file:
 
@@ -74,7 +74,7 @@ module.exports = (ibexaConfig, ibexaConfigManager) => {
 
     After you add new files, run `php bin/console cache:clear`.
 
-    For a full example of overriding configuration, see [`ibexa.config.manager.js`](https://github.com/ibexa/fieldtype-matrix/blob/main/src/bundle/Resources/encore/ibexa.config.manager.js).
+    For a full example of overriding configuration, see [`ibexa.config.manager.js`](https://github.com/ibexa/fieldtype-matrix/blob/5.0/src/bundle/Resources/encore/ibexa.config.manager.js).
 
 To add a new configuration under your own namespace and with its own dependencies, create an `ibexa.webpack.custom.config.js` file that you create either in the bundle's `Resources/encore/` folder, or in the `encore` folder in the root directory of your project, for example:
 

docs/administration/back_office/back_office_tabs/back_office_tabs.md

@@ -64,7 +64,7 @@ You can also influence tab display (for example, order tabs, remove, or modify t
 
 ## Tab groups
 
-You can create new tab groups by using the [`TabsComponent`](https://github.com/ibexa/admin-ui/blob/main/src/lib/Component/TabsComponent.php).
+You can create new tab groups by using the [`TabsComponent`](https://github.com/ibexa/admin-ui/blob/5.0/src/lib/Component/TabsComponent.php).
 
 To create a tab group, register it as a service:
 

docs/administration/back_office/subitems_list.md

@@ -145,7 +145,7 @@ Optionally, Sub-items module can take a following list of props:
 - **items** _{Array}_ - list of location's sub-items
 - **limit** _{Number}_ - items limit count
 - **offset** _{Number}_ - items limit offset
-- **labels** _{Object}_ - list of module labels, see [sub.items.module.js](https://github.com/ibexa/admin-ui/blob/main/src/bundle/ui-dev/src/modules/sub-items/sub.items.module.js) for details. Contains definitions for sub components:
+- **labels** _{Object}_ - list of module labels, see [sub.items.module.js](https://github.com/ibexa/admin-ui/blob/5.0/src/bundle/ui-dev/src/modules/sub-items/sub.items.module.js) for details. Contains definitions for sub components:
     - **subItems** _{Object}_ - list of sub-items module labels
     - **tableView** _{Object}_ - list of table view component labels
     - **tableViewItem** _{Object}_ - list of table item view component labels

docs/administration/project_organization/bundles.md

@@ -11,7 +11,7 @@ You can also reuse the bundles you create in other projects or share them with t
 
 Many [[= product_name =]] functionalities are provided through separate bundles included in the installation.
 You can see the bundles that are automatically installed with [[= product_name =]] in the respective `composer.json` files.
-For example, for [[= product_name_headless =]], see the [JSON file on GitHub](https://github.com/ibexa/headless/blob/master/composer.json).
+For example, for [[= product_name_headless =]], see the [JSON file on GitHub](https://github.com/ibexa/headless/blob/5.0/composer.json).
 
 ## Working with bundles
 

docs/api/graphql/graphql_custom_ft.md

@@ -80,7 +80,7 @@ To do that, you need to replace `mapXXX` by the method it's in:
 
 It's required for every implemented method, so that other mappers are called for the other field types.
 
-For an example implementation, look at the [`RelationFieldDefinitionMapper`](https://github.com/ibexa/graphql/blob/main/src/lib/Schema/Domain/Content/Mapper/FieldDefinition/RelationFieldDefinitionMapper.php) class.
+For an example implementation, look at the [`RelationFieldDefinitionMapper`](https://github.com/ibexa/graphql/blob/5.0/src/lib/Schema/Domain/Content/Mapper/FieldDefinition/RelationFieldDefinitionMapper.php) class.
 
 The value type depends on the field definition allowed content types setting:
 
@@ -111,4 +111,4 @@ The following variables are available in the resolver's expression:
 - `location` is the content item's resolved location. For more information, see [Querying Locations](graphql_queries.md#querying-locations)
 - `item` is the content together with its location `\Ibexa\GraphQL\Value\Item`
 
-`RelationFieldValueBuilder` or `SelectionFieldValueBuilder` can be used as examples.
+`RelationFieldValueBuilder` or `SelectionFieldValueBuilder` can be used as examples.

docs/api/php_api/php_api.md

@@ -71,7 +71,7 @@ To create and modify repository values, use data structures, such as [`ContentSe
 
 ### Value info objects
 
-Some complex value objects have an `Info` counterpart, for example [`ContentInfo`](https://github.com/ibexa/core/blob/main/src/contracts/Repository/Values/Content/ContentInfo.php) for [`Content`](https://github.com/ibexa/core/blob/main/src/contracts/Repository/Values/Content/Content.php).
+Some complex value objects have an `Info` counterpart, for example [`ContentInfo`](https://github.com/ibexa/core/blob/5.0/src/contracts/Repository/Values/Content/ContentInfo.php) for [`Content`](https://github.com/ibexa/core/blob/5.0/src/contracts/Repository/Values/Content/Content.php).
 These objects provide you with lower-level information.
 For instance, `ContentInfo` contains `currentVersionNo` or `remoteId`, while `Content` enables you to retrieve fields, content type, or previous versions.
 

docs/content_management/field_types/field_type_reference/richtextfield.md

@@ -116,7 +116,7 @@ The RichText format enriches [DocBook](https://docbook.org/) with the following
 !!! note "Unsupported DocBook elements"
 
     Some DocBook elements aren't supported by RichText.
-    Refer to [`ezpublish.rng`](https://github.com/ibexa/fieldtype-richtext/blob/main/src/bundle/Resources/richtext/schemas/docbook/ezpublish.rng#L137) for a full list.
+    Refer to [`ezpublish.rng`](https://github.com/ibexa/fieldtype-richtext/blob/5.0/src/bundle/Resources/richtext/schemas/docbook/ezpublish.rng#L137) for a full list.
 
 ### Online Editor elements
 

docs/content_management/field_types/field_type_search.md

@@ -46,7 +46,7 @@ Default field is typically used by the [`Field` Sort Clause](field_sort_clause.m
 ## Register `Indexable` implementations
 
 Implement `Ibexa\Contracts\Core\FieldType\Indexable` as an extra service and register this Service using the `ibexa.field_type.indexable` tag.
-Example from [`indexable_fieldtypes.yaml`](https://github.com/ibexa/core/blob/main/src/lib/Resources/settings/indexable_fieldtypes.yml):
+Example from [`indexable_fieldtypes.yaml`](https://github.com/ibexa/core/blob/5.0/src/lib/Resources/settings/indexable_fieldtypes.yml):
 
 ``` yaml
 Ibexa\Core\FieldType\Keyword\SearchField: