How Bengal transforms source content into final output.
| Stage | What it does | Key modules |
|---|---|---|
| Discovery | Find.mdfiles, parse frontmatter |
bengal/content/discovery/ |
| Rendering | Template selection, Markdown → HTML | bengal/rendering/, bengal/parsing/ |
| Post-Process | Sitemap, RSS, redirects, social cards | bengal/postprocess/ |
| Health | Link validation, content checks | bengal/health/ |
Template Resolution
- Check for explicit
templatein frontmatter - Match by content
type(page →page.html, section →list.html) - Fall back to
single.html
Note
The rendering pipeline is lazy — templates are compiled on first use and cached.
In This Section
Asset Pipeline
How Bengal processes static assets
Content Processing API
What Bengal computes vs what themes display - the content processing contract
Discovery System
How Bengal finds and catalogs content, sections, and assets
Post-Processing
Site-wide operations after rendering - sitemap, RSS, and link validation
Rendering Pipeline
How Bengal transforms Markdown to HTML