Merge pull request magento-commerce/devdocs#2619

DOC-515: Rearrange QPT and add a widget

Author: dshevtsov

src/_data/toc/software-update-guide.yml

@@ -69,21 +69,22 @@ pages:
     - label: Add or update components
       url: /install-gde/install/cli/dev_add-update.html
 
-    - label: Apply patches
-      url: /comp-mgr/patching.html
+    - label: Quality Patches Tool
+      url: /quality-patches/tool.html
+      versionless: true
       children:
 
-       - label: Quality Patches Tool
-         url: /comp-mgr/patching/mqp.html
-         children:
+        - label: Usage
+          url: /quality-patches/usage.html
+          versionless: true
 
-           - label: Quality patches for Adobe Commerce
-             url: /quality-patches/release-notes-commerce.html
-             versionless: true
+        - label: Release notes
+          url: /quality-patches/release-notes.html
+          versionless: true
 
-           - label: Quality patches for Magento Open Source
-             url: /quality-patches/release-notes-open-source.html
-             versionless: true
+    - label: Apply patches
+      url: /comp-mgr/patching.html
+      children:
 
        - label: Command Line
          url: /comp-mgr/patching/command-line.html

src/_data/whats-new.yml

@@ -330,7 +330,7 @@ entries:
   - Major Update
   - 2.4.3
 - description: Added [Community quality patches release notes](https://github.com/magento/quality-patches/blob/master/community-release-notes.md)
-    to a table of contents at [Commerce Quality Patches](https://devdocs.magento.com/guides/v2.4/comp-mgr/patching/mqp.html).
+    to a table of contents at [Commerce Quality Patches](https://devdocs.magento.com/quality-patches/usage.html).
   versions: 2.x
   type: Major Update
   date: August 27, 2021

src/_includes/install/patch/quality-patch-intro.md

@@ -1,5 +1,5 @@
 The [Quality Patches Tool](https://github.com/magento/quality-patches) delivers individual patches developed by Adobe and the {{ site.data.var.ce }} community. It allows you to apply, revert, and view general information about all individual patches that are available for the installed version of {{ site.data.var.ee }} or {{ site.data.var.ce }}. You can apply patches to {{site.data.var.ee}} and {{site.data.var.ce}} projects regardless of who developed the patch. For example, you can apply a patch developed by the community to {{site.data.var.ee}} projects.
 
 {:.bs-callout-info}
-See [Apply patches]({{ site.baseurl }}{{ site.gdeurl }}/comp-mgr/patching/mqp.html) for instructions on applying patches to your {{ site.data.var.ee }} or {{ site.data.var.ce }} projects.
+See [Apply patches]({{ site.baseurl }}/quality-patches/usage.html) for instructions on applying patches to your {{ site.data.var.ee }} or {{ site.data.var.ce }} projects.
 See [Patches available in the Quality Patches Tool](https://support.magento.com/hc/en-us/sections/360010506631-Patches-available-in-MQP-tool-) for additional patch details.

src/cloud/project/project-patch.md

@@ -14,7 +14,7 @@ functional_areas:
 Both packages improve the integration of all {{site.data.var.ee}} versions with Cloud environments and support quick delivery of critical, optional, and custom fixes. You can use these packages to apply, revert, and view general information about all individual patches that are available for Magento.
 
 {:.bs-callout-tip}
-You can use the [Quality Patches Tool]({{ site.baseurl }}{{ site.gdeurl }}/comp-mgr/patching/mqp.html) and [{{ site.data.var.mcp-prod }}](#standalone) packages as stand-alone packages for {{ site.data.var.ce }} and {{ site.data.var.ee }} projects. We recommend using the Quality Patches Tool for non-Cloud projects.
+You can use the [Quality Patches Tool]({{ site.baseurl }}/quality-patches/usage.html) and [{{ site.data.var.mcp-prod }}](#standalone) packages as stand-alone packages for {{ site.data.var.ce }} and {{ site.data.var.ee }} projects. We recommend using the Quality Patches Tool for non-Cloud projects.
 
 When you deploy changes to the remote environment, `{{site.data.var.ct}}` uses {{ site.data.var.mcp-package }} and `magento/quality-patches` to check for pending patches and applies them automatically in the following order:
 
@@ -201,7 +201,7 @@ To apply and test a custom patch on a Cloud environment:
 
 ## Apply patches to a non-Cloud project {#standalone}
 
-Use the [Quality Patches Tool]({{ site.baseurl }}{{ site.gdeurl }}/comp-mgr/patching/mqp.html) for {{ site.data.var.ce }} and {{ site.data.var.ee }} projects.
+Use the [Quality Patches Tool]({{ site.baseurl }}/quality-patches/usage.html) for {{ site.data.var.ce }} and {{ site.data.var.ee }} projects.
 
 ## Revert a patch in a local environment
 

src/common/js/qpt.app.min.js

@@ -1,16 +1,19 @@
 ---
 group: software-update-guide
-title: Quality patches for Adobe Commerce
+title: Release notes
 functional_areas:
   - Setup
   - Configuration
   - Upgrade
-redirect_from: /quality-patches/release-notes.html
+redirect_from:
+  - /quality-patches/release-notes-commerce.html
+  - /quality-patches/release-notes-open-source.html
 ---
 
 {% include install/patch/quality-patch-intro.md %}
 
-For information about quality patches created by the community for {{site.data.var.ce}}, see the [release notes](https://github.com/magento/quality-patches/blob/master/community-release-notes.md).
+{: .bs-callout-info}
+For information about quality patches created by the Community for {{site.data.var.ce}}, see the [release notes](https://github.com/magento/quality-patches/blob/master/community-release-notes.md).
 
 <!-- The release notes include:
 
@@ -138,7 +141,7 @@ For information about quality patches created by the community for {{site.data.v
 
 ## v1.0.20
 
--  **MDVA-36170** _(for Magento `>=2.3.4 <2.4.2`)_-This fixes the issue where the GraphqQL query is not caching by using the category cache tag.
+-  **MDVA-36170** _(for Magento `>=2.3.4 <2.4.2`)_-This fixes the issue where the GraphQL query is not caching by using the category cache tag.
 -  **MDVA-33168** _(for Magento `>=2.3.3 <2.4.2`)_-Fixes the issue when updating a product attribute via API all other attributes change to an empty value.
 -  **MDVA-19640** _(for Magento `>=2.3.0`)_-Fixes the issue where Advanced Reporting is not showing any data.
 -  **MDVA-11189**  _(for Magento `>=2.3.0 <2.3.5`)_-Fixes the issue when after importing a .csv file to update product stock, rows from the cataloginventory_stock table are deleted.

src/guides/v2.4/comp-mgr/patching/mqp.md

@@ -0,0 +1,42 @@
+---
+group: software-update-guide
+title: Quality Patches Tool
+functional_areas:
+  - Upgrade
+---
+
+The [Quality Patches Tool][github] is a command-line tool that delivers
+quality patches for {{site.data.var.ee}} and {{site.data.var.ce}}.
+
+It allows you to:
+
+*  View general information about the latest quality patches
+*  Apply quality patches
+*  Revert applied patches
+
+**{{site.data.var.ee}} support** and the **{{site.data.var.ce}} community** develop quality patches.
+
+{: .bs-callout-note}
+The Quality Patches Tool is for quality patches only. Security patches
+are available in the [Magento Security Center][security] .
+
+## Available patches   {#patch-grid}
+
+<div id="root"></div>
+
+<script src="{{ site.baseurl }}/common/js/qpt.app.min.js?v=1"></script>
+
+## Related topics   {#related-topics}
+
+*  [Quality Patches Tool release notes][notes]
+*  [How to install and use Quality Patches Tool for Adobe Commerce on
+  cloud infrastructure][cloud]
+*  [How to install and use Quality Patches Tool for Adobe Commerce &
+  Magento Open Source][standalone]
+
+<!-- link definitions -->
+[cloud]: {{ site.baseurl }}/cloud/project/project-patch.html
+[github]: https://github.com/magento/quality-patches
+[notes]: {{ site.baseurl }}/quality-patches/release-notes.html
+[security]: https://magento.com/security/patches
+[standalone]: {{ site.baseurl }}/quality-patches/usage.html

src/quality-patches/release-notes-open-source.md

@@ -1,16 +1,19 @@
 ---
 group: software-update-guide
-title: Quality Patches Tool
+title: Usage
 functional_areas:
   - Upgrade
+redirect_from:
+   - guides/v2.4/comp-mgr/patching/mqp.html
+   - guides/v2.3/comp-mgr/patching/mqp.html
 ---
 
 {% include install/patch/quality-patch-intro.md %}
 
 {:.bs-callout-warning}
 We do not recommend using the Quality Patches Tool to apply large numbers of patches because it increases the complexity of your code, which makes upgrading to a new version of {{ site.data.var.ee }} or {{ site.data.var.ce }} more difficult.
 
-#### Install
+## Install
 
 {:.bs-callout-info}
 If it is not already installed, you must install [Git](https://github.com/git-guides/install-git) or [Patch](https://man7.org/linux/man-pages/man1/patch.1.html) before installing the Quality Patches Tool.
@@ -20,7 +23,7 @@ Add the `magento/quality-patches` Composer package to your `composer.json` file:
 composer require magento/quality-patches
 ```
 
-#### View individual patches
+## View individual patches
 
 To view the list of individual patches available for your version of {{ site.data.var.ee }} or {{ site.data.var.ce }}:
 
@@ -86,10 +89,10 @@ The status table contains the following types of information:
 {:.bs-callout-info}
 After upgrading to a new version of {{ site.data.var.ee }} or {{ site.data.var.ce }}, you must re-apply patches if the patches are not included in the new version. See [Re-apply patches after an upgrade](#upgrade).
 
-#### Apply individual patches
+## Apply individual patches
 
 {:.bs-callout-warning}
-We strongly recommend testing all patches in a staging or development environment before deploying to production. We also strongly recommend backing up your data before applying a patch. See [Back up and roll back the file system]({{ page.baseurl }}/install-gde/install/cli/install-cli-backup.html).
+We strongly recommend testing all patches in a staging or development environment before deploying to production. We also strongly recommend backing up your data before applying a patch. See [Back up and roll back the file system][backup].
 
 To apply a single patch, run the following command where `MAGETWO-XXXX` is the patch ID specified in the status table:
 
@@ -112,10 +115,10 @@ You must clean the cache after applying patches to see changes in the Magento ap
 {:.bs-callout-info}
 Consider keeping a list of applied patches in a separate location. You might need to re-apply some of them after upgrading to a new version of {{ site.data.var.ee }} or {{ site.data.var.ce }}. See [Re-apply patches after an upgrade](#upgrade).
 
-#### Revert individual patches
+## Revert individual patches
 
 {:.bs-callout-warning}
-We strongly recommend testing all patches in a staging or development environment before deploying to production. We also strongly recommend backing up your data before applying a patch. See [Back up and roll back the file system]({{ page.baseurl }}/install-gde/install/cli/install-cli-backup.html).
+We strongly recommend testing all patches in a staging or development environment before deploying to production. We also strongly recommend backing up your data before applying a patch. See [Back up and roll back the file system][backup].
 
 To revert a single patch, run the following command where `MAGETWO-XXXX` is the patch ID specified in the status table:
 
@@ -141,7 +144,7 @@ You must clean the cache after reverting patches to see changes in the Magento a
 ./bin/magento cache:clean
 ```
 
-#### Get updates
+## Get updates
 
 Magento periodically releases new individual patches. You must update the Quality Patches Tool to get new individual patches:
 
@@ -158,7 +161,7 @@ New add patches display at the bottom of the table.
 ./vendor/bin/magento-patches status
 ```
 
-#### Re-apply patches after an upgrade {#upgrade}
+## Re-apply patches after an upgrade {#upgrade}
 
 When you upgrade to a new version of {{ site.data.var.ee }} or {{ site.data.var.ce }}, you must re-apply patches if the patches are not included in the new version.
 
@@ -190,6 +193,9 @@ To re-apply patches:
    {:.bs-callout-info}
    When you run the `status` command, the patches that where included in the new version are no longer displayed in the table of available patches.
 
-#### Logging
+## Logging
 
 The Quality Patches Tool logs all operations in the `<Magento_root>/var/log/patch.log` file.
+
+<!-- link definitions -->
+[backup]: {{ site.baseurl }}{{ site.gdeurl }}/install-gde/install/cli/install-cli-backup.html