core: Start of the big refactor for PieCrust 3.0. * Everything is a `ContentSource`, including assets directories. * Most content sources are subclasses of the base file-system source. * A source is processed by a "pipeline", and there are 2 built-in pipelines, one for assets and one for pages. The asset pipeline is vaguely functional, but the page pipeline is completely broken right now. * Rewrite the baking process as just running appropriate pipelines on each content item. This should allow for better parallelization.

---
title: Code
---

PieCrust can be extended with plugins in order to support additional features
such as new [formatters][1], [processors][2], or [template engines][3] (among
other things).

[Creating a plugin][4] is very easy in itself, but requires making a
`setuptools` package in order to be easily shared with other people.


[1]: {{docurl('content/formatters')}}
[2]: {{docurl('asset-pipeline')}}
[3]: {{docurl('content/templating')}}
[4]: {{apiurl('plugins')}}