move "Custom Plugin Repository" to Appendix I

ijs.tree

@@ -43,7 +43,6 @@
       <toc-element id="publishing_plugin.md"/>
     </toc-element>
     <toc-element id="ide_development_instance.md" accepts-web-file-names="settings_caches_logs.html"/>
-    <toc-element id="update_plugins_format.md" toc-title="Custom Plugin Repositories"/>
     <toc-element id="plugin_structure.md">
       <toc-element id="plugin_content.md"/>
       <toc-element id="bundling_plugin_openapi_sources.md" toc-title="Plugin API Sources"/>
@@ -353,6 +352,7 @@
     <toc-element id="learning_resources.md"/>
     <toc-element id="marketing.md"/>
     <toc-element id="consulting.md"/>
+    <toc-element id="custom_plugin_repository.md" accepts-web-file-names="update-plugins-format.html"/>
     <toc-element id="plugin_repository_obsolete.md"
                  accepts-web-file-names="api_reference.html,feature_extractor.html,plugin_details.html,custom_channels.html,plugins_list.html,maven_interface.html,plugin_upload.html,plugin_developers.html"/>
   </toc-element>

topics/appendix/resources/custom_plugin_repository.md

@@ -1,4 +1,4 @@
-[//]: # (title: Publishing a Plugin to a Custom Plugin Repository)
+[//]: # (title: Custom Plugin Repository)
 
 <!-- Copyright 2000-2022 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->
 

topics/appendix/tools/gradle_intellij_plugin/tools_gradle_intellij_plugin.md

@@ -376,7 +376,7 @@ Acceptable values
 - `marketplace()` - use Maven repository with plugins listed in [JetBrains Marketplace](https://plugins.jetbrains.com)
 - `maven(repositoryUrl)` - use custom Maven repository with plugins
 - `maven { repositoryUrl }` - use custom Maven repository with plugins where you can configure additional parameters (credentials, authentication and etc.)
-- `custom(pluginsXmlUrl)` - use [custom plugin repository](update_plugins_format.md)
+- `custom(pluginsXmlUrl)` - use [](custom_plugin_repository.md)
 
 
 ### jreRepository

topics/basics/getting_started/publishing_plugin.md

@@ -3,7 +3,7 @@
 <!-- Copyright 2000-2022 JetBrains s.r.o. and other contributors. Use of this source code is governed by the Apache 2.0 license that can be found in the LICENSE file. -->
 
 When your plugin is ready, you can publish it to a plugin repository so that other users can install it.
-You can choose to publish it on the [JetBrains Marketplace](https://plugins.jetbrains.com) or a [custom plugin repository](update_plugins_format.md).
+You can choose to publish it on the [JetBrains Marketplace](https://plugins.jetbrains.com) or a [](custom_plugin_repository.md).
 
 > Please make sure to follow the guidelines from [Plugin Overview page](https://plugins.jetbrains.com/docs/marketplace/plugin-overview-page.html) for an optimal presentation of your plugin on JetBrains Marketplace.
 >
@@ -48,4 +48,4 @@ New versions can be uploaded manually on the plugin's detail page, see [Marketpl
 
 ## Publishing a Plugin to a Custom Plugin Repository
 
-If you plan to publish your plugin to a repository _other than_ the [JetBrains Marketplace](https://plugins.jetbrains.com), please refer to the [Publishing to Custom Plugin Repositories](update_plugins_format.md) documentation.
+If you plan to publish your plugin to a repository _other than_ the [JetBrains Marketplace](https://plugins.jetbrains.com), please refer to the [](custom_plugin_repository.md) documentation.

topics/basics/plugin_structure/plugin_icon_file.md

@@ -15,7 +15,7 @@ Whether online or in the product UI, a Plugin Logo helps users to identify a plu
 
 ![Example Product Plugin Preferences Dialog](plugin_prefs.png){width="800"}
 
-> When browsing [custom plugin repositories](update_plugins_format.md), there is no support for showing logos for plugins hosted there but not yet installed.
+> When browsing [custom plugin repositories](custom_plugin_repository.md), there is no support for showing logos for plugins hosted there but not yet installed.
 >
 {type="note"}
 

topics/intro/intellij_platform.md

@@ -27,7 +27,7 @@ The IntelliJ Platform includes parsers and a PSI model for many languages, and i
 
 Products built on the IntelliJ Platform are extensible applications, with the platform being responsible for creating components and the injection of dependencies into classes.
 The IntelliJ Platform fully supports plugins, and JetBrains hosts the [JetBrains Marketplace](https://plugins.jetbrains.com) which can be used to distribute plugins that support one or more of the products.
-It is also possible to distribute plugins using [Custom Plugin Repositories](update_plugins_format.md).
+It is also possible to distribute plugins using a [](custom_plugin_repository.md).
 
 Plugins can extend the platform in many ways, from adding a simple menu item to adding support for a complete language, build system, and debugger.
 Many of the existing IntelliJ Platform features are implemented as plugins that can be included or excluded depending on the needs of the end product.

topics/tutorials/build_system/deployment.md

@@ -18,7 +18,7 @@ Please see the guide page for manually [publishing a plugin](publishing_plugin.m
 
 For initial upload, manual distribution or local installation, invoke the [`buildPlugin`](tools_gradle_intellij_plugin.md#buildplugin-task) Gradle task to create the plugin distribution.
 The resulting ZIP file is located in <path>build/distributions</path> and can then be installed via drag & drop (or using [plugin manager](https://www.jetbrains.com/help/idea/managing-plugins.html#installing-plugins-from-disk))
-or uploaded to a [custom plugin repository](update_plugins_format.md).
+or uploaded to a [](custom_plugin_repository.md).
 
 ## Providing Your Personal Access Token to Gradle