Expand-app-developers-pages

content/docs/for-app-developers/concepts/build.md

@@ -23,5 +23,4 @@ Builders provide a convenient way to distribute buildpacks.
 [build-time base image]: /docs/for-app-developers/concepts/base-images/build/
 [builder]: /docs/for-platform-operators/concepts/builder
 [buildpack]: /docs/for-app-developers/concepts/buildpack/
-[lifecycle]: /docs/for-platform-operators/concepts/lifecycle/
 [runtime base image]: /docs/for-app-developers/concepts/base-images/run/

content/docs/for-app-developers/concepts/experimental-features.md

@@ -0,0 +1,27 @@
++++
+title="What are experimental features?"
+weight=8
++++
+
+Certain features are considered `experimental` and susceptible to change in a future API version.
+
+<!--more-->
+
+This means users will need to enable the `experimental` mode in order to use one of these features.
+
+To enable these features, run `pack config experimental true`, or add `experimental = true` to the `~/.pack/config.toml` file.
+
+For example, exporting your application to disk in `OCI` layout format is an experimental feature available on `pack` since version `v0.30.0`.
+
+The following is a list of experimental features:
+
+* Image extensions
+* Windows extensions
+* Windows containers
+* Windows buildpackage
+* Buildpack registry
+* Flattening a buildpack package
+
+For more information and to look at an example of how this might be valuable, see [Export to OCI layout format on disk][exp-feature].
+
+[exp-feature]: https://buildpacks.io/docs/for-app-developers/how-to/special-cases/export-to-oci-layout/

content/docs/for-app-developers/how-to/build-inputs/specify-default-launch-process.md

@@ -4,6 +4,19 @@ weight=99
 summary="Buildpacks can define multiple processes for an application image. Specify which process should be the default."
 +++
 
-This page is a stub! The CNB project is applying to [Google Season of Docs](https://developers.google.com/season-of-docs/docs/timeline) to receive support for improving our documentation. Please check back soon.
+Buildpacks usually define the default process type for an application, while retaining the ability for a user to specify their desired default process.
 
-If you are familiar with this content and would like to make a contribution, please feel free to open a PR :)
+To configure the `build` to work differently from the default behavior:
+
+* You first need to know what processes would be contributed by the buildpacks running in your build.
+* Once known, you can append the following flag to the `pack build` command
+
+```bash
+pack build --default-process <process name> <image name>` # <process name> must be a valid process name in launch.toml
+```
+
+If this flag is not provided by the user, `pack` will provide the process type as `web` to the `lifecycle`.
+
+>As an app developer, you can specify the default process for an application. However, buildpacks-built images can contain multiple process types, to see how to invoke each one, see the [Run the application] page.
+
+[Run the application]: https://buildpacks.io/docs/for-app-developers/how-to/build-outputs/specify-launch-process/

content/docs/for-app-developers/how-to/build-outputs/inspect-app.md

@@ -8,15 +8,19 @@
 <!--more-->
 
 Information includes:
+
 * The process types that are available and the commands associated with them
 * The run-image the app image was based on
 * The buildpacks were used to create the app image
 * Whether the run-image can be rebased with a new version through the `Rebasable` label or not
 * And more...!
 
+`Pack` offers a built-in command to help you inspect the resultant image and view some of its contents as shown below:
+
 ```bash
 pack inspect-image test-node-js-app
 ```
+
 You should see the following:
 
 ```text
@@ -35,4 +39,25 @@
 
 Apart from the above standard metadata, buildpacks can also populate information about the dependencies they have provided in form of a `Software Bill-of-Materials` or [SBOM].
 
+As already mentioned, buildpacks help you get an `OCI` images that are constructed in a way that’s easy to understand and update with each of the layers being meaningful and independent of all other layers. You can get more details about each layer and how it was created to better understand how the [Build] actually worked.
+
+There are some available tools that help you achieve this and understand what is contained in your `OCI` image; a popular one is [Dive].
+
+Dive can help you inspect `OCI` images, view their layers and each layer's details. If you were to build an `OCI` image following the [multi process app] example and run `Dive` on the generated image, you'll be presented with some detailed information about all of the image layers and understand what is in each layer.
+
+You can use `Dive` as follows:
+
+```bash
+dive multi-process-app
+```
+
+The output should look similar to the following:
+
+PLACEHOLDER
+
+As seen in the output above, you're presented with `Layers`, `Layer Details`, `Image Details`, and `Current Layer Contents`. To view the contents or explore the file tree of any layer, you need to select the layer on the left using the arrow keys.
+
 [SBOM]: /docs/for-app-developers/how-to/build-outputs/download-sbom
+[build]: https://buildpacks.io/docs/for-app-developers/concepts/build/
+[Dive]: https://github.com/wagoodman/dive
+[multi process app]: https://buildpacks.io/docs/for-app-developers/how-to/build-outputs/specify-launch-process/#build-a-multi-process-app

content/docs/for-app-developers/how-to/build-outputs/specify-launch-process.md

@@ -1,4 +1,3 @@
-
 +++
 title="Run the application"
 aliases=[
@@ -15,7 +14,8 @@ Buildpacks-built images can contain multiple process types.
 For this example we will use the `hello-processes` buildpack from our [samples][samples] repo so make sure you have it cloned locally.
 
 Let's build the app.
-```
+
+```bash
 pack build multi-process-app \
     --builder cnbs/sample-builder:alpine \
     --buildpack samples/java-maven \
@@ -26,14 +26,14 @@ pack build multi-process-app \
 
 If you inspect the app image with `pack`, you will see multiple process types defined:
 
-```
+```bash
 pack inspect-image multi-process-app
 ```
 <!--+- "{{execute}}"+-->
 
 The output should look similar to the below:
 
-```
+```text
 Inspecting image: multi-process-app
 
 REMOTE:
@@ -76,16 +76,18 @@ The `launcher` will source any profile scripts (for `non-direct` processes) and
 
 If you would like to run the default process, you can simply run the app image without any additional arguments:
 
-```
+```bash
 docker run --rm -p 8080:8080 multi-process-app
 ```
 <!--+- "{{execute}}"+-->
 
+>As an app developer, you can specify what the default process is, see [specify default launch process][default-process] page for more information.
+
 #### Default process type with additional arguments
 
 If you would like to pass additional arguments to the default process, you can run the app image with the arguments specified in the command:
 
-```
+```bash
 docker run --rm -p 8080:8080 multi-process-app --spring.profiles.active=mysql
 ```
 <!--+- "{{execute interrupt}}"+-->
@@ -94,7 +96,7 @@ docker run --rm -p 8080:8080 multi-process-app --spring.profiles.active=mysql
 
 To run a non-default process type, set the process type as the entrypoint for the run container:
 
-```
+```bash
 docker run --rm --entrypoint sys-info multi-process-app
 ```
 <!--+- "{{execute interrupt}}"+-->
@@ -103,7 +105,7 @@ docker run --rm --entrypoint sys-info multi-process-app
 
 You can pass additional arguments to a non-default process type:
 
-```
+```bash
 docker run --rm --entrypoint sys-info multi-process-app --spring.profiles.active=mysql
 ```
 <!--+- "{{execute interrupt}}"+-->
@@ -112,21 +114,24 @@ docker run --rm --entrypoint sys-info multi-process-app --spring.profiles.active
 
 You can even override the buildpack-defined process types:
 
-```
+```bash
 docker run --rm --entrypoint launcher -it multi-process-app bash
 ```
 <!--+- "{{execute interrupt}}"+-->
 
-Now let's exit this shell and run an alternative entrypoint - 
-```
+Now let's exit this shell and run an alternative entrypoint -
+
+```bash
 exit
 ```
 <!--+- "{{execute interrupt}}"+-->
-```
+
+```bash
 docker run --rm --entrypoint launcher -it multi-process-app echo hello "$WORLD" # $WORLD is evaluated on the host machine
 ```
 <!--+- "{{execute interrupt}}"+-->
-```
+
+```bash
 docker run --rm --entrypoint launcher -it multi-process-app echo hello '$WORLD' # $WORLD is evaluated in the container after profile scripts are sourced
 ```
 <!--+- "{{execute interrupt}}"+-->
@@ -135,7 +140,7 @@ docker run --rm --entrypoint launcher -it multi-process-app echo hello '$WORLD'
 
 An entire script may be provided as a single argument:
 
-```
+```bash
 docker run --rm --entrypoint launcher -it multi-process-app 'for opt in $JAVA_OPTS; do echo $opt; done'
 ```
 <!--+- "{{execute interrupt}}"+-->
@@ -145,7 +150,7 @@ docker run --rm --entrypoint launcher -it multi-process-app 'for opt in $JAVA_OP
 By passing `--` before the command, we instruct the `launcher` to start the provided process without `bash`.
 Note that while buildpack-provided environment variables will be set in the execution environment, no profile scripts will be sourced (as these require `bash`):
 
-```
+```text
 docker run --rm --entrypoint launcher multi-process-app -- env # output will include buildpack-provided env vars
 docker run --rm --entrypoint launcher multi-process-app -- echo hello "$WORLD" # $WORLD is evaluated on the host machine
 docker run --rm --entrypoint launcher multi-process-app -- echo hello '$WORLD' # $WORLD is not evaluated, output will include string literal `$WORLD`
@@ -155,11 +160,12 @@ docker run --rm --entrypoint launcher multi-process-app -- echo hello '$WORLD' #
 
 You can bypass the launcher entirely by setting a new entrypoint for the run container:
 
-```
+```bash
 docker run --rm --entrypoint bash -it multi-process-app # profile scripts have NOT been sourced and buildpack-provided env vars are NOT set in this shell
 ```
 <!--+- "{{execute interrupt}}"+-->
 
 To learn more about the launcher, see the [platform spec](https://github.com/buildpacks/spec/blob/main/platform.md#launcher).
 
 [samples]: https://github.com/buildpacks/samples
+[default-process]: https://buildpacks.io/docs/for-app-developers/how-to/build-inputs/specify-default-launch-process/

content/docs/for-app-developers/how-to/build-outputs/understand-failures.md

@@ -4,6 +4,6 @@ weight=99
 summary="How to troubleshoot when things go wrong."
 +++
 
-This page is a stub! The CNB project is applying to [Google Season of Docs](https://developers.google.com/season-of-docs/docs/timeline) to receive support for improving our documentation. Please check back soon.
+While `Buildpacks` help developers transform applications' source code into container images that can run on any cloud, creating an error-free experience remains far from achieved.
 
-If you are familiar with this content and would like to make a contribution, please feel free to open a PR :)
+This guide explores some of the most common issues that may prevent image build completion and provides troubleshooting tips to help end-users navigate these issues.