<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>openATTIC (Posts about nikola)</title><link>/</link><description></description><atom:link href="https://openattic.org/categories/nikola.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Thu, 22 Aug 2019 20:00:53 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Use Nikola from a developer point of view</title><link>https://openattic.org/posts/use-nikola-from-a-developer-point-of-view/</link><dc:creator>Volker Theile</dc:creator><description>&lt;div&gt;&lt;p&gt;If you want to create or modify a oA blog post, then this short introduction
will show you how to do this without the need to read howto's about Nikola.
You will be able to setup a virtual environment within seconds to avoid
polluting your Python installation and your Git repository on your development
system.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://openattic.org/posts/use-nikola-from-a-developer-point-of-view/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>blog</category><category>git</category><category>nikola</category><guid>https://openattic.org/posts/use-nikola-from-a-developer-point-of-view/</guid><pubDate>Mon, 10 Apr 2017 09:01:35 GMT</pubDate></item><item><title>Linking to Jira issues in Nikola using the issue_role plugin</title><link>https://openattic.org/posts/linking-to-jira-issues-in-nikola/</link><dc:creator>Lenz Grimmer</dc:creator><description>&lt;div&gt;&lt;p&gt;Our release announcements (like the &lt;a class="reference external" href="https://openattic.org/posts/openattic-208-beta-has-been-released/"&gt;one for openATTIC 2.0.8&lt;/a&gt;) usually contain a lot of references
to issues on &lt;a class="reference external" href="http://tracker.openattic.org"&gt;our issue tracker&lt;/a&gt; in the form
of issue ids like &lt;cite&gt;OP-XXX&lt;/cite&gt;.&lt;/p&gt;
&lt;p&gt;However, &lt;a class="reference external" href="https://getnikola.com"&gt;Nikola&lt;/a&gt;, the static site generator that
powers this blog, did not provide an easy method to convert these issue IDs
into URLs pointing to our issue tracker automatically. Converting each issue
ID into an URL manually using the existing reStructuredText link syntax felt
too tedious.&lt;/p&gt;
&lt;p&gt;But fortunately Nikola provides a plugin system, that allows you to &lt;a class="reference external" href="https://getnikola.com/extending.html"&gt;extend
its functionality&lt;/a&gt; quite easily!&lt;/p&gt;
&lt;p&gt;After some discussion with the Nikola developers on the #nikola IRC channel on
Freenode, we came to the conclusion that the best approach would be to extend
the reStructuredText markup language with an additional &lt;a class="reference external" href="http://docutils.sourceforge.net/docs/ref/rst/roles.html"&gt;explicit role&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;And that's what we did - our &lt;a class="reference external" href="https://github.com/getnikola/plugins/pull/135"&gt;pull request&lt;/a&gt; was accepted and the new
plugin &lt;a class="reference external" href="https://plugins.getnikola.com/#issue_role"&gt;issue_role&lt;/a&gt; is now
available from the Nikola plugin repository.&lt;/p&gt;
&lt;p&gt;The installation and configuration is pretty simple - simply run &lt;tt class="docutils literal"&gt;nikola
plugin &lt;span class="pre"&gt;--install&lt;/span&gt; issue_role&lt;/tt&gt; and configure &lt;tt class="docutils literal"&gt;conf.py&lt;/tt&gt; as described, by
setting &lt;tt class="docutils literal"&gt;ISSUE_URL&lt;/tt&gt; in the &lt;tt class="docutils literal"&gt;GLOBAL_CONTEXT&lt;/tt&gt;. In our case, we added the
following to the configuration file:&lt;/p&gt;
&lt;pre class="literal-block"&gt;
GLOBAL_CONTEXT['ISSUE_URL'] = "http://tracker.openattic.org/browse/{issue}"
&lt;/pre&gt;
&lt;p&gt;In our blog posts, we now enter issues as follows, and Nikola takes care of
converting them into URLs:&lt;/p&gt;
&lt;pre class="literal-block"&gt;
Created plugin that automatically converts Jira Task IDs to URLs
(:issue:`OP-741`)
&lt;/pre&gt;
&lt;p&gt;Running &lt;cite&gt;nikola build&lt;/cite&gt; converts this into the following HTML:&lt;/p&gt;
&lt;blockquote&gt;
Created plugin that automatically converts Jira Task IDs to URLs
(&lt;a class="reference external" href="https://tracker.openattic.org/browse/OP-741"&gt;OP-741&lt;/a&gt;)&lt;/blockquote&gt;
&lt;p&gt;We hope you find this useful!&lt;/p&gt;&lt;/div&gt;</description><category>collaboration</category><category>contributing</category><category>nikola</category><category>opensource</category><category>python</category><guid>https://openattic.org/posts/linking-to-jira-issues-in-nikola/</guid><pubDate>Thu, 03 Mar 2016 16:17:15 GMT</pubDate></item></channel></rss>