forked from github/pelican
Add details on how to use Pelican for non-blog static sites
This question comes up on IRC quite frequently.
This commit is contained in:
parent
dd66ad6731
commit
bc26cde436
1 changed files with 13 additions and 1 deletions
14
docs/faq.rst
14
docs/faq.rst
|
|
@ -96,7 +96,7 @@ This metadata can then be accessed in templates such as ``article.html`` via::
|
|||
Last modified: {{ article.modified }}
|
||||
{% endif %}
|
||||
|
||||
If you want to include metadata in templates outside the article context (e.g., ``base.html``), the ``if`` statement should instead be:
|
||||
If you want to include metadata in templates outside the article context (e.g., ``base.html``), the ``if`` statement should instead be::
|
||||
|
||||
{% if article and article.modified %}
|
||||
|
||||
|
|
@ -191,3 +191,15 @@ Older themes that referenced the old setting names may not link properly.
|
|||
In order to rectify this, please update your theme for compatibility by changing
|
||||
the relevant values in your template files. For an example of complete feed
|
||||
headers and usage please check out the ``simple`` theme.
|
||||
|
||||
Is Pelican only suitable for blogs?
|
||||
===================================
|
||||
|
||||
No. Pelican can be easily configured to create and maintain any type of static site.
|
||||
This may require little customization of your theme and Pelican configuration.
|
||||
For example, if you are building a launch site for your product and do not need
|
||||
tags on your site. You can hide tags by removing relevant html code from your theme.
|
||||
You can also disable generation of tags pages::
|
||||
|
||||
TAGS_SAVE_AS = ''
|
||||
TAG_SAVE_AS = ''
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue