<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Pelican Plugins on Chris Ramsay</title><link>https://chrisramsay.co.uk/series/pelican-plugins/</link><description>Recent content in Pelican Plugins on Chris Ramsay</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sun, 12 Jan 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://chrisramsay.co.uk/series/pelican-plugins/index.xml" rel="self" type="application/rss+xml"/><item><title>Show Source Plugin Update</title><link>https://chrisramsay.co.uk/posts/2016/12/show-source-plugin-update/</link><pubDate>Sat, 17 Dec 2016 00:00:00 +0000</pubDate><guid>https://chrisramsay.co.uk/posts/2016/12/show-source-plugin-update/</guid><description>&lt;h2 id="latest-news"&gt;Latest News&lt;/h2&gt;
&lt;p&gt;I received some good news this week: my &lt;a href="https://github.com/chrisramsay/pelican-plugins/tree/feature/show_source/show_source"&gt;Show Source&lt;/a&gt; plugin, the one inspired by &lt;a href="http://www.sphinx-doc.org/"&gt;Sphinx&lt;/a&gt;, has had its pull request accepted into the &lt;a href="https://github.com/getpelican/pelican-plugins"&gt;getpelican/pelican-plugins repo&lt;/a&gt;. This means that the plugin becomes a part of the standard &lt;a href="https://github.com/getpelican/pelican"&gt;Pelican&lt;/a&gt; plugin canon.&lt;/p&gt;
&lt;p&gt;My next task will be to make a small addition, and hence pull request, to the developers of the theme I use with this site (&lt;a href="https://github.com/getpelican/pelican-themes/tree/master/pelican-bootstrap3"&gt;pelican-bootstrap3&lt;/a&gt;) to accomodate a couple of small template changes to support &lt;a href="https://github.com/chrisramsay/pelican-plugins/tree/feature/show_source/show_source"&gt;Show Source&lt;/a&gt; automatically.&lt;/p&gt;
&lt;p&gt;The officially accepted version of show source &lt;a href="https://github.com/getpelican/pelican-plugins/tree/master/show_source"&gt;is available now right here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;</description></item><item><title>The Show Source Pelican Plugin</title><link>https://chrisramsay.co.uk/posts/2016/11/the-show-source-pelican-plugin/</link><pubDate>Sun, 06 Nov 2016 00:00:00 +0000</pubDate><guid>https://chrisramsay.co.uk/posts/2016/11/the-show-source-pelican-plugin/</guid><description>&lt;h2 id="rationale"&gt;Rationale&lt;/h2&gt;
&lt;p&gt;I have always been a fan of the &lt;a href="http://www.sphinx-doc.org/"&gt;Sphinx&lt;/a&gt; Python documentation generator and it has, I think, a nice feature where you can check out the raw source of a generated piece of documentation - a &lt;em&gt;Show Source&lt;/em&gt; link. I decided that developing a &lt;a href="https://github.com/getpelican/pelican-plugins"&gt;Pelican plugin&lt;/a&gt; to imitate that feature would be a great way of getting a little deeper into the Pelican code itself.&lt;/p&gt;
&lt;p&gt;This second post of the series explains the use of the Show Source plugin that I developed from the learning in the &lt;a href="https://chrisramsay.co.uk/posts/2016/11/basic-notes-on-pelican-plugin-architecture/"&gt;previous post&lt;/a&gt;. The following article has been, in some part, reproduced in the &lt;code&gt;ReadMe.rst&lt;/code&gt; file included as part of the plugin.&lt;/p&gt;</description></item><item><title>Basic Notes on Pelican Plugin Architecture</title><link>https://chrisramsay.co.uk/posts/2016/11/basic-notes-on-pelican-plugin-architecture/</link><pubDate>Fri, 04 Nov 2016 00:00:00 +0000</pubDate><guid>https://chrisramsay.co.uk/posts/2016/11/basic-notes-on-pelican-plugin-architecture/</guid><description>&lt;h2 id="rationale"&gt;Rationale&lt;/h2&gt;
&lt;p&gt;I have always been a fan of the &lt;a href="http://www.sphinx-doc.org/"&gt;Sphinx&lt;/a&gt; Python documentation generator and it has, I think, a nice feature where you can check out the raw source of a generated piece of documentation - a &lt;em&gt;Show Source&lt;/em&gt; link. I decided that developing a &lt;a href="https://github.com/getpelican/pelican-plugins"&gt;Pelican plugin&lt;/a&gt; to imitate that feature would be a great way of getting a little deeper into the Pelican code itself.&lt;/p&gt;
&lt;p&gt;This first post explores the Pelican plugin architecture and the basics of building a plugin.&lt;/p&gt;</description></item></channel></rss>