remove the server component from main (#97)

* remove the server component from main

* add back in links to latest server version from migration page

* Fix tab syntax (#98)

* update script to handle directories

* update script

* fix tab syntax

* update link to server installation guides

* fix typo

Author: rosieyohannan

antora-playbook.yml

@@ -14,7 +14,7 @@ content:
     start_path: docs/orbs
   - url: .
     start_path: docs/server-admin
-    branches: [HEAD, server-v*]
+    branches: [server-v*]
   - url: .
     start_path: docs/contributors
 ui:

docs/guides/modules/ROOT/partials/runner/terms.adoc

@@ -1,7 +1,10 @@
 //[#self-hosted-runner-terms-agreement]
 //== Self-hosted runner Terms Agreement
 
-[.tab.runner-terms.Web_app_installation]
+[tabs]
+====
+Web_app_installation::
++
 --
 
 Before you can install self-hosted runners through the web app, you will need to agree to the https://circleci.com/legal/runner-terms/[CircleCI Runner Terms]. To be able to gain access to the *Self-Hosted Runners* section of the https://app.circleci.com/[CircleCI web app] or your CircleCI server app, an admin in your organization needs to navigate to menu:Organization Settings[Self-Hosted Runners], and agree to the terms.
@@ -26,7 +29,7 @@ For more information about the differences, see the link:https://docs.github.com
 ****
 
 --
-[.tab.runner-terms.CLI_installation]
+====
 --
 
 If you are installing and using self-hosted runners through the CLI, you are agreeing to the https://circleci.com/legal/runner-terms/[CircleCI Runner Terms].

docs/guides/modules/about-circleci/pages/concepts.adoc

@@ -240,7 +240,11 @@ An _image_ is a packaged system that includes instructions for creating a runnin
 
 include::ROOT:partial$notes/docker-auth.adoc[]
 
-[.tab.executors.Cloud]
+[tabs]
+====
+Cloud::
++
+--
 [,yaml]
 ----
 version: 2.1
@@ -284,8 +288,10 @@ workflows:
       - build2
       - build3
 ----
-
-[.tab.executors.Server]
+--
+Server::
++
+--
 [,yaml]
 ----
 version: 2.1
@@ -318,6 +324,8 @@ workflows:
       - build1
       - build2
 ----
+--
+====
 
 The primary container is defined by the first image listed in `.circleci/config.yml` file. This is where commands are executed. The Docker executor spins up a container with a Docker image. The machine executor spins up a complete Ubuntu virtual machine image. Further images can be added to spin up secondary/service containers.
 

docs/guides/modules/about-circleci/pages/open-source.adoc

@@ -6,7 +6,10 @@
 
 This page provides the details of 3rd-party open source components used in CircleCI products.
 
-[.tab.oss-ack.Release_agent]
+[tabs]
+====
+Release_agent::
++
 --
 The following 3rd-party open source components are used in the CircleCI release agent. The release agent is used to integrate CircleCI with Kubernetes clusters for release management. For more information, see the xref:deploy:deploys-overview.adoc[Deploys docs].
 
@@ -16,8 +19,8 @@ The following 3rd-party open source components are used in the CircleCI release
 include::guides:ROOT:attachment$release-agent.csv[]
 |===
 --
-
-[.tab.oss-ack.GOAT]
+GOAT::
++
 --
 The following 3rd-party open source components are used in the CircleCI General Orchestration Agent (GOAT). GOAT is an agent used by self-hosted container runners for managing the container environment. For more information, see the xref:execution-runner:container-runner.adoc[Container Runner docs].
 
@@ -27,8 +30,7 @@ The following 3rd-party open source components are used in the CircleCI General
 include::guides:ROOT:attachment$runner-init.csv[]
 |===
 --
-
-[.tab.oss-ack.CircleCI_Runner]
+====
 --
 The following 3rd-party open source components are used in the CircleCI self-hosted runner. The CircleCI runner is a utility used to run CirlceCI jobs on self-hosted infrastructure. For more information, see the xref:execution-runner:runner-overview.adoc[self-hosted runner overview docs].
 

docs/guides/modules/deploy/pages/deploy-android-applications.adoc

@@ -219,7 +219,10 @@ You can set up your configuration with the link:https://circleci.com/developer/o
 
 Using the Android orb gives you two options for deploying to the Google Play Store. You can either use the `deploy_to_play_store` job from the orb, or run each command individually in a job.
 
-[.tab.configAndroidOrb.Use_the_deploy-to-play-store_job]
+[tabs]
+====
+Use_the_deploy-to-play-store_job::
++
 --
 To deploy using the `deploy-to-play-store` job you just need to add an `android/deploy_to_play_store` job to your list of jobs in your workflow.
 
@@ -254,8 +257,8 @@ workflows:
 
 NOTE: The executor has no default value and must be set in the configuration.
 --
-
-[.tab.configAndroidOrb.Run_each_command_individually]
+Run_each_command_individually::
++
 --
 To run each command individually in a job, you will need to add the following commands to your job:
 
@@ -296,6 +299,7 @@ jobs:
             lane_name: internal
 ```
 --
+====
 
 [#set-up-config-without-the-android-orb]
 === b. Set up configuration without the Android orb

docs/guides/modules/deploy/pages/set-up-circleci-deploys.adoc

@@ -34,7 +34,10 @@ include::ROOT:partial$deploy/supported-versions.adoc[]
 
 == Set up CircleCI deploys
 
-[.tab.environmentintegration.Kubernetes_cluster]
+[tabs]
+====
+Kubernetes_cluster::
++
 --
 . In the CircleCI web app, select **Deploys** in the sidebar.
 . If this is your first environment setup, select btn:[Create your first Environment Integration]. If you already have environments set up, choose the **Environments** tab and select btn:[Create Environment Integration].
@@ -48,15 +51,16 @@ After completing all the setup steps in the app, you will have done the followin
 * Installed the release agent into your Kubernetes cluster
 * Configured your Kubernetes components.
 --
-
-[.tab.environmentintegration.Amazon_SageMaker]
+Amazon_SageMaker::
++
 --
 . In the CircleCI web app, select **Deploys** in the sidebar.
 . If this is your first environment setup, select btn:[Create your first Environment Integration]. If you already have environments set up, choose the **Environments** tab and select btn:[Create Environment Integration].
 . Enter a name for your environment, and a description if you would like.
 . Use the dropdown menu to choose your environment integration type, Amazon SageMaker, then select btn:[Save and Continue].
 . To get set up with CircleCI deploys and Amazon SageMaker from this point, follow the steps outlined on the xref:deploy-to-amazon-sagemaker.adoc[Deploy to Amazon SageMaker] page.
 --
+====
 
 [#next-steps]
 == Next steps

docs/guides/modules/execution-managed/pages/executor-intro.adoc

@@ -69,7 +69,10 @@ NOTE: *CircleCI cloud* The use of `machine: true` is deprecated. You must specif
 
 To access the Linux VM execution environment, use the `machine` executor and specify a Linux image. For a full list of `machine` images, see the link:https://circleci.com/developer/images?imageType=machine[CircleCI Developer Hub]
 
-[.tab.machine.Cloud]
+[tabs]
+====
+Cloud::
++
 --
 [,yml]
 ----
@@ -82,8 +85,8 @@ jobs:
         # Commands run in a Linux virtual machine environment
 ----
 --
-
-[.tab.machine.Server]
+Server::
++
 --
 [,yml]
 ----
@@ -94,6 +97,7 @@ jobs:
       # Commands run in a Linux virtual machine environment
 ----
 --
+====
 
 Find out more about the Linux VM execution environment in the xref:using-linuxvm.adoc[Using Linux Virtual Machines] page.
 
@@ -128,7 +132,10 @@ To access the Windows execution environment, you can either:
 
 For a full list of `machine` images, see the link:https://circleci.com/developer/images?imageType=machine[CircleCI Developer Hub].
 
-[.tab.windowsblock.Cloud_with_orb]
+[tabs]
+====
+Cloud_with_orb::
++
 --
 [,yml]
 ----
@@ -147,8 +154,8 @@ jobs:
       - run: Write-Host 'Hello, Windows'
 ----
 --
-
-[.tab.windowsblock.Cloud]
+Cloud::
++
 --
 [,yaml]
 ----
@@ -166,8 +173,8 @@ jobs:
         - run: Write-Host 'Hello, Windows'
 ----
 --
-
-[.tab.windowsblock.Server]
+Server::
++
 --
 [,yml]
 ----
@@ -183,6 +190,7 @@ jobs:
         - run: Write-Host 'Hello, Windows'
 ----
 --
+====
 
 Find out more about the Windows execution environment in the xref:using-windows.adoc[Using the Windows Execution Environment] page. See link:https://circleci.com/developer/orbs/orb/circleci/windows[the Windows orb page in the developer hub] for the list of options available in the Windows orb.
 
@@ -198,7 +206,10 @@ For a full list of `machine` images, see the link:https://circleci.com/developer
 
 NOTE: It is not possible to run a GPU build on CircleCI server.
 
-[.tab.gpublock.Linux]
+[tabs]
+====
+Linux::
++
 --
 [,yml]
 ----
@@ -213,8 +224,8 @@ jobs:
       - run: nvidia-smi
 ----
 --
-
-[.tab.gpublock.Windows_without_orb]
+Windows_without_orb::
++
 --
 [,yml]
 ----
@@ -229,8 +240,8 @@ jobs:
       - run: nvidia-smi
 ----
 --
-
-[.tab.gpublock.Windows_with_orb]
+Windows_with_orb::
++
 --
 [,yml]
 ----
@@ -246,6 +257,7 @@ jobs:
       - run: 'Write-Host ''Hello, Windows'''
 ----
 --
+====
 
 Find out more about the GPU execution environment on the xref:using-gpu.adoc[Using the GPU Execution Environment] page.
 
@@ -254,7 +266,10 @@ Find out more about the GPU execution environment on the xref:using-gpu.adoc[Usi
 
 To access the Arm VM execution environment, use the `machine` executor as detailed below, and specify either the `arm.medium` or the `arm.large` resource class. For a full list of `machine` images, see the link:https://circleci.com/developer/images?imageType=machine[CircleCI Developer Hub].
 
-[.tab.armblock.Cloud]
+[tabs]
+====
+Cloud::
++
 --
 [,yml]
 ----
@@ -285,8 +300,8 @@ workflows:
       - build-large
 ----
 --
-
-[.tab.armblock.Server_on_AWS]
+Server_on_AWS::
++
 --
 [,yml]
 ----
@@ -317,6 +332,7 @@ workflows:
       - build-large
 ----
 --
+====
 
 Find out more about the Arm VM execution environment in the xref:using-arm.adoc[Using the Arm VM Execution Environment] page. You can also use xref:using-docker.adoc#arm[Arm on Docker].
 

docs/guides/modules/execution-managed/pages/using-arm.adoc

@@ -6,7 +6,10 @@
 
 You can access the Arm VM (virtual machine) execution environment for a job by using the machine executor, specifying a Linux virtual machine image that includes Arm resources, and then specifying an Arm resource class.
 
-[.tab.armblock.Cloud]
+[tabs]
+====
+Cloud::
++
 --
 [,yaml]
 ----
@@ -21,8 +24,8 @@ jobs:
       - run: echo "Hello, Arm!"
 ----
 --
-
-[.tab.armblock.Server]
+Server::
++
 --
 [,yaml]
 ----
@@ -37,6 +40,7 @@ jobs:
       - run: echo "Hello, Arm!"
 ----
 --
+====
 
 [#available-resource-classes]
 == Available resource classes

docs/guides/modules/execution-managed/pages/using-gpu.adoc

@@ -25,7 +25,10 @@ jobs:
 
 To use the Windows GPU execution environment, you can either choose to use the Windows orb and specify the built-in GPU executor, or use the machine executor and specify a Windows GPU-enabled image. Refer to the link:https://circleci.com/developer/orbs/orb/circleci/windows[Orb Registry page] for full details, and the link:https://circleci.com/developer/images?imageType=machine[Developer Hub] for full details of available machine executor images.
 
-[.tab.gpublock.Windows_GPU_with_orb]
+[tabs]
+====
+Windows_GPU_with_orb::
++
 --
 [,yaml]
 ----
@@ -41,8 +44,8 @@ jobs:
       - run: '&"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe"'
 ----
 --
-
-[.tab.gpublock.Windows_GPU_with_machine]
+Windows_GPU_with_machine::
++
 --
 [,yaml]
 ----
@@ -56,6 +59,7 @@ jobs:
       - run: '&"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe"'
 ----
 --
+====
 
 [#available-resource-classes]
 == Available resource classes

docs/guides/modules/execution-managed/pages/using-linuxvm.adoc

@@ -19,7 +19,10 @@ The use of `machine: true` is deprecated when using **CircleCI cloud**. You must
 * When using the machine executor on CircleCI server
 ****
 
-[.tab.machineblock.Cloud]
+[tabs]
+====
+Cloud::
++
 --
 [,yaml]
 ----
@@ -31,8 +34,8 @@ jobs:
     resource_class: large
 ----
 --
-
-[.tab.machineblock.Server]
+Server::
++
 --
 [,yaml]
 ----
@@ -43,6 +46,7 @@ jobs:
     resource_class: large
 ----
 --
+====
 
 You can view the list of available images xref:reference:ROOT:configuration-reference.adoc#available-linux-machine-images-cloud[in the Configuration Reference], or on the link:https://circleci.com/developer/images?imageType=machine[Developer Hub]. If you are working on an installation of CircleCI server, you will notice in the example above the syntax is slightly different, and the available Linux images are managed by your system administrator.