Document posthook requirements and behavior (#21)

Reviewed-on: https://git.mills.io/prologic/zs/pulls/21
Reviewed-by: James Mills <james@mills.io>
Co-authored-by: jedahan <jedahan@noreply@mills.io>
Co-committed-by: jedahan <jedahan@noreply@mills.io>
This commit is contained in:
jedahan 2024-06-10 05:13:46 +00:00 committed by James Mills
parent 92b387d910
commit d7c5c48621

View File

@ -220,12 +220,13 @@ Looking for more plugins? Check out the [contrib/plugins](https://git.mills.io/p
## Hooks ## Hooks
There are two special plugin names that are executed every time the build There are two special plugin names that are executed every time the build happens:
happens:
- `prehook` -- executed before the build - `prehook` -- executed before the build
- `posthook` -- executed after the build - `posthook` -- executed after the build
You must have `prehook` for `posthook` to work correctly, and `posthook` will only run if a file has been modified.
You can use these to customize the build before and after. For example you can use the `posthook` to minify CSS or Javascript files. You can use these to customize the build before and after. For example you can use the `posthook` to minify CSS or Javascript files.
`.zs/posthook`: `.zs/posthook`: