From 65f0f31b7baab9794567075c65c5d62e12d94011 Mon Sep 17 00:00:00 2001 From: derwinlu Date: Sat, 17 Oct 2015 16:49:11 +0200 Subject: [PATCH] Add FAQ about static files parsed as content Since #1509 got merged this pops up again and again (latest #1845). This PR addresses the issue by adding a FAQ about it that explains why it is necessary to add `*_EXCLUDES`. --- docs/faq.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/faq.rst b/docs/faq.rst index 8ecdcb55..f75e4e6c 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -264,3 +264,15 @@ to iterate over ``pages`` instead of ``PAGES``. Just replace:: with something like:: {% for pg in pages %} + +How can I stop Pelican from trying to parse my static files as content? +======================================================================= + +Pelican's article and page generators run before it's static generator. That +means if you use a setup similar to the default configuration, where a static +source directory is defined inside a ``*_PATHS`` setting, all files that have a +valid content file ending (``.html``, ``.rst``, ``.md``, ...) will be treated as +articles or pages before they get treated as static files. + +To circumvent this issue either use the appropriate ``*_EXCLUDES`` setting or +disable the offending reader via ``READERS`` if you don't need it.