-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
2
-
False
-
-
False
-
-
-
None
| I don't agree with renaming it back to "CLI Guide". We renamed the title for certain reasons. "CLI Guide" goes against our guidelines for naming the docs/headings/title/etc. Moreover, it'll go against all the CQA and JTBD initiatives that will change the docs completely. "CLI Guide" is a very unclear name that doesn't express what the title is about. And from my POV, "CLI Guide" doesn't make it clearer that there are sections on platform awareness and asset generation. So, no to the renaming it back to "CLI Guide" from my side. We must comply with the doc requirements. But I have another solution: What about adding information about these to the Abstract of the title? We usually create abstracts that contain short info on what is in the title. Currently, the Abstract has the following text: "By using the Migration Toolkit for Applications (MTA) command-line interface (CLI), you can assess and prioritize migration and modernization efforts for applications written in different languages. You can use the CLI to customize MTA analysis options or integrate with external automation tools. " But we can enhance it by adding information on assets generation, for example: "By using the Migration Toolkit for Applications (MTA) command-line interface (CLI), you can assess and prioritize migration and modernization efforts for applications written in different languages. You can use the CLI to customize MTA analysis options or integrate with external automation tools. You can also use the MTA CLI to generate the manifests needed to deploy a Cloud Foundry (CF) application in the OpenShift Container Platform." WDYT? |
