Sub-articles are useful when an article has logically related parts
that are too large to be conveniently included in a single article,
yet are not independent enough to merit a separate article.
The site pxquim.pt uses sub-articles to associate multiple photo galleries
with a single article. Each photo gallery goes into a sub-article.
By convention, subparts of articles are articles with "--" in their name.
The part before the "--" should be the slug of the parent article.
For example:
* article.md (the parent article)
* article--one.md (a sub-article of "article.md")
* article--other.md (another sub-article of "article.md")
The article object gets a list of subparts[].
The sub-article object gets the following attributes parent:
* parent -- Reference to the parent article object.
* title -- Changed to start with the parent article plus a comma.
* subtitle -- The original title of the sub-article.
Since PDF Generation is no longer a core feature, these settings are irrelevant. If the `pdf` plugin from pelican-plugins is used, it disregards the `PDF_GENERATOR` setting anyways.
There was an issue with static path watchers, where they were watching wrong paths.
They need to be prefixed with the 'content' path. So, they were not working at all.
It was also possible to overwrite default watchers like 'content', 'settings' and
'theme' by mistake if any of them were present in `STATIC_PATHS`. This is fixed
by adding a prefix to static watchers.
And static watchers were "too static", meaning, they stayed the same even if
`STATIC_PATHS` was changed in the settings during autoreload. Now static watchers
reflect those changes (i.e. new paths are added to watch list, and removed ones
are no longer watched).
This is helpful for mobile testing of Pelican sites by allowing
broadcasting on the local network. Using port 80 requires
running as root on most machines.
- Remove gratuitous Unixisms so that fabfile will work on Windows
- Docstrings for tasks so `fab --list` is more useful.
- Add `gh_pages` task for publishing to GitHub Pages
using [ghp-import](https://github.com/davisp/ghp-import)
Until now, making static files end up in the same output directory as an
article that links to them has been difficult, especially when the article's
output path is generated based on metadata. This changeset introduces the
{attach} link syntax, which works like the {filename} syntax, but also
overrides the static file's output path with the directory of the
linking document.
It also clarifies and expands the documentation on linking to internal content.
