diff --git a/contribute/contribute-pull-requests/add_hook.md b/contribute/contribute-pull-requests/add_hook.md
index 69eca95adc..c0e094cda9 100644
--- a/contribute/contribute-pull-requests/add_hook.md
+++ b/contribute/contribute-pull-requests/add_hook.md
@@ -1,6 +1,49 @@
 ---
-title: Adding a new hook
-weight: 3
-layout: redirect
-redirect: /8/development/components/hook/register-new-hook/
+title: Adding a new Core hook
+weight: 5
 ---
+# Adding a new Core hook
+
+{{% notice note %}}
+If you wish to add a new hook but are not sure how to proceed, you can read the [Adding a new Core hook]({{< relref "../../development/components/hook/register-new-hook/" >}}) guide.
+{{% /notice %}}
+
+Contributing a new hook to PrestaShop is a geat way to extend the software's capabilities, but it requires a few steps to be done properly that we called the "definition of ready".
+
+So, before you start submitting a pull request, make sure you have completed the following steps.
+
+## 1. The `hook.xml` file
+Make sure the hook have a clear description in the `hook.xml` file located in the `install-dev/data/xml/` folder.
+
+This description must be clear and concise, and should help developers understand where this hook is dispatched or what the hook aims to do.
+
+```xml {hl_lines=[4]}
+<hook id="actionMaintenancePageFormSave">
+  <name>actionMaintenancePageFormSave</name>
+  <title>Processing Maintenance page form</title>
+  <description>This hook is called when the Maintenance Page form is processed</description>
+</hook>
+```
+
+## 2. Describe how to test the hook
+
+Don't forget to describe how to test the hook in your pull request. This is important for the reviewer to understand how the new hook works and how to test it.
+
+Providing a small test module in your pull request to validate the use case is a good practice, and helps reviewers to validate your new hook faster. 
+
+{{% notice note %}}
+If you are not sure how to write a test module, you can read the [Tutorial: Creating your first module]({{< relref "../../modules/creation/tutorial" >}}) and the [Using hooks in modules]({{< relref "../../modules/concepts/hooks#using-hooks" >}}) guides.
+{{% /notice %}}
+
+## 3. Trigger UI Tests
+
+When your pull request is ready and submitted, don't forget to trigger the UI auto tests to make sure your new hook doesn't break anything else in PrestaShop.
+
+You can follow the readme file in the [`ga.tests.ui.pr`](https://github.com/prestashop/ga.tests.ui.pr) repository to know how to trigger the UI tests directly on github.
+
+Then, add the url of the UI tests previously launched directly in your pull request description!
+
+## 4. Check the `Hook Contribution` label
+We have a specific label for hook contributions, and this label must be added automatically by our bots.
+
+If for some reason the label is not added, please ping the `@PrestaShop/committers` team in the pull request comments!
diff --git a/development/components/hook/register-new-hook.md b/development/components/hook/register-new-hook.md
index c5a5e7a51f..d95eec9d0f 100644
--- a/development/components/hook/register-new-hook.md
+++ b/development/components/hook/register-new-hook.md
@@ -13,6 +13,10 @@ Although hooks are automatically created the first time they are subscribed to,
 
 Here are the steps you need to follow.
 
+{{% notice note %}}
+If you wish to share your new hook with us, but are not sure how to proceed, you can read the [Contribute: Adding a new Core hook]({{< relref "../../../contribute/contribute-pull-requests/add_hook" >}}) guide.
+{{% /notice %}}
+
 ## 1. Dispatch the new hook
 
 The very first step is just to dispatch the new hook wherever you need it, as explained in [Dispatching a Hook]({{< relref "dispatching-hook" >}}).