[[PreProcessorDirective]] output is sanitised, which may limit what your
plugin can do. Also, the rest of the page content is not in html format at
preprocessor time. Text output by a preprocessor directive will be passed
-through markdown along with the rest of the page.
+through markdown (or whatever engine is used to htmlize the page) along
+with the rest of the page.
# Other types of hooks
make arbitrary changes. The function is passed named parameters `page` and
`content` and should return the filtered content.
-## sanitize
+## htmlize
- IkiWiki::hook(type => "filter", id => "foo", call => \&sanitize);
+ IkiWiki::hook(type => "htmlize", id => "ext", call => \&filter);
-Use this to implement html sanitization or anything else that needs to
-modify the content of a page after it has been fully converted to html.
-The function is passed the page content and should return the sanitized
-content.
+Runs on the raw source of a page and turns it into html. The id parameter
+specifies the filename extension that a file must have to be htmlized using
+this plugin. This is how you can add support for new and exciting markup
+languages to ikiwiki.
## pagetemplate
common thing to do is probably to call $template->param() to add a new
custom parameter to the template.
+## sanitize
+
+ IkiWiki::hook(type => "sanitize", id => "foo", call => \&sanitize);
+
+Use this to implement html sanitization or anything else that needs to
+modify the content of a page after it has been fully converted to html.
+The function is passed the page content and should return the sanitized
+content.
+
## delete
IkiWiki::hook(type => "delete", id => "foo", call => \&dele);