invoked after all the generators are executed and just before pelican exits
usefull for custom post processing actions, such as:
- minifying js/css assets.
- notify/ping search engines with an updated sitemap.

generator_init

generator

invoked in the Generator.__init__

article_generate_context

article_generator, metadata

article_generate_preread

article_generator

invoked before a article is read in ArticlesGenerator.generate_context;
use if code needs to do something before every article is parsed

article_generator_init

article_generator

invoked in the ArticlesGenerator.__init__

article_generator_finalized

article_generator

invoked at the end of ArticlesGenerator.generate_context

get_generators

generators

invoked in Pelican.get_generator_classes,
can return a Generator, or several
generator in a tuple or in a list.

pages_generate_context

pages_generator, metadata

pages_generator_init

pages_generator

invoked in the PagesGenerator.__init__

pages_generator_finalized

pages_generator

invoked at the end of PagesGenerator.generate_context

content_object_init

content_object

invoked at the end of Content.__init__ (see note below)

The list is currently small, so don’t hesitate to add signals and make a pull
request if you need them!

Note

The signal content_object_init can send a different type of object as
the argument. If you want to register only one type of object then you will
need to specify the sender when you are connecting to the signal.