Javier Gonel e00e7d35c9 The asset_url needs to use also theme_static_dir
Sorry for this mistake, I was using harcoded paths in my template.

If the destination changes in the output folder (`THEME_STATIC_DIR`) also the URL used for the assets should change.
2013-11-14 18:41:33 +02:00
2013-04-12 17:48:52 -04:00
2013-08-08 17:06:50 -07:00
2013-09-27 16:28:46 +08:00
2013-06-23 21:24:20 -07:00
2013-05-03 07:22:31 -07:00
2013-09-29 22:49:49 +08:00
2013-05-17 11:33:16 +10:00

Pelican Plugins
###############

Beginning with version 3.0, Pelican supports plugins. Plugins are a way to add
features to Pelican without having to directly modify the Pelican core. Starting
with 3.2, all plugins (including the ones previously in the core) are 
moved here, so this is the central place for all plugins. 

How to use plugins
==================

Easiest way to install and use these plugins is cloning this repo::

    git clone https://github.com/getpelican/pelican-plugins

and activating the ones you want in your settings file::

    PLUGIN_PATH = 'path/to/pelican-plugins'
    PLUGINS = ['assets', 'sitemap', 'gravatar']

``PLUGIN_PATH`` can be a path relative to your settings file or an absolute path.

Alternatively, if plugins are in an importable path, you can omit ``PLUGIN_PATH``
and list them::

    PLUGINS = ['assets', 'sitemap', 'gravatar']

or you can ``import`` the plugin directly and give that::

    import my_plugin
    PLUGINS = [my_plugin, 'assets']

Please refer to the ``Readme`` file in a plugin's folder for detailed information about 
that plugin.

Contributing a plugin
=====================

Please refer to the `Contributing`_ file.

.. _Contributing: Contributing.rst
Languages
Python 81.9%
HTML 10.5%
CSS 6.4%
Smarty 1.2%