migrate all content (#94)

* check all snippets partials and images exist and copy across all pages

* migrate all pages and make mapping table

* remove old docs

* convert page-platform and remove frontmatter

* remove page-layout

* fix image block references

* fix include

* update includes

* fix server includes

* fix xrefs as far as script can

* remove # when no section anchor needed

* fix xrefs

* fix image blocks and missing index

* fix some xrefs

* fix double file ext

* fix some xrefs

* fix more xrefs

* fix xrefs

* fix xrefs

* create server-admin for latest version

* fix xrefs

* fix xrefs

* fix xrefs

* fix partial paths

* fix paths and xrefs

* fix paths and xrefs

* fix paths and xrefs

* fix xrefs

* add missing sublanding pages

* fix xrefs and add missing pages

* fix xref and introduce missing pages

* fix xrefs

* remove server 4.6 from latest

* remove 4.5 server content from latest

* remove server 4.4 from latest

* remove 4.3 version from latest

* remove 4.1 and 4.2

* upper case Server

* add some content to landing page

* fix warning about unset attribute

Author: rosieyohannan

docs/contributors/modules/docs-style/pages/index.adoc

@@ -1,3 +1 @@
-= Docs Style Guide
-
-The pages in this section make up the CircleCI documentation style guide.
+= Docs style guide

docs/contributors/modules/docs-style/pages/links.adoc

@@ -8,7 +8,7 @@
 +
 [source,adoc]
 ----
-link:/docs/github-integration#user-keys-and-deploy-keys[User Keys and Deploy Keys]
+xref:guides:integration:github-integration.adoc#user-keys-and-deploy-keys[User Keys and Deploy Keys]
 ----
 
 * The **.md** equivalent would be to use a link:

docs/contributors/modules/templates/pages/index.adoc

@@ -1 +1 @@
-= Content Templates
+= Templates

docs/contributors/modules/templates/pages/template-conceptual.adoc

@@ -146,6 +146,6 @@ For more information, see xref:docs-style:formatting.adoc#using-notes-tips-cauti
 == Next steps
 
 // Here you can inlude links to other pages in docs or the blog etc. where the reader should head next.
-* xref:template-tutorial.adoc#[Tutorial template]
+* xref:template-tutorial.adoc[Tutorial template]
 * xref:guides:about-circleci:benefits-of-circleci.adoc[Benefits of CircleCI]
-* xref:guides:about-circleci:concepts.adoc#[CircleCI concepts]
+* xref:guides:about-circleci:concepts.adoc[CircleCI concepts]

docs/contributors/modules/templates/pages/template-how-to.adoc

@@ -16,7 +16,7 @@ Some notes on attributes
 ////
 
 [NOTE]
-****
+====
 This template will help you create a new docs page that shows the reader how to carry out a task and accomplish a specific goal with CircleCI. Content templates help you to:
 
 * Develop new content quickly
@@ -25,7 +25,7 @@ This template will help you create a new docs page that shows the reader how to
 To use this template, make a copy and place it in the `_cci2` directory. The filename should match the page title. Look at the source file for this page template link:https://github.com/circleci/circleci-docs/blob/master/jekyll/_cci2/template/template-how-to.adoc?plain=1[here]. There is additional detail in the comments.
 
 Contributors from within CircleCI can also consider setting up a local development environment to preview changes before pushing. Ping one of the Developer Resources and Engineering team (DRE) for more information.
-****
+====
 
 In a how-to guide, include one or two opening paragraphs. The opening paragraph should be used to briefly describe to the reader what the reader will do using this guide, and what the outcomes are when they successfully finish the task. The information in the opening paragraph should help answer the following questions for the reader:
 
@@ -34,7 +34,7 @@ In a how-to guide, include one or two opening paragraphs. The opening paragraph
 
 TIP: Since the reader will usually want to quickly get to the task at hand, keep the introduction succinct.
 
-TIP: Consider providing a link to an xref:template-conceptual.adoc#[overview or conceptual doc], should the reader be interested in more explanatory or background information regarding the feature or task.
+TIP: Consider providing a link to an xref:template-conceptual.adoc[overview or conceptual doc], should the reader be interested in more explanatory or background information regarding the feature or task.
 
 [#prerequisites]
 == Prerequisites
@@ -48,7 +48,7 @@ This is the first subsection in the how-to guide. List any prerequisites that th
 * Roles and permissions
 * Skills/knowledge
 // This renders as a nested item
-** Link to any helpful documentation or pages that they can refer to, for example, "For more information on how test splitting works, refer to the xref:guides:optimize:parallelism-faster-jobs.adoc#[Test splitting and parallelism] page."
+** Link to any helpful documentation or pages that they can refer to, for example, "For more information on how test splitting works, refer to the xref:guides:optimize:parallelism-faster-jobs.adoc[Test splitting and parallelism] page."
 * Any other dependencies
 
 Sometimes, there may be topics to know or tasks to complete that are _helpful_ in order to successfully finish the how-to guide, but do not necessarily have a negative impact on the user's flow if they only do those as they go along. For example, you may include generating an API token in the how-to steps itself, rather than listing it as a strict prerequisite. Use your best judgment to decide whether to add such a requirement as a prerequisite or as a step that is part of the how-to.
@@ -70,8 +70,8 @@ In a how-to guide, you might walk the reader through an example scenario. Exampl
 
 Subsections can be used to break steps into logical sub-parts as needed. Level 2 section titles (`===`) should also be ordered:
 
-* If the document comprises multiple smaller how-to guide, use numbers in the Level 2 titles. (As an example, see the xref:guides:config-policies:manage-contexts-with-config-policies.adoc#[Manage contexts with config policies] guide)
-* Otherwise, consider using lowercase letters. (As an example, see xref:guides:optimize:use-the-circleci-cli-to-split-tests.adoc#[Use the CircleCI CLI to split tests])
+* If the document comprises multiple smaller how-to guide, use numbers in the Level 2 titles. (As an example, see the xref:guides:config-policies:manage-contexts-with-config-policies.adoc[Manage contexts with config policies] guide)
+* Otherwise, consider using lowercase letters. (As an example, see xref:guides:optimize:use-the-circleci-cli-to-split-tests.adoc[Use the CircleCI CLI to split tests])
 
 Break up large blocks of text where possible to help make it easier to consume. You can use bullet lists:
 
@@ -107,7 +107,7 @@ link:https://circleci.com/[CircleCI website]
 
 To link to another page within the docs use a cross reference:
 
-xref:guides:about-circleci:about-circleci.adoc#[About CircleCI]
+xref:guides:about-circleci:about-circleci.adoc[About CircleCI]
 
 Notice the `#` at the end of the filename. You can place the subsection anchor there if you want to link to a subsection:
 
@@ -170,5 +170,5 @@ End the guide with a conclusion section that summarizes what was covered.
 == Next steps
 
 // Here you can inlude links to other pages in docs or the blog etc. where the reader should head next.
-* xref:guides:about-circleci:benefits-of-circleci.adoc#[Benefits of CircleCI]
-* xref:guides:about-circleci:concepts.adoc#[CircleCI concepts]
+* xref:guides:about-circleci:benefits-of-circleci.adoc[Benefits of CircleCI]
+* xref:guides:about-circleci:concepts.adoc[CircleCI concepts]

docs/contributors/modules/templates/pages/template-tutorial.adoc

@@ -30,7 +30,7 @@ Contributors from within CircleCI can also consider setting up a local developme
 [#introduction]
 == Introduction
 
-Use the introduction to explain what the reader is going to achieve through following the tutorial. Link back to the _conceptual_ page that accompanies the tutorial, to illustrate this here is a link to the xref:template-conceptual.adoc#[template for conceptual pages]. If possible provide a demo or example. The tutorial should ideally be written to accompany a public/open source example that any reader can use, but the tutorial should also be able to accommodate a reader’s own project.
+Use the introduction to explain what the reader is going to achieve through following the tutorial. Link back to the _conceptual_ page that accompanies the tutorial, to illustrate this here is a link to the xref:template-conceptual.adoc[template for conceptual pages]. If possible provide a demo or example. The tutorial should ideally be written to accompany a public/open source example that any reader can use, but the tutorial should also be able to accommodate a reader’s own project.
 
 [#prerequisites]
 == Prerequisites
@@ -92,7 +92,7 @@ link:https://circleci.com/[CircleCI website]
 
 To link to another page within the docs use a cross reference:
 
-xref:guides:about-circleci:about-circleci.adoc#[About CircleCI]
+xref:guides:about-circleci:about-circleci.adoc[About CircleCI]
 
 Notice the `#` at the end of the filename. You can place the subsection anchor there if you want to link to a subsection:
 
@@ -153,5 +153,5 @@ End the tutoral with a conclusion section that summarizes what was covered.
 == Next steps
 
 // Here you can inlude links to other pages in docs or the blog etc. where the reader should head next.
-* xref:guides:about-circleci:benefits-of-circleci.adoc#[Benefits of CircleCI]
-* xref:guides:about-circleci:concepts.adoc#[CircleCI concepts]
+* xref:guides:about-circleci:benefits-of-circleci.adoc[Benefits of CircleCI]
+* xref:guides:about-circleci:concepts.adoc[CircleCI concepts]

docs/guides/.DS_Store

@@ -0,0 +1,25 @@
+version: 2.1
+
+orbs:
+  my-orb: << url-ref >>
+
+jobs:
+  build:
+    steps: 
+      - run: task build
+  test:
+    steps:
+      - run: task test
+  deploy:
+    steps:
+      - run: ccc deploy
+
+workflows:
+  - build-test-deploy:
+      jobs:
+        - build
+        - test:
+            override-with: my-orb/my-test
+            requires: build
+        - deploy:
+            requires: test