Feb 22, 2022 · Feb 22, 2022
diff --git a/_data/home-content.yml b/_data/home-content.yml
    localurl: /docs/codefresh-yaml/deployment-environments/
  - title: Hooks
    localurl: /docs/codefresh-yaml/hooks/
  - title: Plugins
    localurl: /docs/codefresh-yaml/steps/#creating-your-own-step
  - title: Examples
    localurl: /docs/yaml-examples/examples/

diff --git a/_docs/codefresh-yaml/hooks.md b/_docs/codefresh-yaml/hooks.md

 For simple commands we suggest you use a small image such as `alpine`, but any Docker image can be used in hooks.

 Also, Hooks can use [steps/plugins](https://steps.codefresh.io) and need to define:

 1. The type field for the step/plugin.
 1. The arguments needed for the step/plugin.

 ## Pipeline hooks

 Codefresh allows you to run a specific step before each pipeline as well as after it has finished.
 1. The `on_finish` segment always executes at the end


 ## Running [steps/plugins](https://steps.codefresh.io) in hooks:

 Hooks can use [steps/plugins](https://steps.codefresh.io). With plugin you have to specify:

 - The type field for the step/plugin.
 - The arguments needed for the step/plugin.

 `codefresh.yml`
 {% highlight yaml %}
 {% raw %}
 version: "1.0"

 hooks: #run slack-notifier hook on build completion
  on_finish:
    steps:
      exec:
        type: slack-notifier
        arguments:
          SLACK_HOOK_URL: '${{SLACK_WEBHOOK_URL}}'
          SLACK_TEXT: '${{SLACK_TEXT}}'

 steps:
  step1:
    title: "Freestyle step"
    type: "freestyle"
    image: alpine
    commands:
      - echo "Codefresh"
    hooks: #run slack-notifier hook on step completion
      on_finish:
        steps:
          exec:
            type: slack-notifier
            arguments:
              SLACK_HOOK_URL: '${{SLACK_WEBHOOK_URL}}'
              SLACK_TEXT: '${{SLACK_TEXT}}'
 {% endraw %}
 {% endhighlight %}

 ## Controlling errors inside pipeline/step hooks

 By default if a step fails within a pipeline, the whole pipeline will stop and be marked as failed. This is also true for `on_elected` segments as well. If they fail, then the whole pipeline will fail (regardless of the position of the segment in a pipeline or step).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -112,6 +112,8 @@
		localurl: /docs/codefresh-yaml/deployment-environments/
		- title: Hooks
		localurl: /docs/codefresh-yaml/hooks/
		- title: Plugins
		localurl: /docs/codefresh-yaml/steps/#creating-your-own-step
		- title: Examples
		localurl: /docs/yaml-examples/examples/

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -14,11 +14,6 @@ Hooks can be a [freestyle step]({{site.baseurl}}/docs/codefresh-yaml/steps/frees

		For simple commands we suggest you use a small image such as `alpine`, but any Docker image can be used in hooks.

		Also, Hooks can use [steps/plugins](https://steps.codefresh.io) and need to define:

		1. The type field for the step/plugin.
		1. The arguments needed for the step/plugin.

		## Pipeline hooks

		Codefresh allows you to run a specific step before each pipeline as well as after it has finished.
Expand DownExpand Up		@@ -262,6 +257,45 @@ The order of events in the example above is the following.
		1. The `on_finish` segment always executes at the end


		## Running [steps/plugins](https://steps.codefresh.io) in hooks:

		Hooks can use [steps/plugins](https://steps.codefresh.io). With plugin you have to specify:

		- The type field for the step/plugin.
		- The arguments needed for the step/plugin.

		`codefresh.yml`
		{% highlight yaml %}
		{% raw %}
		version: "1.0"

		hooks: #run slack-notifier hook on build completion
		on_finish:
		steps:
		exec:
		type: slack-notifier
		arguments:
		SLACK_HOOK_URL: '${{SLACK_WEBHOOK_URL}}'
		SLACK_TEXT: '${{SLACK_TEXT}}'

		steps:
		step1:
		title: "Freestyle step"
		type: "freestyle"
		image: alpine
		commands:
		- echo "Codefresh"
		hooks: #run slack-notifier hook on step completion
		on_finish:
		steps:
		exec:
		type: slack-notifier
		arguments:
		SLACK_HOOK_URL: '${{SLACK_WEBHOOK_URL}}'
		SLACK_TEXT: '${{SLACK_TEXT}}'
		{% endraw %}
		{% endhighlight %}

		## Controlling errors inside pipeline/step hooks

		By default if a step fails within a pipeline, the whole pipeline will stop and be marked as failed. This is also true for `on_elected` segments as well. If they fail, then the whole pipeline will fail (regardless of the position of the segment in a pipeline or step).
Expand Down