Here's some minor, initial feedback for procedural output generated by docs-workflow. In general, I think steps are a bit noisy. - There were optional cmd line flags added in additional cmd line examples under a single step. These would probably be better either removed as they're doc'd in the tool's cmd line reference table, or added to the initial step and explained with callouts there. Otherwise we are breaking the 1 step 1 task mantra https://github.com/mcljot/openshift-docs/pull/3/changes#diff-e29e8612dde8af066ec63f1056a4f9f01d499e7c96070bc888c6a3b5bfd34e2eR45-R70 (The note could also be a prereq instead of adding noise to the step) - Using substeps, instead of bulleted options within a step, would probably translate better to DITA semantic structure best practices: https://github.com/mcljot/openshift-docs/pull/3/changes#diff-e29e8612dde8af066ec63f1056a4f9f01d499e7c96070bc888c6a3b5bfd34e2eR95-R111
Here's some minor, initial feedback for procedural output generated by docs-workflow. In general, I think steps are a bit noisy.
There were optional cmd line flags added in additional cmd line examples under a single step. These would probably be better either removed as they're doc'd in the tool's cmd line reference table, or added to the initial step and explained with callouts there. Otherwise we are breaking the 1 step 1 task mantra https://github.com/mcljot/openshift-docs/pull/3/changes#diff-e29e8612dde8af066ec63f1056a4f9f01d499e7c96070bc888c6a3b5bfd34e2eR45-R70
(The note could also be a prereq instead of adding noise to the step)
Using substeps, instead of bulleted options within a step, would probably translate better to DITA semantic structure best practices:
https://github.com/mcljot/openshift-docs/pull/3/changes#diff-e29e8612dde8af066ec63f1056a4f9f01d499e7c96070bc888c6a3b5bfd34e2eR95-R111