convert long banners to sidebars to avoid conflicts (#96)

Author: rosieyohannan

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

@@ -72,21 +72,19 @@ You can also make a longer admonition block for any of the types listed above:
 
 [source,adoc]
 ----
-[CAUTION]
-====
+****
 This is a longer admonition with an ordered list:
 
 . Step 1
 . Step 2
 . Step 3
-====
+****
 ----
 
-[CAUTION]
-====
+****
 This is a longer admonition with an ordered list:
 
 . Step 1
 . Step 2
 . Step 3
-====
+****

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

@@ -15,8 +15,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 +24,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:
 

docs/guides/modules/ROOT/partials/create-project/steps-up-to-pipeline.adoc

@@ -14,14 +14,13 @@ image::guides:ROOT:create-project/what-project.png[Screenshot showing options to
 
 . Give your project a descriptive name and then select btn:[Next: Set up a pipeline].
 +
-[TIP]
-====
+****
 **Project names** must meet the following requirements:
 
 * Begin with a letter.
 * Be 3-40 characters long.
 * Contain only letters, numbers, or the following characters: `" - _ . : ! & + [ ] " ;`.
-====
+****
 +
 .Name your project
 image::guides:ROOT:create-project/enter-project-details.png[Screenshot showing options to enter project details]

docs/guides/modules/ROOT/partials/execution-resources/docker-arm-resource-table.adoc

@@ -1,13 +1,13 @@
-[NOTE]
-====
+
+****
 *Arm on Docker* For credit and access information see the link:https://circleci.com/product/features/resource-classes/[Resource classes page]. Resource class access is dependent on your xref:guides:plans-pricing:plan-overview.adoc[Plan]
 
 To find out which CircleCI Docker convenience images support Arm resource classes, you can refer to link:https://hub.docker.com/u/cimg[Docker hub]:
 
 . Select the image (for example, `cimg/python`).
 . Select the **tags** tab.
 . View what is supported under **OS/ARCH** for the latest tags. For example, `cimg/python` has `linux/amd64` and `linux/arm64`, which means Arm **is** supported.
-====
+****
 
 [.table.table-striped]
 [cols=5*, options="header", stripes=even]

docs/guides/modules/ROOT/partials/execution-resources/macos-resource-table.adoc

@@ -28,11 +28,10 @@
 | icon:times[]
 |===
 
-[WARNING]
-====
+****
 *We have deprecated support for all Intel-based macOS resources.*
 
 The `macos.x86.medium.gen2` resource class was deprecated on June 28, 2024.
 
 See our link:https://discuss.circleci.com/t/macos-intel-support-deprecation-in-january-2024/48718[announcement] for more details.
-====
+****

docs/guides/modules/ROOT/partials/notes/find-organization-id.adoc

@@ -1,6 +1,5 @@
-[NOTE]
-====
+****
 To find your organization/user ID, select **Organization Settings** in the CircleCI web app side bar.
 
 image::guides:ROOT:org-id.png[screenshot showing where to find your organization ID]
-====
+****

docs/guides/modules/ROOT/partials/notes/standalone-unsupported.adoc

@@ -1,5 +1,4 @@
-[NOTE]
-====
+****
 This feature **is supported** for orgs that use OAuth authentication.
 
 Check your Organization slug at menu:Organization settings[Overview]. OAuth authenticated orgs are structured as follows:
@@ -12,4 +11,4 @@ This feature is **not supported** if your organization slug is in the following
 * `circleci/<UID>`.
 
 For an overview of feature support, see the xref:guides:integration:version-control-system-integration-overview.adoc#feature-support-for-each-integration-type[VCS integration overview] page.
-====
+****

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

@@ -16,15 +16,14 @@ Your role within your org is determined differently depending on how you integra
 
 * If your code is integrated with CircleCI via the GitHub App, GitLab, or Bitbucket Data Center, you can check roles by navigating to menu:Organization Settings[People]. Full details on roles and permissions are available in the xref:guides:permissions-authentication:roles-and-permissions-overview.adoc[Roles and permissions overview].
 
-[TIP]
-====
+****
 To find out which GitHub integration you are using, head to the link:https://circleci.com/app[CircleCI web app], select your org, select **Organization Home** from the sidebar, and inspect the URL in your browser:
 
 * This style of URL indicates you authenticated with the **GitHub App**: `https://app.circleci.com/organization/circleci/UTxCZDiJ9MLGLC8hR1ZDmg`
 * This style of URL indicates you authenticated with the **GitHub OAuth app**: `https://app.circleci.com/pipelines/github/<your GitHub username/organization name>`
 
 For more information about the differences, see the link:https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps[GitHub docs comparison page].
-====
+****
 
 --
 [.tab.runner-terms.CLI_installation]

docs/guides/modules/ROOT/partials/tips/check-github-type-org.adoc

@@ -1,5 +1,4 @@
-[TIP]
-====
+****
 To find out which GitHub integration type you have, check your Organization slug at menu:Organization settings[Overview]. OAuth authenticated orgs are structured as follows:
 
 * `github/<your-org-name>` or `gh/<your-org-name>`
@@ -8,4 +7,4 @@ To find out which GitHub integration type you have, check your Organization slug
 An organization slug for a GitHub App integration is in the following format:
 
 * `circleci/<UID>`
-====
+****

docs/guides/modules/ROOT/partials/tips/find-project-slug.adoc

@@ -1,5 +1,4 @@
-[TIP]
-====
+****
 **To find your project slug, follow these steps:**
 
 . Head to the link:https://app.circleci.com/home[CircleCI web app] and select your org from the cards on your user homepage.
@@ -10,4 +9,4 @@
 
 * **GitHub App**: Project slug starts with `circleci` followed by UUIDs. For example, `circleci/34R3kN5RtfEE7v4sa4nWAU/4nYdoKGkb6RXn7JGt8SQtg`).
 * **GitHub OAuth app**: Project slug is human readable. For example, `github/circleci/circleci-demo-workflows`.
-====
+****