It also assumes you've set up Pelican with
something like it. In particular it assumes:
- The existence of
Makefilein some ancestor directory.
- The first component of the path (e.g.
content) after that ancestor is irrelevant.
- If the next component is
pages, that indicates a static page rather than a dated post.
It also enforces some parts of my preferred Pelican configuration:
- Categories are never provided (you can have one if you want, but the default interactive commands don't provide one).
- Tags are always provided.
- Slugs are explicit, and include nested subdirectories.
C-x p n- Insert a post or page header
C-x p p- Remove draft status from a post (i.e. publish it)
C-x p t- Update the date field in a post/page header
C-x p h- Generate HTML output for a site (equivalent to
C-x p u- Upload a site using rsync (equivalent to
If the commands which invoke
make can find the Makefile but can't
exec-path may not be set right. Try out
This code is released into the public domain via the CC0 Public Domain Dedication.