Plugin Pipeline

What this example is

A dev guide for the SSG plugin pipeline. It shows when each hook fires.

Run it from the repo root:

cargo run --example plugins

The console labels each stage:

1. Cache check — BuildCache::changed_files() skips work when nothing changed
2. Compile — staticdatagen::compile() turns markdown into HTML
3. Plugin pipeline — before_compile, then after_compile, then on_serve
4. Output report — what each plugin made

Plugins shown here

• SeoPlugin — Open Graph + Twitter Card tags
• CanonicalPlugin —
• RobotsPlugin — robots.txt file
• SearchPlugin — client-side search index + UI
• MinifyPlugin — HTML/CSS/JS minify
• LiveReloadPlugin — WebSocket script for dev mode

Order matters. MinifyPlugin runs after SEO and search. It shrinks the final HTML, not a draft.

How this differs from quickstart

quickstart is a starter site you clone and ship. This example is a map of how plugins work. It has no UI polish. Read examples/plugins_example.rs next to the console output.

Where to go next

• Browse the source
• Read the Plugin trait docs for each hook