From d976fd34af269ae425bf3cb1d2c32f878d1b127d Mon Sep 17 00:00:00 2001 From: Mitchell Date: Fri, 19 Feb 2016 10:48:15 +0530 Subject: [PATCH] Move plugins. Refs #1488 --- docs/content.rst | 6 +++--- docs/faq.rst | 2 +- docs/index.rst | 2 +- docs/plugins.rst | 10 ++++++---- 4 files changed, 11 insertions(+), 9 deletions(-) diff --git a/docs/content.rst b/docs/content.rst index 0fa89921..bfbc4db3 100644 --- a/docs/content.rst +++ b/docs/content.rst @@ -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 diff --git a/docs/faq.rst b/docs/faq.rst index f75e4e6c..60d21612 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -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 -`_. +`_. See the :ref:`plugins` documentation further information about the Pelican plugin system. diff --git a/docs/index.rst b/docs/index.rst index ccfb9982..fce118e0 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -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 diff --git a/docs/plugins.rst b/docs/plugins.rst index 6a850100..fcb77ff3 100644 --- a/docs/plugins.rst +++ b/docs/plugins.rst @@ -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 =====================