sambuc/pelican-plugins
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

teach plugins with dependencies to behave

Browse Source
This commit is contained in:
Deniz Turgut
2013-04-12 18:26:32 -04:00
parent c694cb404d
commit 31ccbde072
86 changed files with 45 additions and 930 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
Contributing.rst
View File

@@ -9,7 +9,9 @@ request. Make sure that your plugin follows the structure below::
my_plugin
├── __init__.py
├── my_plugin.py
├── test_my_plugin.py
└── Readme.rst / Readme.md
``my_plugin.py`` is the actual plugin implementation. Include a brief
explanation of what the plugin does as a module docstring. Leave any further
@@ -17,9 +19,8 @@ explanations and usage details to ``Readme`` file.
``__init__.py`` should contain a single line with ``from .my_plugin import *``.
If you have tests for your plugin, place them in the ``tests`` folder with name
``test_my_plugin.py``. You can use ``test_data`` folder inside, if you need content
or templates in your tests.
Place tests for your plugin in the same folder with name ``test_my_plugin.py``.
You can use ``test_data`` main folder, if you need content or templates in your tests.
**Note:** Plugins in the repository are licensed with *GNU AFFERO GENERAL PUBLIC LICENSE
Version 3*. By submitting a pull request, you accept to release your