Correct broken *.md links (#7108)

Author: nielslange

README.md

@@ -1,7 +1,7 @@
 # WooCommerce Blocks <!-- omit in toc -->
 
 [![Latest Tag](https://img.shields.io/github/tag/woocommerce/woocommerce-gutenberg-products-block.svg?style=flat&label=Latest%20Tag)](https://github.com/woocommerce/woocommerce-gutenberg-products-block/releases)
-[![View](https://img.shields.io/badge/Project%20Components-brightgreen.svg?style=flat)](https://woocommerce.github.io/woocommerce-gutenberg-products-block)
+[![View](https://img.shields.io/badge/Project%20Components-brightgreen.svg?style=flat)](https://woocommerce.github.io/woocommerce-blocks/)
 ![JavaScript and CSS Linting](https://github.com/woocommerce/woocommerce-gutenberg-products-block/workflows/JavaScript%20and%20CSS%20Linting/badge.svg?branch=trunk)
 ![PHP Coding Standards](https://github.com/woocommerce/woocommerce-gutenberg-products-block/workflows/PHP%20Coding%20Standards/badge.svg?branch=trunk)
 ![Automated tests](https://github.com/woocommerce/woocommerce-gutenberg-products-block/workflows/Automated%20tests/badge.svg?branch=trunk)

assets/js/base/components/README.md

@@ -1,5 +1,5 @@
 # WooCommerce Blocks - General Purpose Components
 
-These are shared components used in WooCommerce blocks, and may be used in the store front end (shopper experience) as well as the editor or admin dashboard. 
+These are shared components used in WooCommerce blocks, and may be used in the store front end (shopper experience) as well as the editor or admin dashboard.
 
-See [_Components & Storybook_](docs/contributors/storybook.md) doc for more information.
+See [_Components & Storybook_](../../../../docs/contributors/contributing/storybook-and-components.md) doc for more information.

assets/js/data/schema/README.md

@@ -2,7 +2,6 @@
 
 ## Table of contents <!-- omit in toc -->
 
--   [Table of contents](#table-of-contents)
 -   [Actions](#actions)
     -   [`receiveRoutes( routes, namespace = '/wc/blocks' )`](#receiveroutes-routes-namespace--wcblocks-)
 -   [Selectors](#selectors)

assets/js/editor-components/README.md

@@ -4,7 +4,7 @@ These are shared components used in WooCommerce blocks for the editor (Gutenberg
 
 Many of our blocks need rich, smart components to provide an interface for selecting or configuring blocks with WooCommerce data. Often there are multiple blocks that need such components. Components in this collection are used in multiple blocks, and may include logic for working with Woo data specifically (e.g. products, shipping methods, product categories).
 
-See [Storybook & Components](docs/contributors/storybook.md) doc for more information.
+See [Storybook & Components](../../../docs/contributors/contributing/storybook-and-components.md) doc for more information.
 
 <!-- FEEDBACK -->
 

bin/hook-docs/data/actions.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://raw.githubusercontent.com/johnbillion/wp-hooks-generator/0.7.0/schema.json",
+    "$schema": "https://raw.githubusercontent.com/wp-hooks/generator/0.9.0/schema.json",
     "hooks": [
         {
             "name": "woocommerce_add_to_cart",

bin/hook-docs/data/filters.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://raw.githubusercontent.com/johnbillion/wp-hooks-generator/0.7.0/schema.json",
+    "$schema": "https://raw.githubusercontent.com/wp-hooks/generator/0.9.0/schema.json",
     "hooks": [
         {
             "name": "__experimental_woocommerce_blocks_add_data_attributes_to_block",
@@ -339,18 +339,6 @@
             },
             "args": 1
         },
-        {
-            "name": "woocommerce_admin_disabled",
-            "file": "InboxNotifications.php",
-            "type": "filter",
-            "doc": {
-                "description": "",
-                "long_description": "",
-                "tags": [],
-                "long_description_html": ""
-            },
-            "args": 1
-        },
         {
             "name": "woocommerce_apply_individual_use_coupon",
             "file": "StoreApi/Utilities/CartController.php",

bin/hook-docs/format-hook-doc/files.js

@@ -2,7 +2,7 @@ const files = ( sources ) => {
 	return sources && sources.length
 		? {
 				ul: sources.map( ( file ) => {
-					return `[${ file }](../../src/${ file })`;
+					return `[${ file }](../../../../src/${ file })`;
 				} ),
 		  }
 		: null;

docs/README.md

@@ -146,7 +146,7 @@ The following tutorials from [developer.woocommerce.com](https://developer.wooco
 
 [We're hiring!](https://woocommerce.com/careers/) Come work with us!
 
-🐞 Found a mistake, or have a suggestion? [Leave feedback about this document here.](https://github.com/woocommerce/woocommerce-blocks/issues/new?assignees=&labels=type%3A+documentation&template=--doc-feedback.md&title=Feedback%20on%20./docs/readme.md)
+🐞 Found a mistake, or have a suggestion? [Leave feedback about this document here.](https://github.com/woocommerce/woocommerce-blocks/issues/new?assignees=&labels=type%3A+documentation&template=--doc-feedback.md&title=Feedback%20on%20./docs/README.md)
 
 <!-- /FEEDBACK -->
 

docs/contributors/components.md

@@ -2,17 +2,15 @@
 
 This repo includes [Storybook](https://storybook.js.org) tooling so we can test and develop components in isolation.
 
-The storybook is automatically built and published to [GitHub pages](https://woocommerce.github.io/woocommerce-gutenberg-products-block/) on every push to the main branch. See [travis.yml](https://github.com/woocommerce/woocommerce-gutenberg-products-block/blob/trunk/.travis.yml) for details.
-
-<https://woocommerce.github.io/woocommerce-gutenberg-products-block/>
+The storybook is automatically built and published to [GitHub pages](https://woocommerce.github.io/woocommerce-blocks/) on every push to the main branch.
 
 ## Where are our components?
 
 We have components in a few folders, for different contexts.
 
--   [`assets/js/base/components`](https://github.com/woocommerce/woocommerce-gutenberg-products-block/tree/trunk/assets/js/base/components)
--   [`assets/js/editor-components`](https://github.com/woocommerce/woocommerce-gutenberg-products-block/tree/trunk/assets/js/editor-components)
--   [`assets/js/icons`](https://github.com/woocommerce/woocommerce-gutenberg-products-block/tree/trunk/assets/js/icons)
+-   [`assets/js/base/components`](../../assets/js/base/components)
+-   [`assets/js/editor-components`](../../assets/js/editor-components)
+-   [`assets/js/icons`](../../assets/js/icons)
 
 **`assets/js/base/components`** are used in front-end code, as well as editor & admin.
 These components help us build consistent interfaces across the front end (shopper) experience and elsewhere.
@@ -27,7 +25,7 @@ They allow us to build a consistent and powerful UI for merchants for authoring
 
 **`assets/js/icons`** is a suite of icons and SVG images that we use in our interfaces.
 
-For more info about individual components, refer to [Storybook](https://woocommerce.github.io/woocommerce-gutenberg-products-block/) or individual readme files.
+For more info about individual components, refer to [Storybook](https://woocommerce.github.io/woocommerce-blocks/) or individual readme files.
 
 ## How to run Storybook locally and test components
 

docs/contributors/contributing/getting-started.md

@@ -2,19 +2,19 @@
 
 ## Table of contents <!-- omit in toc -->
 
-- [Cloning the Git Repository](#cloning-the-git-repository)
-- [Configuring your WordPress site](#configuring-your-wordpress-site)
-- [Installing dependencies](#installing-dependencies)
-- [Building the plugin files](#building-the-plugin-files)
-    - [Legacy builds](#legacy-builds)
-- [Create a plugin package in ZIP format](#create-a-plugin-package-in-zip-format)
-- [Linting](#linting)
-- [Running the Blocks plugin](#running-the-blocks-plugin)
-- [Developer Tools (Visual Studio Code)](#developer-tools-visual-studio-code)
-    - [EditorConfig](#editorconfig)
-    - [ESLint](#eslint)
-    - [Prettier](#prettier)
-- [Testing](#testing)
+-   [Cloning the Git Repository](#cloning-the-git-repository)
+-   [Configuring your WordPress site](#configuring-your-wordpress-site)
+-   [Installing dependencies](#installing-dependencies)
+-   [Building the plugin files](#building-the-plugin-files)
+    -   [Legacy builds](#legacy-builds)
+-   [Create a plugin package in ZIP format](#create-a-plugin-package-in-zip-format)
+-   [Linting](#linting)
+-   [Running the Blocks plugin](#running-the-blocks-plugin)
+-   [Developer Tools (Visual Studio Code)](#developer-tools-visual-studio-code)
+    -   [EditorConfig](#editorconfig)
+    -   [ESLint](#eslint)
+    -   [Prettier](#prettier)
+-   [Testing](#testing)
 
 Before you can begin contributing to the Blocks plugin there are several steps and tools required to setup your local development environment.
 
@@ -52,7 +52,7 @@ To install dependencies, you will need the following tools installed on your mac
 -   [`npm` and `node.js`](https://nodejs.org)
 -   [`composer`](https://getcomposer.org)
 
-See [`package.json` `engines`](../../package.json) for details of required versions.
+See [`package.json` `engines`](../../../package.json) for details of required versions.
 
 Once you have `node` and `composer` setup, install the dependencies from the command line:
 
@@ -79,7 +79,7 @@ This plugin supports two type of builds:
 
 The legacy builds are loaded in a site environment where the WordPress version doesn't meet minimum requirements for a component used in a set build.
 
-You can read more about legacy builds in the [this doc](./assets/js/legacy/README.md).
+You can read more about legacy builds in the [this doc](../../../assets/js/legacy/README.md).
 
 ## Create a plugin package in ZIP format
 
@@ -96,9 +96,9 @@ Run `$ npm run lint` to check code against our linting rules.
 
 This script runs 3 sub-commands: `lint:php`, `lint:css`, `lint:js`. Use these to run linters across the codebase (linters check for valid syntax).
 
--   `lint:php` runs phpcs via composer, which uses the [phpcs.xml](https://github.com/woocommerce/woocommerce-gutenberg-products-block/blob/trunk/phpcs.xml) rule set.
--   `lint:css` runs stylelint over all the scss code in `assets/css`, using the rules in [.stylelintrc.json.](https://github.com/woocommerce/woocommerce-gutenberg-products-block/blob/trunk/.stylelintrc.json)
--   `lint:js` runs eslint over all the JavaScript, using the rules in [.eslintrc.js.](https://github.com/woocommerce/woocommerce-gutenberg-products-block/blob/trunk/.eslintrc.js)
+-   `lint:php` runs phpcs via composer, which uses the [phpcs.xml](../../../phpcs.xml) rule set.
+-   `lint:css` runs stylelint over all the scss code in `assets/css`, using the rules in [.stylelintrc.json.](../../../.stylelintrc.json)
+-   `lint:js` runs eslint over all the JavaScript, using the rules in [.eslintrc.js.](../../../.eslintrc.js)
 
 Note; linters are also ran before commits via Git. If there are any violations, you will not be able to commit your changes until they are fixed, unless you add the `--no-verify` flag to your commit command.
 
@@ -148,7 +148,7 @@ You’ll find a handful of scripts in `package.json` that performs the automated
 -   JS tests: `npm run test`
 -   Run `npm run wp-env` command to setup the development environment in Docker.
 
-To find out more about how to run automated JavaScript tests, check out the documentation on [JavaScript Testing](https://github.com/woocommerce/woocommerce-gutenberg-products-block/blob/trunk/docs/contributors/javascript-testing.md).
+To find out more about how to run automated JavaScript tests, check out the documentation on [JavaScript Testing](../../contributors/contributing/javascript-testing.md).
 
 <!-- FEEDBACK -->