Content hook
Content hooks join named phases of content processing: from config resolved through content loaded, post-parsed, post-processed, content graph, to manifest creation and diagnostics.
Processing phases
The content processing pipeline orders hooks as: setup → buildStart → config resolved → public locations resolved → content loaded → Markdown/HTML pipeline → post parsed → post processed → content graph → manifest created → diagnostics → build end.
Hook usage
Only use hooks for phases you genuinely need. Avoid reconstructing later-stage information in earlier hooks; for example, do not rebuild manifest information inside onContentLoaded. Each hook receives progressively more data: onConfigResolved gets config, onContentLoaded gets raw content, onPostParsed gets parsed AST, onPostProcessed gets processed HTML, and onManifestCreated has access to the full manifest.