Blade deploy does not follow a specific configuration. It defaults to the current build tool's (Gradle/Maven) deployment configuration. Express this in the docs.
Also include an explanation for the -l flag, which uses Gogo to deploy a module JAR straight to the OSGi container. This was the old way of doing Blade deployment.