What would be a python alternative to a system like nanoc?

1.9k Views Asked by At

Is there a python publishing system (have no idea whether this is an appropriate name for such a thing, but they're calling it that way) similar to nanoc? Generally, a thing which will convert a lot of markup/asciidoc files to HTML in an orderly fashion?

I know of python-markdown, but one by one page with no support for outside .css pages is not what I'm looking for?

So, is there something python based of more or less this quality?

5

There are 5 best solutions below

0
On

Some website are built using Sphinx which was for documentation purposes but could be extended to a static website easily. (e.g. http://redhotchilipython.com/)

0
On

I know what nanoc is but I never use it, so I can't do comparison. These are some Python generators you can consider:

  • Blogofile: a static website compiler and blog engine (there is #blogofile irc channel on freenode)
  • Chisel: a simple Python static blog generation utility (last update March 2009)
  • Hyde: static website generator powered by Python & Django (version 0.5, which is in development, lacks features if compared to 0.4 and is not well documented, but it should be easier to use).
  • Pelican: a simple weblog generator (there is #pelican irc channel on freenode)
  • poole: an easy to use Markdown driven static website generator (I used it, does its job well)
  • PyGreen: a small framework based on Bottle and Mako to create web sites that can easily be exported as static web sites

From what I can say, at the moment static site generators in Ruby are more feature complete and mature, though you should be able to find a solution right for you in Python, too.

1
On

Not sure how this compares to nanoc:

0
On

The closest equivalent seems to be StrangeCase. The author even mentions the similarity:

I just read about nanoc, and realized that it is the Ruby equivalent to StrangeCase. I commend them! I had considered porting StrangeCase to Ruby (and maybe I will some day, just for kicks), but for now, I would say to Rubyists: use nanoc.

1
On