style(doc): added section about detect.target.type to the running page
@@ -153,9 +153,33 @@ export DETECT_DOWNLOAD_ONLY=1
./${bash_script_name}
````
+## Choosing the target type
+
+${solution_name} will select a workflow based in part on the target type you select via the *detect.target.type* property.
+
+When running ${solution_name} on project source code, you'll probably want to
+set *detect.target.type* to *SOURCE*, or leave *detect.target.type* unset (since
+*SOURCE* is the default value).
+
+When running ${solution_name} on a Docker image, you'll probably want to
+set *detect.target.type* to *IMAGE*.
+
+### Common workflows
+
+By default (detect.target.type=SOURCE), ${solution_name} will run the following on the source directory:
+
+1. Any applicable detectors
+1. ${blackduck_signature_scanner_name}
+
+When a Docker image is provided and property *detect.target.type* is set to IMAGE, ${solution_name} will run the following on the image:
+
+1. Docker Inspector
+1. ${blackduck_signature_scanner_name}
+1. ${blackduck_binary_scan_capability}
+
## Including and excluding tools and detectors
-[Properties](../properties/all-properties/) provide a variety of options for configuring ${solution_name} behavior. One of the
+[Properties](../properties/all-properties/) provide a variety of additional options for configuring ${solution_name} behavior. One of the
most fundamental ways to modify ${solution_name} is by including and excluding [tools](../components/tools/) and [detectors](../components/detectors/).
### Tools
