Merge branch 'main' into DOCSS-1935-deploy-marker-screenshots

Author: rosieyohannan

docs/guides/modules/ROOT/images/ids-from-env-vars.png

@@ -291,6 +291,7 @@
 *** xref:integration:authorize-google-cloud-sdk.adoc[Authorize Google Cloud SDK]
 
 * Developer toolkit
+** xref:toolkit:how-to-find-ids.adoc[How to find IDs]
 ** AI features
 *** xref:toolkit:using-the-circleci-mcp-server.adoc[Using the CircleCI MCP server]
 *** xref:toolkit:intelligent-summaries.adoc[Intelligent summaries]

docs/guides/modules/ROOT/images/pipeline-id-from-job.png

@@ -1,4 +1,4 @@
-. In the link:https://app.circleci.com[CircleCI web app], select your org from the org cards on your user homepage.
+. In the link:https://app.circleci.com[CircleCI web app, window=_blank], select your org from the org cards on your user homepage.
 . Select **Projects** from the sidebar and locate your project from the list. You can use the search to help.
 . Select the ellipsis image:guides:ROOT:icons/more.svg[more icon, role="no-border"] next to your project and select **Project Settings**.
 +

docs/guides/modules/ROOT/images/pipeline-id-from-workflow.png

@@ -58,7 +58,7 @@ The AWS CodeBuild and CircleCI configurations will be different. It may be helpf
 
 include::ROOT:partial$notes/docker-auth.adoc[]
 
-[table-scroll]
+[.table-scroll]
 --
 [cols="1,1", options="header"]
 |===
@@ -67,7 +67,7 @@ include::ROOT:partial$notes/docker-auth.adoc[]
 2+| Define a job that executes a single build step.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 phases:
   build:
@@ -76,7 +76,7 @@ phases:
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   job1:
@@ -88,7 +88,7 @@ jobs:
 2+| Specify a Docker image to use for a job.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 phases:
   install:
@@ -97,7 +97,7 @@ phases:
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   job1:
@@ -108,7 +108,7 @@ jobs:
 2+| Define a multi-stage build pipeline. Job1 and Job2 run concurrently. Once they are done, Job3 runs. Once Job3 is done, Job4 runs. An AWS CodeBuild project runs all commands sequentially. If you are running concurrent commands, you are probably using CodePipeline and multiple CodeBuild projects.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 # CodePipeline Project 1
 phases:
@@ -136,7 +136,7 @@ phases:
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 version: 2.1
 jobs:
@@ -170,7 +170,7 @@ workflows:
 2+| Execute jobs on multiple platforms. An AWS CodePipeline project can target a single platform only. If you are targeting multiple platforms, you’re probably using CodePipeline and multiple CodeBuild projects. CircleCI provides executors for Docker, Linux and macOS that can be combined in a single build definition.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 # Environments are selected in the CodeBuild
 # web console or defined in a project
@@ -191,7 +191,7 @@ a|
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   ubuntuJob:
@@ -214,7 +214,7 @@ jobs:
 2+| Cache dependencies.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 # If custom cache is enabled in the web
 # console, CLI or CloudFormation, cache
@@ -229,9 +229,8 @@ cache:
   paths:
     - 'node_modules/**/*'
 ----
-
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   job1:
@@ -251,6 +250,7 @@ jobs:
 |===
 --
 
+
 For larger and more complex build files, we recommend moving over the build steps in phases until you get comfortable with the CircleCI platform. We recommend this order:
 
 . Execution of shell scripts and Docker compose files

docs/guides/modules/ROOT/images/workflow-id-from-job-url.png

@@ -74,7 +74,7 @@ include::ROOT:partial$notes/docker-auth.adoc[]
 2+| Define a job that executes a single build step.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   - job: job1
@@ -84,7 +84,7 @@ jobs:
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   job1:
@@ -96,7 +96,7 @@ jobs:
 2+| Specify a Docker image to use for a job.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   - job: job1
@@ -105,7 +105,7 @@ jobs:
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   job1:
@@ -116,7 +116,7 @@ jobs:
 2+| Define a multi-stage build pipeline. Job1 and Job2 run in concurrently. Once they are done, Job3 runs. Once Job3 is done, Job4 runs.
 
 a|
-[source, yaml,role="no-numbers"]
+[source, yaml]
 ----
 stages:
   - stage: build
@@ -140,7 +140,7 @@ stages:
 ----
 
 a|
-[source, yaml,role="no-numbers"]
+[source, yaml]
 ----
 version: 2.1
 jobs:
@@ -174,7 +174,7 @@ workflows:
 2+| Execute jobs on multiple platforms. Azure DevOps uses pools and demands to identify build runners. CircleCI provides executors for Docker, Linux and macOS.
 
 a|
-[source, yaml,role="no-numbers"]
+[source, yaml]
 ----
 jobs:
   - job: ubuntuJob
@@ -192,7 +192,7 @@ jobs:
 ----
 
 a|
-[source, yaml,role="no-numbers"]
+[source, yaml]
 ----
 jobs:
   ubuntuJob:

docs/guides/modules/ROOT/images/workflow-id-from-workflow-url.png

@@ -67,14 +67,14 @@ include::ROOT:partial$notes/docker-auth.adoc[]
 2+| Define a job that executes a single build step.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 steps:
   - command: 'execute-script-for-job1.sh'
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   job1:
@@ -86,7 +86,7 @@ jobs:
 2+| Specify a Docker image to use for a job.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 steps:
   - label: 'job1'
@@ -97,7 +97,7 @@ steps:
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   job1:
@@ -109,7 +109,7 @@ jobs:
 2+| Define a multi-stage build pipeline. Job1 and Job2 run concurrently. Once they are done, Job3 runs. Once Job3 is done, Job4 runs.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 steps:
   - label: 'job1'
@@ -130,7 +130,7 @@ steps:
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 version: 2.1
 jobs:
@@ -164,7 +164,7 @@ workflows:
 2+| Execute jobs on multiple platforms. Buildkite uses tags to identify build agents. CircleCI provides executors for Docker, Linux and macOS.
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 steps:
   - label: 'ubuntuJob'
@@ -180,7 +180,7 @@ steps:
 ----
 
 a|
-[source,yaml,role="no-numbers"]
+[source,yaml]
 ----
 jobs:
   ubuntuJob: