<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sphinx on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/sphinx/</link>
    <description>Recent content in Sphinx on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 25 Aug 2012 18:15:00 +0000</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/sphinx/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automatic Github Pages generation from Sphinx documentation</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2012/automatic-github-pages-generation-from/</link>
      <pubDate>Sat, 25 Aug 2012 18:15:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2012/automatic-github-pages-generation-from/</guid>
      <description>Sphinx is a very common documentation tool which gobbles up ReStructuredText and other free-form markup formats and outputs great HTML, PDF and other formats. It is meant for reference manuals and API documentation due to its good integration with source code (especially Python). The libuv book is written using Sphinx so that it looks so good with minimum effort.&#xA;Sphinx uses make to generate the HTML, which is great. The only problem is that deploying this to Github Pages requires multiple commands to switch branches to gh-pages, pull in the source text, then cleanup the working copy and switch back to master.</description>
    </item>
  </channel>
</rss>
