Add a hook documentation

[tleon]

Questions	Answers
Branch?	9.x
Description?	Documentation on how to add a new hook

[nicosomb]

Suggested change

	As you can see on this [PR](https://github.com/PrestaShop/PrestaShop/pull/34431/files) Adding a simple Hook::exex() statement is enought to add a new hook. In order for it to be complete, there is a couple more steps to do.
	As you can see on this [PR](https://github.com/PrestaShop/PrestaShop/pull/34431/files), adding a simple Hook::exex() statement is enough to add a new hook. In order for it to be complete, there is a couple more steps to do.

[Hlavtox]

exec

[kpodemski]

I would be more precise here. In the shown example, you don't write about "adding a hook" but adding code that executes the hook in this place. That doesn't mean the hook is fully added to the system if you add this code.

[tleon]

This is the only way I was told how to do it maybe you can enlight me ?

[matks]

I think @kpodemski means that adding the Hook::exec() (part 1) will trigger the hook, but if you dont do the parts 2 and parts 3 it will work only partially

[kpodemski]

Good idea to have it as a separate article. I added my feedback.

[kpodemski]

Suggested change

	Adding a new hook is quite a simple process. It can be done in only tree steps.
	Adding a new hook is a process that can be done in only three steps.

We should refrain from using "simple", "easy", etc., in the documentation. It might not be that simple for some :)

[kpodemski]

I would be more precise here. In the shown example, you don't write about "adding a hook" but adding code that executes the hook in this place. That doesn't mean the hook is fully added to the system if you add this code.

[Hlavtox]

It would be good to add "what happens if X". The hook doesn't have to be in the hooks table to work, it will be added automatically when first module registers on it. However, it can be done only programatically, not by using the backoffice.

[kpodemski]

I added final suggestions @tleon @Hlavtox

[matks]

Good for me

Waiting for @kpodemski last check ;)

fixed

[kpodemski]

thanks @tleon :-)