我有一个现有的网站,其结构与以下类似:
.
|-blog
|-articles
| |-foo.html
|-images
|-references
当我运行pelican时,它获取foo.html并将其存储在输出目录的根目录中。有没有办法告诉pelican保留articles目录,以便在那里创建foo.html?我在官方文件中找不到答案。
*更新*
使用我正在使用的pelican配置文件进行更新:
#!/usr/bin/env python
# -*- coding: utf-8 -*- #
from __future__ import unicode_literals
AUTHOR = u'Donny'
SITENAME = u"Happy Valley"
SITEURL = ''
SHOW_FULL_ARTICLE = True
THEME = 'themes/pelican-clean-blog'
PATH = 'site_content'
TIMEZONE = 'US/Eastern'
DEFAULT_LANG = u'en'
PLUGINS = ['pelican_alias']
STATIC_PATHS = ['presentations']
site_content目录包含上面列出的树。我想做的是让pelican从源代码中获取articles/foo.html,并将其作为/articles/foo.html显示在输出目录中。为了保持目录的干净,我希望它创建一个实际的articles目录,并将生成的文件放在那里。
这对我有效(如下):
content/
├── p001
│ └── myArticle001.md
│ └── img001
│ └── myPic1.png
│ └── myPic2.png
├── p002
│ └── myArticle002.md
│ └── img002
│ └── myPic1.png
│ └── myPic2.png
在pelicanconfig.py
集合中:
PATH = 'content'
STATIC_PATHS = ['p001','p002']
ARTICLE_PATHS = STATIC_PATHS
运行Pelican后,我得到:
output/
├── p001
│ └── img001
│ └── myPic1.png
│ └── myPic2.png
├── p002
│ └── img002
│ └── myPic1.png
│ └── myPic2.png
├── posts
│ └── myArticle001.md
│ └── myArticle002.md