Merge branch 'main' into slsa-doc

Author: Chr1st1anSears

docs/modules/ROOT/images/.DS_Store

@@ -1,11 +1,11 @@
 * Concepts
 ** xref:concepts/slsa/con_slsa-conformity.adoc[Supply chain security through SLSA conformity]
-** xref:concepts/RenovateBot/index.adoc[RenovateBot]
 ** xref:concepts/java-build-service/java-build-service.adoc[Java build service]
 ** xref:concepts/java-build-service/java-build-service-components.adoc[Java build service components]
 
 ////
 Adam Kaplan said that the index.adoc for Pipelines, and presumably the other docs in that directory, need to be rewritten, since index.adoc was based on an old version of {ProductName} that used KCP. --Christian csears@redhat.com 3/1/23
+** xref:concepts/RenovateBot/index.adoc[RenovateBot]
 ** xref:concepts/pipelines/index.adoc[Pipelines]
 *** xref:concepts/pipelines/persister.adoc[Persister component]
 *** xref:concepts/pipelines/pipeline_concepts.adoc[Pipeline concepts]

docs/modules/ROOT/images/Application_route.png

@@ -1,4 +1,4 @@
-= Getting started
+= Getting started with {ProductName}
 
 {ProductName} is a multi-tenant, software as a service (SaaS) based continuous integration and continuous delivery (CI/CD) service with an emphasis on secure supply chain features.
 
@@ -11,16 +11,12 @@ Let’s get you signed up!
 == Creating your first application
 We include ready-to-use bundled code samples that you can import into our service. In this guide, we’ll walk you through how to fork a sample repository and create your first application. 
 
-=== Naming your application
-Every great app needs a name – add yours! 
-
-. Select *Create an application*. 
-. Name your application.
+To begin the process, click *Create an application*. 
 
 === Choosing a bundled sample
 
-. Click *Start with a sample*.
-. Choose one of the following options: 
+Scroll to the section *Select a sample* and choose one of the following options: 
+
 * Node.js
 * Quarkus
 * Spring Boot
@@ -33,19 +29,20 @@ Decided on a favorite sample? Great! Now let’s fork the code to your repo in t
 
 ==== Why should you fork a sample?
 
-There are many perks to forking one of our samples, this list shows a few:
+There are many perks to forking one of our samples, for example:
 
 * Pipeline customization
 * Automated builds for new commits with GitHub webhook integration
 * Pull request testing
 * Rebuilding dependencies from source
 * Scanning your build for vulnerabilities, viruses, and other checks
 
+[#How to fork a sample]
 ==== How to fork a sample
 
 To fork the sample, complete the following steps:
 
-. In the sample that you chose, click *Git repository*. This link takes you to GitHub.
+. Click *Open Git repository* for the sample that you chose. This link takes you to GitHub.
 . Now that you’re in GitHub, click *Fork*.
 . Copy the URL of this new forked repository. We'll use this URL in the next section! 
 
@@ -54,50 +51,60 @@ To fork the sample, complete the following steps:
 Right now we support GitHub, but come back soon for other Git providers! 
 ====
 
+
 === Importing the code from your forked repository
 
-. Return to the app and go back to the *Select a sample* view. 
-. Click *Import your code*.
-. In *Git repo URL*, paste the URL that you copied in the previous section.
-. Click *Next*.
+. Return to the app and scroll up to *Bring in your own code*. 
+. In *Git repository URL*, paste the URL that you copied in the previous section.
+. Click *Import code*.
 
+[#Reviewing and configuring]
 === Reviewing and configuring
-We scan your Git repository for source code and detect your runtime and other configuration settings for you to review. You have the option to use our default build pipeline or to customize the pipeline. 
+We now scan your Git repository for source code and detect your runtime and other configuration settings for you to review. You have the option to use our default build pipeline or to customize the pipeline. Let's stick with the default option for now. 
+
+Complete the following steps to finish the process:
 
-For now, select *Default*.
+. In *Application details*, enter a name for your app.
+. In *Component name*, enter a name for your component. 
+. Leave the toggle set to *Default build pipeline*.
+. Scroll to the end of the page and click *Create application*.
 
 == Congrats!
 
-Now click *Create* and we’ll start building your application. We build an image from the source code of this sample.
+Now, we build an image from the source code of your sample. 
 
-== Next steps
+Great work! You're done with the first steps.
+
+== Advanced options
 
 === Adding more components 
 
 Because your application can run on one or more components, you might want to add more. 
 
-The additional source code that you add can either be from the same repository that you used when you created your application, _or_ a different Git repository. Remember, we call source code _components_.
+The additional source code that you add can either be from the _same_ repository that you used when you created your application, or a _different_ Git repository. Remember, we call source code _components_.
 
 In the *Overview* tab, select *Add component*:
 
 image::Add_more_components.png[Overview tab that shows how you can add additional components to your application. The Overview button is on the bottom left and has a red arrow next to it.]
 
+Follow the process in <<How to fork a sample>> to add any additional components. 
+
 === Customizing your build pipeline
 
-To add automation, you can upgrade your default build pipelines to custom build pipelines. 
+In the <<Reviewing and configuring>> section, you used the default built pipeline. To add automation, you can upgrade to custom build pipelines. 
 
 Custom build pipelines are pipelines as code, set on your component's repository. With custom build pipelines, pull requests and commits to your main branch automatically rebuild. 
 
 By customizing your build pipeline, you can change the tasks that are included, control when those tasks update to newer versions, and accept any changes to the pipeline when you're ready for them.
 
-To get started, click *Manage build pipelines* from the *Overview* page.
+To get started, click *Manage build pipelines* from the *Overview* page. For more information on this topic, go to xref:how-to-guides/proc_upgrade_build_pipeline.adoc[Upgrading your build pipeline].
 
 === Viewing your activity 
 You can view your latest commits, as well as your pipeline runs. 
 
 ==== Viewing your latest commits
 
-Since you forked your repo, you have permissions to commit to the Git repo. We like to focus on commits, rather than pipelines, so that it’s easy to correlate a developer's work with what’s going on in the system. 
+Because you forked your repo, you have permissions to commit to the Git repo. We like to focus on commits, rather than pipelines, so that it’s easy to correlate a developer's work with what’s going on in the system. 
 
 To view your recent commits, go to the *Activity* tab and click *Latest commits*. 
 
@@ -107,40 +114,39 @@ Didn’t fork your repo? Fret not! You can also view your activity by pipeline r
 
 To view your pipeline runs, go to the *Activity* tab and click *Pipeline runs*. 
 
-=== Adding an integration test
-
-An integration test is a pipeline that you set up in GitHub. When you add components, it tests each one individually, and then tests the application as a whole.
+The following image shows the *Pipeline run details*:
 
-To add an integration test, complete the following steps:
+image::Pipeline-runs.png[View of an application's pipeline runs. Multiple tasks are depicted in a tree flow and the user can click on a task to view more details.]
 
-. Go to the *Integration tests* tab.
-. Click *Add integration test*.
-. Enter a name for your test, a path to the container image, and the name of the pipeline that you want to run. 
-. Click *Add integration test*.
+In the previous view, you can see tasks that you can run based on the pipeline definition while the image is being inspected. You can also click an individual task to see its details. 
 
-=== Viewing your application route 
+=== Viewing your application route
 
-You can find each component’s route in the *Components* tab, next to each component’s details:
+You can find each component’s route in the *Components* tab, next to each component’s details. 
 
-////
-image::modules/ROOT/images/View-application-route.png[The Components tab has a hyperlink called Route that opens the current component's route.]
-////
+Refer to the following image:
 
-=== Examining your integration test results
+image::Application_route.png[In the Components tab, there is a link called Route next to every component that takes you to the application route.]
 
-You can view your test results in two different ways: 
+=== Managing compliance with Enterprise Contract 
+The Enterprise Contract (EC) is an artifact verifier and customizable policy checker. You can use EC to keep your software supply chain secure and to ensure that container images comply with your organization’s policies. 
 
-* Go to the *Activity* tab and select *Pipeline runs*.
-* View your integration test log output by selecting *Logs*:
-
-image::Logs_step2.png[In Activity after you select Pipeline runs, there is a tab called Logs.]
+For more information about EC, refer to xref:how-to-guides/proc_managing-compliance-with-the-enterprise-contract.adoc[Managing compliance with the Enterprise Contract].
 
 === Deploying your app 
 Check the status of your application in *Environments*. You can view information about your environment such as its type, strategy, and deployment status:
 
 image::Environments.png[The Environments tab shows the type of your environment, its deployment strategy, the cluster type, the application status, the last deploy, and the applications deployed. In this example, the type is Default, the strategy is Automatic, the cluster type is OpenShift, the Application status is Missing, the Last deploy is -, and there are 3 applications deployed.]
 
-An environment is a set of compute resources that you can use to develop, test, and stage your applications.
+An environment is a set of compute resources that you can use to develop, test, and stage your applications. There is a development environment included for you so that you can explore {ProductName}.
+
+For information about creating an application with your own cluster, refer to xref:how-to-guides/proc_creating_your_own_environment.adoc[Creating your own environment].
+
+=== Examining your SBOM
+
+A software bill of materials (SBOM) is a list of all the software libraries that a component uses. You can run 'cosign' in your command line interface (CLI) to inspect the image SBOM.
+
+For more information on this topic, go to xref:how-to-guides/Secure-your-supply-chain/proc_inspect_sbom.adoc[Inspecting SBOMs].
 
 == Great work!
 Congrats on creating your first application!