From 860c861716cd9a4059dc574c6af14bbb954f145b Mon Sep 17 00:00:00 2001 From: Gaurav Trivedi Date: Mon, 24 Aug 2026 19:58:15 +0530 Subject: [PATCH] chore: promote Extend to top-level Antora module (JTBD Phase 3) Move editor, extension, AI provider, and Open VSX content from administration-guide to a new top-level modules/extend/ Antora module. Apply JTBD titles, sync navtitles, and fix cross-module xrefs. Co-authored-by: Cursor --- .gitignore | 1 + antora.yml | 1 + modules/administration-guide/nav.adoc | 22 ---------------- ...ster-custom-resource-fields-reference.adoc | 4 +-- .../pages/configuring-dashboard.adoc | 8 +++--- ...ft-visual-studio-code-open-source-ide.adoc | 2 +- ...-code-extensions-at-workspace-startup.adoc | 4 +-- ...ncealing-editors-additional-resources.adoc | 2 +- .../snip_che-default-vsx-registry.adoc | 0 .../examples/snip_che-editor-id-list.adoc | 0 .../snip_che-managing-extensions.adoc | 0 ...che-non-default-vsx-registry-instance.adoc | 0 modules/extend/nav.adoc | 25 +++++++++++++++++++ .../ai-provider-api-key-secret-reference.adoc | 10 +++++--- .../pages/concealing-editors.adoc | 8 +++--- .../pages/configuring-ai-providers.adoc | 8 +++--- .../pages/configuring-default-editor.adoc | 6 +++-- .../configuring-editors-definitions.adoc | 8 +++--- .../configuring-editors-download-urls.adoc | 6 +++-- ...uring-single-and-multiroot-workspaces.adoc | 6 +++-- ...configuring-the-open-vsx-registry-url.adoc | 8 +++--- .../pages/configuring-visual-studio-code.adoc | 6 +++-- ...ions-for-microsoft-visual-studio-code.adoc | 6 +++-- ...ions-for-microsoft-visual-studio-code.adoc | 8 +++--- ...nabling-the-managed-open-vsx-registry.adoc | 1 - ...rosoft-visual-studio-code-open-source.adoc | 6 +++-- .../pages/manage-extension-installation.adoc | 6 +++-- .../pages/managing-ide-extensions.adoc | 6 +++-- ...oc_configure-internal-open-vsx-access.adoc | 6 +++-- ...ng-extension-from-postgresql-database.adoc | 6 +++-- ...ing-extension-using-openvsx-admin-api.adoc | 6 +++-- .../proc_deploy-open-vsx-from-source.adoc | 6 +++-- .../proc_deploy-open-vsx-from-workspace.adoc | 6 +++-- .../pages/show-deprecated-editors.adoc | 10 +++++--- ...ions-for-microsoft-visual-studio-code.adoc | 6 +++-- ...or-removing-extensions-in-a-workspace.adoc | 2 +- ...dding-or-removing-extensions-on-linux.adoc | 2 +- ...lecting-an-open-vsx-registry-instance.adoc | 2 +- 38 files changed, 133 insertions(+), 87 deletions(-) rename modules/{administration-guide => extend}/examples/snip_che-concealing-editors-additional-resources.adoc (66%) rename modules/{administration-guide => extend}/examples/snip_che-default-vsx-registry.adoc (100%) rename modules/{administration-guide => extend}/examples/snip_che-editor-id-list.adoc (100%) rename modules/{administration-guide => extend}/examples/snip_che-managing-extensions.adoc (100%) rename modules/{administration-guide => extend}/examples/snip_che-non-default-vsx-registry-instance.adoc (100%) create mode 100644 modules/extend/nav.adoc rename modules/{administration-guide => extend}/pages/ai-provider-api-key-secret-reference.adoc (95%) rename modules/{administration-guide => extend}/pages/concealing-editors.adoc (79%) rename modules/{administration-guide => extend}/pages/configuring-ai-providers.adoc (97%) rename modules/{administration-guide => extend}/pages/configuring-default-editor.adoc (87%) rename modules/{administration-guide => extend}/pages/configuring-editors-definitions.adoc (97%) rename modules/{administration-guide => extend}/pages/configuring-editors-download-urls.adoc (88%) rename modules/{administration-guide => extend}/pages/configuring-single-and-multiroot-workspaces.adoc (93%) rename modules/{administration-guide => extend}/pages/configuring-the-open-vsx-registry-url.adoc (92%) rename modules/{administration-guide => extend}/pages/configuring-visual-studio-code.adoc (80%) rename modules/{administration-guide => extend}/pages/default-extensions-for-microsoft-visual-studio-code.adoc (96%) rename modules/{administration-guide => extend}/pages/editor-configurations-for-microsoft-visual-studio-code.adoc (94%) rename modules/{administration-guide => extend}/pages/enabling-the-managed-open-vsx-registry.adoc (99%) rename modules/{administration-guide => extend}/pages/extensions-for-microsoft-visual-studio-code-open-source.adoc (88%) rename modules/{administration-guide => extend}/pages/manage-extension-installation.adoc (97%) rename modules/{administration-guide => extend}/pages/managing-ide-extensions.adoc (94%) rename modules/{administration-guide => extend}/pages/proc_configure-internal-open-vsx-access.adoc (90%) rename modules/{administration-guide => extend}/pages/proc_deleting-extension-from-postgresql-database.adoc (96%) rename modules/{administration-guide => extend}/pages/proc_deleting-extension-using-openvsx-admin-api.adoc (93%) rename modules/{administration-guide => extend}/pages/proc_deploy-open-vsx-from-source.adoc (97%) rename modules/{administration-guide => extend}/pages/proc_deploy-open-vsx-from-workspace.adoc (96%) rename modules/{administration-guide => extend}/pages/show-deprecated-editors.adoc (77%) rename modules/{administration-guide => extend}/pages/trusted-extensions-for-microsoft-visual-studio-code.adoc (92%) rename modules/{administration-guide => extend}/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc (98%) rename modules/{administration-guide => extend}/partials/proc_adding-or-removing-extensions-on-linux.adoc (98%) rename modules/{administration-guide => extend}/partials/proc_selecting-an-open-vsx-registry-instance.adoc (98%) diff --git a/.gitignore b/.gitignore index bed5638306..d7a37026fe 100644 --- a/.gitignore +++ b/.gitignore @@ -43,3 +43,4 @@ yarn.lock # Do not commit diagrams generated for downstream crw* +CLAUDE.md diff --git a/antora.yml b/antora.yml index b61cd17f90..b3cd035044 100644 --- a/antora.yml +++ b/antora.yml @@ -15,6 +15,7 @@ nav: - modules/secure/nav.adoc - modules/optimize/nav.adoc - modules/observe/nav.adoc + - modules/extend/nav.adoc - modules/administration-guide/nav.adoc - modules/extensions/nav.adoc - modules/glossary/nav.adoc diff --git a/modules/administration-guide/nav.adoc b/modules/administration-guide/nav.adoc index ad78f8b903..0adfd2758d 100644 --- a/modules/administration-guide/nav.adoc +++ b/modules/administration-guide/nav.adoc @@ -35,13 +35,6 @@ *** xref:con_persistent-user-home.adoc[] ** xref:configuring-dashboard.adoc[] *** xref:configuring-getting-started-samples.adoc[] -*** xref:configuring-editors-definitions.adoc[] -*** xref:show-deprecated-editors.adoc[] -*** xref:configuring-default-editor.adoc[] -*** xref:concealing-editors.adoc[] -*** xref:configuring-editors-download-urls.adoc[] -*** xref:configuring-ai-providers.adoc[] -**** xref:ai-provider-api-key-secret-reference.adoc[] *** xref:customizing-openshift-che-branding-images.adoc[] ** xref:configuring-oauth-for-git-providers.adoc[] *** xref:configuring-oauth-2-for-github.adoc[] @@ -56,19 +49,4 @@ ** xref:devworkspace-backup.adoc[] *** xref:devworkspace-backup-integrated-openshift-registry.adoc[] *** xref:devworkspace-backup-regular-oci-registry.adoc[] -* xref:managing-ide-extensions.adoc[] -** xref:extensions-for-microsoft-visual-studio-code-open-source.adoc[] -** xref:configuring-the-open-vsx-registry-url.adoc[] -** xref:enabling-the-managed-open-vsx-registry.adoc[] -** xref:proc_deploy-open-vsx-from-source.adoc[] -** xref:proc_deploy-open-vsx-from-workspace.adoc[] -** xref:proc_configure-internal-open-vsx-access.adoc[] -** xref:proc_deleting-extension-using-openvsx-admin-api.adoc[] -** xref:proc_deleting-extension-from-postgresql-database.adoc[] -* xref:configuring-visual-studio-code.adoc[] -** xref:configuring-single-and-multiroot-workspaces.adoc[] -** xref:trusted-extensions-for-microsoft-visual-studio-code.adoc[] -** xref:default-extensions-for-microsoft-visual-studio-code.adoc[] -** xref:manage-extension-installation.adoc[] -** xref:editor-configurations-for-microsoft-visual-studio-code.adoc[] * xref:managing-workloads-using-the-che-server-api.adoc[] diff --git a/modules/administration-guide/pages/checluster-custom-resource-fields-reference.adoc b/modules/administration-guide/pages/checluster-custom-resource-fields-reference.adoc index 2d4a2989e3..6629d7d385 100644 --- a/modules/administration-guide/pages/checluster-custom-resource-fields-reference.adoc +++ b/modules/administration-guide/pages/checluster-custom-resource-fields-reference.adoc @@ -191,5 +191,5 @@ Optional. A JSON array of provider `id` values that are pre-selected in the AI S .Additional resources -* xref:configuring-ai-providers.adoc[] -* xref:ai-provider-api-key-secret-reference.adoc[] +* xref:extend:configuring-ai-providers.adoc[] +* xref:extend:ai-provider-api-key-secret-reference.adoc[] diff --git a/modules/administration-guide/pages/configuring-dashboard.adoc b/modules/administration-guide/pages/configuring-dashboard.adoc index 56047f6105..8a7e2cbae9 100644 --- a/modules/administration-guide/pages/configuring-dashboard.adoc +++ b/modules/administration-guide/pages/configuring-dashboard.adoc @@ -9,15 +9,15 @@ * xref:configuring-getting-started-samples.adoc[] -* xref:configuring-editors-definitions.adoc[] +* xref:extend:configuring-editors-definitions.adoc[] * xref:configuring-editors-download-urls.adoc[] -* xref:show-deprecated-editors.adoc[] +* xref:extend:show-deprecated-editors.adoc[] -* xref:configuring-default-editor.adoc[] +* xref:extend:configuring-default-editor.adoc[] -* xref:concealing-editors.adoc[] +* xref:extend:concealing-editors.adoc[] * xref:customizing-openshift-che-branding-images.adoc[] diff --git a/modules/end-user-guide/pages/microsoft-visual-studio-code-open-source-ide.adoc b/modules/end-user-guide/pages/microsoft-visual-studio-code-open-source-ide.adoc index 046b3d954c..c5a2bde08a 100644 --- a/modules/end-user-guide/pages/microsoft-visual-studio-code-open-source-ide.adoc +++ b/modules/end-user-guide/pages/microsoft-visual-studio-code-open-source-ide.adoc @@ -9,7 +9,7 @@ The {prod-short} build of link:https://github.com/microsoft/vscode[Microsoft Visual Studio Code - Open Source] is the default IDE of a new workspace. -You can automate installation of Microsoft Visual Studio Code extensions from the xref:administration-guide:extensions-for-microsoft-visual-studio-code-open-source.adoc[Open VSX registry] at workspace startup. See _Automating installation of Microsoft Visual Studio Code extensions at workspace startup_. +You can automate installation of Microsoft Visual Studio Code extensions from the xref:extend:extensions-for-microsoft-visual-studio-code-open-source.adoc[Open VSX registry] at workspace startup. See _Automating installation of Microsoft Visual Studio Code extensions at workspace startup_. [TIP] ==== diff --git a/modules/end-user-guide/partials/proc_automating-installation-of-microsoft-visual-studio-code-extensions-at-workspace-startup.adoc b/modules/end-user-guide/partials/proc_automating-installation-of-microsoft-visual-studio-code-extensions-at-workspace-startup.adoc index a00e2c5f11..a4ce43957f 100644 --- a/modules/end-user-guide/partials/proc_automating-installation-of-microsoft-visual-studio-code-extensions-at-workspace-startup.adoc +++ b/modules/end-user-guide/partials/proc_automating-installation-of-microsoft-visual-studio-code-extensions-at-workspace-startup.adoc @@ -5,13 +5,13 @@ To have the Microsoft Visual Studio Code - Open Source IDE automatically install chosen extensions, you can add an `extensions.json` file to the remote Git repository that contains your project source code and that will be cloned into workspaces. .Prerequisites -* The public OpenVSX registry at link:https://open-vsx.org[open-vsx.org] is selected and accessible over the internet. See xref:administration-guide:extensions-for-microsoft-visual-studio-code-open-source.adoc[Selecting an Open VSX registry instance]. +* The public OpenVSX registry at link:https://open-vsx.org[open-vsx.org] is selected and accessible over the internet. See xref:extend:extensions-for-microsoft-visual-studio-code-open-source.adoc[Selecting an Open VSX registry instance]. + [TIP] ==== To install recommended extensions in a restricted environment, consider the following options instead: -* xref:administration-guide:configuring-the-open-vsx-registry-url.adoc[] to point to your OpenVSX registry. +* xref:extend:configuring-the-open-vsx-registry-url.adoc[] to point to your OpenVSX registry. * xref:defining-a-common-ide.adoc[]. diff --git a/modules/administration-guide/examples/snip_che-concealing-editors-additional-resources.adoc b/modules/extend/examples/snip_che-concealing-editors-additional-resources.adoc similarity index 66% rename from modules/administration-guide/examples/snip_che-concealing-editors-additional-resources.adoc rename to modules/extend/examples/snip_che-concealing-editors-additional-resources.adoc index 3c98c8da29..fcce627017 100644 --- a/modules/administration-guide/examples/snip_che-concealing-editors-additional-resources.adoc +++ b/modules/extend/examples/snip_che-concealing-editors-additional-resources.adoc @@ -4,6 +4,6 @@ * xref:install:using-chectl-to-configure-the-checluster-custom-resource-during-installation.adoc[] -* xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[] +* xref:administration-guide:using-the-cli-to-configure-the-checluster-custom-resource.adoc[] * {editor-definition-samples-link} diff --git a/modules/administration-guide/examples/snip_che-default-vsx-registry.adoc b/modules/extend/examples/snip_che-default-vsx-registry.adoc similarity index 100% rename from modules/administration-guide/examples/snip_che-default-vsx-registry.adoc rename to modules/extend/examples/snip_che-default-vsx-registry.adoc diff --git a/modules/administration-guide/examples/snip_che-editor-id-list.adoc b/modules/extend/examples/snip_che-editor-id-list.adoc similarity index 100% rename from modules/administration-guide/examples/snip_che-editor-id-list.adoc rename to modules/extend/examples/snip_che-editor-id-list.adoc diff --git a/modules/administration-guide/examples/snip_che-managing-extensions.adoc b/modules/extend/examples/snip_che-managing-extensions.adoc similarity index 100% rename from modules/administration-guide/examples/snip_che-managing-extensions.adoc rename to modules/extend/examples/snip_che-managing-extensions.adoc diff --git a/modules/administration-guide/examples/snip_che-non-default-vsx-registry-instance.adoc b/modules/extend/examples/snip_che-non-default-vsx-registry-instance.adoc similarity index 100% rename from modules/administration-guide/examples/snip_che-non-default-vsx-registry-instance.adoc rename to modules/extend/examples/snip_che-non-default-vsx-registry-instance.adoc diff --git a/modules/extend/nav.adoc b/modules/extend/nav.adoc new file mode 100644 index 0000000000..9fc1336292 --- /dev/null +++ b/modules/extend/nav.adoc @@ -0,0 +1,25 @@ +.Extend +* Choose which editors are available +** xref:configuring-editors-definitions.adoc[] +** xref:configuring-default-editor.adoc[] +** xref:concealing-editors.adoc[] +** xref:show-deprecated-editors.adoc[] +** xref:configuring-editors-download-urls.adoc[] +* xref:configuring-visual-studio-code.adoc[] +** xref:configuring-single-and-multiroot-workspaces.adoc[] +** xref:trusted-extensions-for-microsoft-visual-studio-code.adoc[] +** xref:default-extensions-for-microsoft-visual-studio-code.adoc[] +** xref:manage-extension-installation.adoc[] +** xref:editor-configurations-for-microsoft-visual-studio-code.adoc[] +* xref:managing-ide-extensions.adoc[] +** xref:extensions-for-microsoft-visual-studio-code-open-source.adoc[] +** xref:configuring-the-open-vsx-registry-url.adoc[] +* Deploy a private extension registry +** xref:proc_deploy-open-vsx-from-source.adoc[] +** xref:proc_deploy-open-vsx-from-workspace.adoc[] +** xref:proc_configure-internal-open-vsx-access.adoc[] +** xref:enabling-the-managed-open-vsx-registry.adoc[] +** xref:proc_deleting-extension-using-openvsx-admin-api.adoc[] +** xref:proc_deleting-extension-from-postgresql-database.adoc[] +* xref:configuring-ai-providers.adoc[] +** xref:ai-provider-api-key-secret-reference.adoc[] diff --git a/modules/administration-guide/pages/ai-provider-api-key-secret-reference.adoc b/modules/extend/pages/ai-provider-api-key-secret-reference.adoc similarity index 95% rename from modules/administration-guide/pages/ai-provider-api-key-secret-reference.adoc rename to modules/extend/pages/ai-provider-api-key-secret-reference.adoc index c66835c0ba..995da48092 100644 --- a/modules/administration-guide/pages/ai-provider-api-key-secret-reference.adoc +++ b/modules/extend/pages/ai-provider-api-key-secret-reference.adoc @@ -1,3 +1,4 @@ +:page-aliases: administration-guide:ai-provider-api-key-secret-reference.adoc :_content-type: REFERENCE :description: Kubernetes Secret schema, labels, and naming convention for AI provider API keys that are automatically mounted into workspace containers. :keywords: administration, ai, api key, secret, kubernetes, devworkspace controller, environment variable, mount @@ -10,7 +11,8 @@ [role="_abstract"] Each user's AI provider API key is stored as a {kubernetes} `Opaque` Secret in the user's personal {orch-namespace}. The {devworkspace} Controller automatically mounts matching Secrets as environment variables into all workspace containers. Use this reference when manually creating or troubleshooting AI provider key Secrets. -== Secret schema + +== What the Secret contains [source,yaml,subs="+quotes,+attributes"] ---- @@ -36,7 +38,7 @@ data: <5> Mounts the Secret data keys as environment variables (not as files). <6> The data key is the environment variable name. The value is base64-encoded. The variable is injected directly into all workspace containers. -== Label and annotation reference +== Required labels and annotations [cols="1,1,2",options="header"] |=== @@ -59,7 +61,7 @@ data: | Used by the {prod-short} dashboard to identify and list AI provider key Secrets when rendering the AI Selector widget. |=== -== Secret naming convention +== How to name your Secret Secret names follow the pattern: @@ -77,7 +79,7 @@ Example: | `ai-provider-openai-api-key` |=== -== Manual Secret creation +== Create the Secret manually Advanced users can create AI provider key Secrets manually using `{orch-cli}` instead of the dashboard UI. Use the same labels and annotations as shown in the schema above: diff --git a/modules/administration-guide/pages/concealing-editors.adoc b/modules/extend/pages/concealing-editors.adoc similarity index 79% rename from modules/administration-guide/pages/concealing-editors.adoc rename to modules/extend/pages/concealing-editors.adoc index e4c0160410..273d1cdf66 100644 --- a/modules/administration-guide/pages/concealing-editors.adoc +++ b/modules/extend/pages/concealing-editors.adoc @@ -1,10 +1,12 @@ +:page-aliases: administration-guide:concealing-editors.adoc :_content-type: PROCEDURE :description: Concealing editors in the Dashboard UI :keywords: administration guide, concealing, dashboard, editors -:navtitle: Concealing editors +:navtitle: Hide editors from the dashboard [id="concealing-editors"] -= Concealing editors += Hide editors from the dashboard + Learn how to conceal {prod-short} editors. This is useful when you want to hide selected editors from the Dashboard UI, for example hide the IntelliJ IDEA Ultimate and have only Visual Studio Code - Open Source visible. @@ -18,7 +20,7 @@ Learn how to conceal {prod-short} editors. This is useful when you want to hide include::example$snip_che-editor-id-list.adoc[] -. Configure the `CheCluster` Custom Resource. See xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[]. +. Configure the `CheCluster` Custom Resource. See xref:administration-guide:using-the-cli-to-configure-the-checluster-custom-resource.adoc[]. + [source,yaml] ---- diff --git a/modules/administration-guide/pages/configuring-ai-providers.adoc b/modules/extend/pages/configuring-ai-providers.adoc similarity index 97% rename from modules/administration-guide/pages/configuring-ai-providers.adoc rename to modules/extend/pages/configuring-ai-providers.adoc index 7eef2df746..149062274b 100644 --- a/modules/administration-guide/pages/configuring-ai-providers.adoc +++ b/modules/extend/pages/configuring-ai-providers.adoc @@ -1,14 +1,15 @@ +:page-aliases: administration-guide:configuring-ai-providers.adoc :_content-type: PROCEDURE :description: Register AI providers in Eclipse Che so that developers can select and use AI coding assistants when creating workspaces. :keywords: administration, ai, ai provider, opencode, configmap, ai-tool-registry, api key, injector image, dockerfile, architecture, arch, version -:navtitle: Configuring AI providers +:navtitle: Register AI coding assistants :page-aliases: [id="configuring-ai-providers"] -= Configure AI providers += Register AI coding assistants :FeatureName: The AI provider feature -include::example$snip_che-technology-preview.adoc[] +include::administration-guide:example$snip_che-technology-preview.adoc[] [NOTE] ==== @@ -18,6 +19,7 @@ OpenCode supports only `x86_64` and `arm64`. IBM Z (`s390x`) and IBM Power (`ppc [role="_abstract"] Register one or more AI providers in {prod-short} so that developers can select and use AI coding assistants when creating workspaces. + The AI tool registry is stored in a {kubernetes} `ConfigMap` with specific labels. When the ConfigMap exists and contains at least one provider with a matching tool, the AI Selector widget is displayed on the dashboard. When the ConfigMap is absent or empty, the widget is hidden. {prod-short} reads the node architectures present in the cluster and filters the tool list before sending it to the dashboard. A tool is shown if at least one cluster node matches an architecture in the tool's `arch` list. Tools that omit the `arch` field are shown on all architectures. diff --git a/modules/administration-guide/pages/configuring-default-editor.adoc b/modules/extend/pages/configuring-default-editor.adoc similarity index 87% rename from modules/administration-guide/pages/configuring-default-editor.adoc rename to modules/extend/pages/configuring-default-editor.adoc index 3db3f7276f..69d2759018 100644 --- a/modules/administration-guide/pages/configuring-default-editor.adoc +++ b/modules/extend/pages/configuring-default-editor.adoc @@ -1,10 +1,12 @@ +:page-aliases: administration-guide:configuring-default-editor.adoc :_content-type: PROCEDURE :description: Configuring default editor :keywords: administration guide, dashboard, editors -:navtitle: Configuring default editor +:navtitle: Set the default IDE for new workspaces [id="configuring-default-editor"] -= Configuring default editor += Set the default IDE for new workspaces + Learn how to configure {prod-short} default editor. diff --git a/modules/administration-guide/pages/configuring-editors-definitions.adoc b/modules/extend/pages/configuring-editors-definitions.adoc similarity index 97% rename from modules/administration-guide/pages/configuring-editors-definitions.adoc rename to modules/extend/pages/configuring-editors-definitions.adoc index 998f0cebf8..215993f2a0 100644 --- a/modules/administration-guide/pages/configuring-editors-definitions.adoc +++ b/modules/extend/pages/configuring-editors-definitions.adoc @@ -1,11 +1,13 @@ +:page-aliases: administration-guide:configuring-editors-definitions.adoc :_content-type: PROCEDURE :description: Configuring editors definitions :keywords: administration guide, configuring, dashboard, editors -:navtitle: Configuring editors definitions +:navtitle: Add custom editors to the dashboard :page-aliases: installation-guide:configuring-editors-definitions.adoc [id="configuring-editors-definitions"] -= Configuring editors definitions += Add custom editors to the dashboard + Learn how to configure {prod-short} editor definitions. @@ -179,7 +181,7 @@ commands: . Refresh the {prod-short} Dashboard page to see new available editor. -== Retrieving the editor definition +== Retrieve the editor definition The editor definition is also served by the {prod-short} dashboard API from the following URL: diff --git a/modules/administration-guide/pages/configuring-editors-download-urls.adoc b/modules/extend/pages/configuring-editors-download-urls.adoc similarity index 88% rename from modules/administration-guide/pages/configuring-editors-download-urls.adoc rename to modules/extend/pages/configuring-editors-download-urls.adoc index ea073a5620..4a82739ce9 100644 --- a/modules/administration-guide/pages/configuring-editors-download-urls.adoc +++ b/modules/extend/pages/configuring-editors-download-urls.adoc @@ -1,10 +1,12 @@ +:page-aliases: administration-guide:configuring-editors-download-urls.adoc :_content-type: PROCEDURE :description: Configuring editors download urls :keywords: administration guide, dashboard, editors -:navtitle: Configuring editors download urls +:navtitle: Host editor binaries for air-gapped clusters [id="configuring-editors-download-urls"] -= Configuring editors download URLs += Host editor binaries for air-gapped clusters + This procedure describes how to configure download URLs for editors. This feature is valuable in air-gapped environments where editors cannot be retrieved from the public internet. diff --git a/modules/administration-guide/pages/configuring-single-and-multiroot-workspaces.adoc b/modules/extend/pages/configuring-single-and-multiroot-workspaces.adoc similarity index 93% rename from modules/administration-guide/pages/configuring-single-and-multiroot-workspaces.adoc rename to modules/extend/pages/configuring-single-and-multiroot-workspaces.adoc index cd4004999c..25848a028d 100644 --- a/modules/administration-guide/pages/configuring-single-and-multiroot-workspaces.adoc +++ b/modules/extend/pages/configuring-single-and-multiroot-workspaces.adoc @@ -1,11 +1,13 @@ +:page-aliases: administration-guide:configuring-single-and-multiroot-workspaces.adoc :_content-type: PROCEDURE :description: Configuring single and multiroot workspaces :keywords: singleroot, multiroot, workspace -:navtitle: Configuring single and multiroot workspaces +:navtitle: Work with multiple projects in one workspace // :page-aliases: [id="configuring-single-and-multiroot-workspaces"] -= Configuring single and multi root workspaces += Work with multiple projects in one workspace + With the multi-root workspace feature, you can work with multiple project folders in the same workspace. This is useful when you are working on several related projects at once, such as product documentation and product code repositories. diff --git a/modules/administration-guide/pages/configuring-the-open-vsx-registry-url.adoc b/modules/extend/pages/configuring-the-open-vsx-registry-url.adoc similarity index 92% rename from modules/administration-guide/pages/configuring-the-open-vsx-registry-url.adoc rename to modules/extend/pages/configuring-the-open-vsx-registry-url.adoc index 5d76369db7..6a1e268048 100644 --- a/modules/administration-guide/pages/configuring-the-open-vsx-registry-url.adoc +++ b/modules/extend/pages/configuring-the-open-vsx-registry-url.adoc @@ -1,15 +1,17 @@ +:page-aliases: administration-guide:configuring-the-open-vsx-registry-url.adoc :_content-type: PROCEDURE :description: Configure the Open VSX registry URL for {prod} workspaces :keywords: administration guide, configuring, openvsx, registry, extensions -:navtitle: Configure the Open VSX registry URL +:navtitle: Use an alternative extension registry :page-aliases: [id="configuring-the-open-vsx-registry-url"] -= Configure the Open VSX registry URL += Use an alternative extension registry [role="_abstract"] Configure {prod-short} to use an alternative Open VSX registry instance instead of the default embedded registry. Switch to the public open-vsx.org registry for internet-connected environments, or to a standalone on-premises instance for full control over available extensions. + The default is the embedded instance of the Open VSX registry. If the default Open VSX registry instance does not meet your requirements, you can select one of the following instances: @@ -68,5 +70,5 @@ Due to the dedicated Microsoft link:https://cdn.vsassets.io/v/M190_20210811.1/_c [role="_additional-resources"] .Additional resources -* xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[] +* xref:administration-guide:using-the-cli-to-configure-the-checluster-custom-resource.adoc[] * link:https://open-vsx.org/[Open VSX registry] diff --git a/modules/administration-guide/pages/configuring-visual-studio-code.adoc b/modules/extend/pages/configuring-visual-studio-code.adoc similarity index 80% rename from modules/administration-guide/pages/configuring-visual-studio-code.adoc rename to modules/extend/pages/configuring-visual-studio-code.adoc index d25bd834d7..4440e9c2d9 100644 --- a/modules/administration-guide/pages/configuring-visual-studio-code.adoc +++ b/modules/extend/pages/configuring-visual-studio-code.adoc @@ -1,11 +1,13 @@ +:page-aliases: administration-guide:configuring-visual-studio-code.adoc :_content-type: CONCEPT :description: Configuring Visual Studio Code - Open Source ("Code - OSS") :keywords: vscode, workspace -:navtitle: Configuring Visual Studio Code - Open Source ("Code - OSS") +:navtitle: Customize the default IDE //:page-aliases: [id="configuring-visual-studio-code"] -= Configuring Visual Studio Code - Open Source ("Code - OSS") += Customize the default IDE + Learn how to configure Visual Studio Code - Open Source ("Code - OSS"). diff --git a/modules/administration-guide/pages/default-extensions-for-microsoft-visual-studio-code.adoc b/modules/extend/pages/default-extensions-for-microsoft-visual-studio-code.adoc similarity index 96% rename from modules/administration-guide/pages/default-extensions-for-microsoft-visual-studio-code.adoc rename to modules/extend/pages/default-extensions-for-microsoft-visual-studio-code.adoc index 06e7692b5e..828c9c852b 100644 --- a/modules/administration-guide/pages/default-extensions-for-microsoft-visual-studio-code.adoc +++ b/modules/extend/pages/default-extensions-for-microsoft-visual-studio-code.adoc @@ -1,11 +1,13 @@ +:page-aliases: administration-guide:default-extensions-for-microsoft-visual-studio-code.adoc :_content-type: PROCEDURE :description: Configure default extensions :keywords: extensions, workspace -:navtitle: Configure default extensions +:navtitle: Pre-install extensions in every workspace // :page-aliases: [id="visual-studio-code-default-extensions"] -= Configuring default extensions += Pre-install extensions in every workspace + Default extensions are a pre-installed set of extensions, specified by putting the extension binary `.vsix` file path to the __DEFAULT_EXTENSIONS__ environment variable. diff --git a/modules/administration-guide/pages/editor-configurations-for-microsoft-visual-studio-code.adoc b/modules/extend/pages/editor-configurations-for-microsoft-visual-studio-code.adoc similarity index 94% rename from modules/administration-guide/pages/editor-configurations-for-microsoft-visual-studio-code.adoc rename to modules/extend/pages/editor-configurations-for-microsoft-visual-studio-code.adoc index dee52b966e..4411da40e0 100644 --- a/modules/administration-guide/pages/editor-configurations-for-microsoft-visual-studio-code.adoc +++ b/modules/extend/pages/editor-configurations-for-microsoft-visual-studio-code.adoc @@ -1,11 +1,13 @@ +:page-aliases: administration-guide:editor-configurations-for-microsoft-visual-studio-code.adoc :_content-type: PROCEDURE :description: Applying editor configurations :keywords: settings, extensions, configurations -:navtitle: Applying editor configurations +:navtitle: Apply IDE settings to all workspaces // :page-aliases: [id="visual-studio-code-editor-configs"] -= Applying editor configurations += Apply IDE settings to all workspaces + You can configure Visual Studio Code - Open Source editor by adding configurations to a ConfigMap. These configurations are applied to any workspace you open. @@ -89,7 +91,7 @@ data: Make sure that the Configmap contains data in a valid JSON format. ==== -TIP: Consider adding the ConfigMap to the {prod-namespace} namespace. By adding it to the namespace, you replicate the ConfigMap across all user namespaces while preventing modifications within user's namespaces. See xref:configuring-a-user-namespace.adoc[]. +TIP: Consider adding the ConfigMap to the {prod-namespace} namespace. By adding it to the namespace, you replicate the ConfigMap across all user namespaces while preventing modifications within user's namespaces. See xref:administration-guide:configuring-a-user-namespace.adoc[]. .Verification . Verify that settings defined in the ConfigMap are applied using one of the following methods: diff --git a/modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc b/modules/extend/pages/enabling-the-managed-open-vsx-registry.adoc similarity index 99% rename from modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc rename to modules/extend/pages/enabling-the-managed-open-vsx-registry.adoc index 88410dfb81..45877a2709 100644 --- a/modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc +++ b/modules/extend/pages/enabling-the-managed-open-vsx-registry.adoc @@ -6,7 +6,6 @@ [id="enabling-the-managed-open-vsx-registry"] = Enable the managed Open VSX registry -[role="_abstract"] [IMPORTANT] ==== The managed Open VSX registry is a Technology Preview feature only. diff --git a/modules/administration-guide/pages/extensions-for-microsoft-visual-studio-code-open-source.adoc b/modules/extend/pages/extensions-for-microsoft-visual-studio-code-open-source.adoc similarity index 88% rename from modules/administration-guide/pages/extensions-for-microsoft-visual-studio-code-open-source.adoc rename to modules/extend/pages/extensions-for-microsoft-visual-studio-code-open-source.adoc index 62798b03f4..b2dabf8b30 100644 --- a/modules/administration-guide/pages/extensions-for-microsoft-visual-studio-code-open-source.adoc +++ b/modules/extend/pages/extensions-for-microsoft-visual-studio-code-open-source.adoc @@ -1,11 +1,13 @@ +:page-aliases: administration-guide:extensions-for-microsoft-visual-studio-code-open-source.adoc :_content-type: ASSEMBLY :description: Extensions for Microsoft Visual Studio Code - Open Source :keywords: extensions, vs-code, vsx, open-vsx, marketplace -:navtitle: Extensions for Microsoft Visual Studio Code - Open Source +:navtitle: How the Open VSX extension registry works //:page-aliases: [id="extensions-for-microsoft-visual-studio-code-open-source"] -= Extensions for Microsoft Visual Studio Code - Open Source += How the Open VSX extension registry works + To manage extensions, {prod-short} uses one of the following Open VSX registry instances: diff --git a/modules/administration-guide/pages/manage-extension-installation.adoc b/modules/extend/pages/manage-extension-installation.adoc similarity index 97% rename from modules/administration-guide/pages/manage-extension-installation.adoc rename to modules/extend/pages/manage-extension-installation.adoc index 73c80af147..4011ab5570 100644 --- a/modules/administration-guide/pages/manage-extension-installation.adoc +++ b/modules/extend/pages/manage-extension-installation.adoc @@ -1,11 +1,13 @@ +:page-aliases: administration-guide:manage-extension-installation.adoc :_content-type: PROCEDURE :description: Manage extension installation with ConfigMap :keywords: extensions, workspace -:navtitle: Manage extension installation with ConfigMap +:navtitle: Control which extensions users can install // :page-aliases: [id="visual-studio-code-manage-extensions-installation"] -= Manage extension installation with ConfigMap += Control which extensions users can install + This page describes how Code - OSS manages extension installation using a ConfigMap. With these controls, you can enforce a fine-grained allow/deny list using the `AllowedExtensions` policy and block installs via the CLI, default extensions, and the `workbench.extensions.command.installFromVSIX` API command. diff --git a/modules/administration-guide/pages/managing-ide-extensions.adoc b/modules/extend/pages/managing-ide-extensions.adoc similarity index 94% rename from modules/administration-guide/pages/managing-ide-extensions.adoc rename to modules/extend/pages/managing-ide-extensions.adoc index 7b5d8a0f03..302b9e89d0 100644 --- a/modules/administration-guide/pages/managing-ide-extensions.adoc +++ b/modules/extend/pages/managing-ide-extensions.adoc @@ -1,15 +1,17 @@ +:page-aliases: administration-guide:managing-ide-extensions.adoc :_content-type: CONCEPT :description: Options for managing IDE extensions in {prod} workspaces :keywords: extensions, plugins, openvsx, registry, ide -:navtitle: Managing IDE extensions +:navtitle: How IDE extensions work in workspaces :page-aliases: [id="managing-ide-extensions"] -= Managing IDE extensions += How IDE extensions work in workspaces [role="_abstract"] Manage IDE extensions in {prod-short} workspaces to control which extensions are available, trusted, and pre-installed for users across different IDE types. Extension management is essential for air-gapped environments, security-conscious organizations, and teams that need consistent developer tooling. + IDEs in {prod-short} use extensions to provide language support, debugging, linting, and other development tools. The Microsoft Visual Studio Code - Open Source editor manages extensions through the Open VSX registry. {prod-short} supports five registry configurations: diff --git a/modules/administration-guide/pages/proc_configure-internal-open-vsx-access.adoc b/modules/extend/pages/proc_configure-internal-open-vsx-access.adoc similarity index 90% rename from modules/administration-guide/pages/proc_configure-internal-open-vsx-access.adoc rename to modules/extend/pages/proc_configure-internal-open-vsx-access.adoc index 51318e6f6b..cda729fe75 100644 --- a/modules/administration-guide/pages/proc_configure-internal-open-vsx-access.adoc +++ b/modules/extend/pages/proc_configure-internal-open-vsx-access.adoc @@ -1,15 +1,17 @@ +:page-aliases: administration-guide:proc_configure-internal-open-vsx-access.adoc :_content-type: PROCEDURE :description: Restrict the Open VSX registry to internal cluster access :keywords: administration guide, openvsx, security, internal, routing -:navtitle: Configure internal Open VSX access +:navtitle: Restrict the extension registry to internal traffic :page-aliases: [id="proc_configure-internal-open-vsx-access"] -= Configure internal access to the Open VSX registry += Restrict the extension registry to internal traffic [role="_abstract"] Restrict your Open VSX registry to internal cluster traffic by removing the public route and configuring {prod-short} to use the internal service URL. Internal routing keeps extension registry traffic within the cluster and avoids public exposure. + .Prerequisites * You have Open VSX deployed in the `openvsx` namespace. diff --git a/modules/administration-guide/pages/proc_deleting-extension-from-postgresql-database.adoc b/modules/extend/pages/proc_deleting-extension-from-postgresql-database.adoc similarity index 96% rename from modules/administration-guide/pages/proc_deleting-extension-from-postgresql-database.adoc rename to modules/extend/pages/proc_deleting-extension-from-postgresql-database.adoc index 1785fc5f42..8d2a1e308f 100644 --- a/modules/administration-guide/pages/proc_deleting-extension-from-postgresql-database.adoc +++ b/modules/extend/pages/proc_deleting-extension-from-postgresql-database.adoc @@ -1,15 +1,17 @@ +:page-aliases: administration-guide:proc_deleting-extension-from-postgresql-database.adoc :_content-type: PROCEDURE :description: Delete an extension directly from the PostgreSQL database :keywords: administration guide, openvsx, delete, extension, postgresql, database -:navtitle: Delete an extension from the PostgreSQL database +:navtitle: Remove an extension from the database :page-aliases: [id="proc_deleting-extension-from-postgresql-database"] -= Delete an extension from the PostgreSQL database += Remove an extension from the database [role="_abstract"] Remove extension records and related data directly from the PostgreSQL database when the administrator API is not available or when you need to clean up specific data. If the extension uses local storage, you must also remove its files from the Open VSX server pod. + .Prerequisites * You have access to the cluster where the Open VSX registry is deployed in the `openvsx` namespace. diff --git a/modules/administration-guide/pages/proc_deleting-extension-using-openvsx-admin-api.adoc b/modules/extend/pages/proc_deleting-extension-using-openvsx-admin-api.adoc similarity index 93% rename from modules/administration-guide/pages/proc_deleting-extension-using-openvsx-admin-api.adoc rename to modules/extend/pages/proc_deleting-extension-using-openvsx-admin-api.adoc index c8c5003474..4a722e30f5 100644 --- a/modules/administration-guide/pages/proc_deleting-extension-using-openvsx-admin-api.adoc +++ b/modules/extend/pages/proc_deleting-extension-using-openvsx-admin-api.adoc @@ -1,15 +1,17 @@ +:page-aliases: administration-guide:proc_deleting-extension-using-openvsx-admin-api.adoc :_content-type: PROCEDURE :description: Delete an extension from the Open VSX registry using the administrator API :keywords: administration guide, openvsx, delete, extension, api -:navtitle: Delete an extension using the Open VSX API +:navtitle: Remove an extension through the registry API :page-aliases: [id="proc_deleting-extension-using-openvsx-admin-api"] -= Delete an extension by using the Open VSX administrator API += Remove an extension through the registry API [role="_abstract"] Delete an extension from your private Open VSX registry by calling the administrator API with an administrator user and a Personal Access Token (PAT). + .Prerequisites * You have access to the cluster where the Open VSX registry is deployed in the `openvsx` namespace. diff --git a/modules/administration-guide/pages/proc_deploy-open-vsx-from-source.adoc b/modules/extend/pages/proc_deploy-open-vsx-from-source.adoc similarity index 97% rename from modules/administration-guide/pages/proc_deploy-open-vsx-from-source.adoc rename to modules/extend/pages/proc_deploy-open-vsx-from-source.adoc index d56f233112..4ad2429746 100644 --- a/modules/administration-guide/pages/proc_deploy-open-vsx-from-source.adoc +++ b/modules/extend/pages/proc_deploy-open-vsx-from-source.adoc @@ -1,15 +1,17 @@ +:page-aliases: administration-guide:proc_deploy-open-vsx-from-source.adoc :_content-type: PROCEDURE :description: Build Open VSX from source and deploy a customized instance :keywords: administration guide, openvsx, build, deploy, registry, extensions -:navtitle: Deploy Open VSX from source +:navtitle: Build the extension registry from source :page-aliases: [id="proc_deploy-open-vsx-from-source"] -= Deploy Open VSX from source += Build the extension registry from source [role="_abstract"] Build custom Open VSX server and CLI images from source and deploy them to your cluster. Use this method when you need a specific Open VSX version or custom modifications to the registry. + .Prerequisites * You have the `{orch-cli}` tool installed. diff --git a/modules/administration-guide/pages/proc_deploy-open-vsx-from-workspace.adoc b/modules/extend/pages/proc_deploy-open-vsx-from-workspace.adoc similarity index 96% rename from modules/administration-guide/pages/proc_deploy-open-vsx-from-workspace.adoc rename to modules/extend/pages/proc_deploy-open-vsx-from-workspace.adoc index d08cc4a012..24425ce27d 100644 --- a/modules/administration-guide/pages/proc_deploy-open-vsx-from-workspace.adoc +++ b/modules/extend/pages/proc_deploy-open-vsx-from-workspace.adoc @@ -1,15 +1,17 @@ +:page-aliases: administration-guide:proc_deploy-open-vsx-from-workspace.adoc :_content-type: PROCEDURE :description: Deploy Open VSX from a Che workspace using devfile tasks :keywords: administration guide, openvsx, deploy, workspace, devfile -:navtitle: Deploy Open VSX from a workspace +:navtitle: Build the extension registry in a workspace :page-aliases: [id="proc_deploy-open-vsx-from-workspace"] -= Deploy Open VSX from a {prod-short} workspace += Build the extension registry in a workspace [role="_abstract"] Deploy an on-premises Open VSX extension registry by using predefined devfile tasks in a {prod-short} workspace. The workspace environment includes all necessary tools and commands defined in the `.devfile.yaml` file of the Open VSX repository. + .Prerequisites * You are logged in to the cluster as a cluster administrator. diff --git a/modules/administration-guide/pages/show-deprecated-editors.adoc b/modules/extend/pages/show-deprecated-editors.adoc similarity index 77% rename from modules/administration-guide/pages/show-deprecated-editors.adoc rename to modules/extend/pages/show-deprecated-editors.adoc index 54eb992c5b..0b49539901 100644 --- a/modules/administration-guide/pages/show-deprecated-editors.adoc +++ b/modules/extend/pages/show-deprecated-editors.adoc @@ -1,11 +1,13 @@ +:page-aliases: administration-guide:show-deprecated-editors.adoc :_content-type: PROCEDURE :description: Show deprecated editors :keywords: administration guide, show deprecated, dashboard, editors -:navtitle: Show deprecated editors +:navtitle: Restore access to deprecated editors :page-aliases: installation-guide:show-deprecated-editors.adoc [id="show-deprecated-editors"] -= Show deprecated editors += Restore access to deprecated editors + Learn how to show deprecated {prod-short} editors on the Dashboard. By default, the Dashboard UI hides them. @@ -25,7 +27,7 @@ Learn how to show deprecated {prod-short} editors on the Dashboard. By default, -- curl -s http://localhost:8080/dashboard/api/editors | jq -r '[.[] | select(.metadata.tags != null) | select(.metadata.tags[] | contains("Deprecate")) | "\(.metadata.attributes.publisher)/\(.metadata.name)/\(.metadata.attributes.version)"]' ---- -. Configure the `CheCluster` Custom Resource. See xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[]. +. Configure the `CheCluster` Custom Resource. See xref:administration-guide:using-the-cli-to-configure-the-checluster-custom-resource.adoc[]. + [source,yaml] ---- @@ -43,4 +45,4 @@ spec: * xref:install:using-chectl-to-configure-the-checluster-custom-resource-during-installation.adoc[] -* xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[] +* xref:administration-guide:using-the-cli-to-configure-the-checluster-custom-resource.adoc[] diff --git a/modules/administration-guide/pages/trusted-extensions-for-microsoft-visual-studio-code.adoc b/modules/extend/pages/trusted-extensions-for-microsoft-visual-studio-code.adoc similarity index 92% rename from modules/administration-guide/pages/trusted-extensions-for-microsoft-visual-studio-code.adoc rename to modules/extend/pages/trusted-extensions-for-microsoft-visual-studio-code.adoc index af6c22ae7b..b44e9651b5 100644 --- a/modules/administration-guide/pages/trusted-extensions-for-microsoft-visual-studio-code.adoc +++ b/modules/extend/pages/trusted-extensions-for-microsoft-visual-studio-code.adoc @@ -1,10 +1,12 @@ +:page-aliases: administration-guide:trusted-extensions-for-microsoft-visual-studio-code.adoc :_content-type: PROCEDURE :description: Configure trusted extensions for Microsoft Visual Studio Code :keywords: extensions, vs-code, vsx, open-vsx, marketplace -:navtitle: Configure trusted extensions for Microsoft Visual Studio Code +:navtitle: Grant extensions access to OAuth tokens [id="visual-studio-code-trusted-extensions"] -= Configure trusted extensions for Microsoft Visual Studio Code += Grant extensions access to OAuth tokens + You can use the `trustedExtensionAuthAccess` field in the `product.json` file of Microsoft Visual Studio Code to specify which extensions are trusted to access authentication tokens. diff --git a/modules/administration-guide/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc b/modules/extend/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc similarity index 98% rename from modules/administration-guide/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc rename to modules/extend/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc index bb051b047e..f6ba2cb98b 100644 --- a/modules/administration-guide/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc +++ b/modules/extend/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc @@ -1,7 +1,7 @@ :_content-type: PROCEDURE [id="adding-or-removing-extensions-in-a-workspace_{context}"] -= Adding or removing extensions by using a {prod-short} workspace += Add or remove extensions in a workspace [role="_abstract"] You can add or remove extensions in the embedded Open VSX registry instance directly within a {prod-short} workspace to create a custom build for your organization. diff --git a/modules/administration-guide/partials/proc_adding-or-removing-extensions-on-linux.adoc b/modules/extend/partials/proc_adding-or-removing-extensions-on-linux.adoc similarity index 98% rename from modules/administration-guide/partials/proc_adding-or-removing-extensions-on-linux.adoc rename to modules/extend/partials/proc_adding-or-removing-extensions-on-linux.adoc index 7c9333607f..8c8205b8a7 100644 --- a/modules/administration-guide/partials/proc_adding-or-removing-extensions-on-linux.adoc +++ b/modules/extend/partials/proc_adding-or-removing-extensions-on-linux.adoc @@ -1,7 +1,7 @@ :_content-type: PROCEDURE [id="adding-or-removing-extensions-on-linux_{context}"] -= Adding or removing extensions by using a Linux operating system += Add or remove extensions from the command line [role="_abstract"] You can build and publish a custom plugin registry using the Linux command line. This results in a custom build of the Open VSX registry that can be used in your organization's workspaces. diff --git a/modules/administration-guide/partials/proc_selecting-an-open-vsx-registry-instance.adoc b/modules/extend/partials/proc_selecting-an-open-vsx-registry-instance.adoc similarity index 98% rename from modules/administration-guide/partials/proc_selecting-an-open-vsx-registry-instance.adoc rename to modules/extend/partials/proc_selecting-an-open-vsx-registry-instance.adoc index 62fc185ed5..1e59b45807 100644 --- a/modules/administration-guide/partials/proc_selecting-an-open-vsx-registry-instance.adoc +++ b/modules/extend/partials/proc_selecting-an-open-vsx-registry-instance.adoc @@ -1,7 +1,7 @@ :_content-type: PROCEDURE [id="selecting-an-open-vsx-registry-instance_{context}"] -= Selecting an Open VSX registry instance += Choose which registry to use include::example$snip_{project-context}-default-vsx-registry.adoc[]