github/pelican
1
0
Fork 1
mirror of https://github.com/getpelican/pelican.git synced 2025-10-15 20:28:56 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Move plugins. Refs #1488

Browse source
This commit is contained in:
Mitchell 2016-02-19 10:48:15 +05:30
commit d976fd34af
4 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/content.rst
View file

@ -69,7 +69,7 @@ Metadata syntax for Markdown posts should follow this pattern::
This is the content of my super blog post.
Readers for additional formats (such as AsciiDoc_) are available via plugins.
Refer to `pelican-plugins`_ repository for those.
Refer to `getpelican-plugins`_ organization for those.
Pelican can also process HTML files ending in ``.html`` and ``.htm``. Pelican
interprets the HTML in a very straightforward manner, reading metadata from
@ -526,7 +526,7 @@ metadata to include ``Status: published``.
.. _W3C ISO 8601: http://www.w3.org/TR/NOTE-datetime
.. _AsciiDoc: http://www.methods.co.nz/asciidoc/
.. _pelican-plugins: http://github.com/getpelican/pelican-plugins
.. _getpelican-plugins: http://github.com/getpelican-plugins
.. _Markdown Extensions: http://pythonhosted.org/Markdown/extensions/
.. _CodeHilite extension: http://pythonhosted.org/Markdown/extensions/code_hilite.html#syntax
.. _i18n_subsites plugin: http://github.com/getpelican/pelican-plugins/tree/master/i18n_subsites
.. _i18n_subsites plugin: http://github.com/getpelican-plugins/i18n_subsites

2
docs/faq.rst
View file

@ -247,7 +247,7 @@ My tag-cloud is missing/broken since I upgraded Pelican
In an ongoing effort to steamline Pelican, `tag_cloud` generation has been
moved out of the pelican core and into a separate `plugin
<https://github.com/getpelican/pelican-plugins/tree/master/tag_cloud>`_.
<https://github.com/getpelican-plugins/tag_cloud>`_.
See the :ref:`plugins` documentation further information about the
Pelican plugin system.

2
docs/index.rst
View file

@ -82,4 +82,4 @@ Documentation
.. _Jinja2: http://jinja.pocoo.org/
.. _`Pelican documentation`: http://docs.getpelican.com/latest/
.. _`Pelican's internals`: http://docs.getpelican.com/en/latest/internals.html
.. _`Pelican plugins`: https://github.com/getpelican/pelican-plugins
.. _`Pelican plugins`: https://github.com/getpelican-plugins

10
docs/plugins.rst
View file

@ -38,14 +38,16 @@ the ``PLUGIN_PATHS`` list can be absolute or relative to the settings file::
Where to find plugins
=====================
We maintain a separate repository of plugins for people to share and use.
Please visit the `pelican-plugins`_ repository for a list of available plugins.
We maintain a separate GitHub organization for plugins so contributors have
a highly visible location and an easier way to collaborate with fellow users.
Please visit the `getpelican-plugins`_ organization to access these plugins.
.. _pelican-plugins: https://github.com/getpelican/pelican-plugins
.. _pelican-plugins: https://github.com/getpelican-plugins
Please note that while we do our best to review and maintain these plugins,
they are submitted by the Pelican community and thus may have varying levels of
support and interoperability.
support and interoperability. Also note that some developers maintain their
own plugin repositories outside of this location.
How to create plugins
=====================