polo is a static blog generator created with Go. It's compatible with your current Jekyll and Pelican markdowns, so your migration should be straightforward.

I'm happily using it on my blog: http://agonzalezro.github.io and you can use it in yours!

Yes, I know that there a lot of them out there but I just want mine to learn a little bit of Go coding.

Here are some features:

• Jekyll and Pelican compatible.
• Can watch files for changes and in that case regenerate the site.
• Pretty quick! But new versions will be faster.
• Deploy it to gh-pages or create your own blog on github.
• You can easily auto deploy it: [example for CircleCI](http://agonzalezro.github.io/how-to-automagically-generate-your-polo-blo g-with-circleci.html).
• It supports templating, check my personal blog source for an example.

Find your version here: https://github.com/agonzalezro/polo/releases

If you want to build it yourself, I am using gb:

$ gb build

If you call the binary without any argument you will get the help:

$ polo
Usage:
  polo [OPTIONS] sourcedir outputdir

Application Options:
  -d, --daemon  start a simple HTTP server watching for markdown changes.
  -c, --config= the settings file. (config.json)
  -p, --port=   port where to run the server. (8080)

Help Options:
  -h, --help    Show this help message

The basic usage mode is:

$ polo sourcedir outputdir

If you want a server that watches for you changes, meaning that if you change something in sourcedir the site will be regenerated:

$ polo -d sourcedir outputdir
...
2015/06/23 23:36:57 Static server running on http://localhost:8080

There is an example project here, you can use it as sourcedir.

You can specify your configuration file with the option -c/--config, or just use the default value: config.json.

An example configuration can be found on the file config.json: https://github.com/agonzalezro/polo/blob/master/example/config.json

This is what you can configure:

• author: if it's not override with the Metadata it's the name that is going to be shown on the articles.
• title: title of the blog, for the <title> element and the header.
• url: sometimes the full url is needed.
• show{Archive,Categories,Tags}: if it's true the pages are going to be created and the links are going to be added.
• paginationSize: set it to -1 if you want to show all the posts.
• favicon: the favicon path if you have one.

• disqusSitename: if you want comments on your blog.
• googleAnalyticsId: the Google Analytics ID.
• shareThisPublisher: the ShareThis publisher ID. If provided, there will be some social buttons on the article view.

Whatever thing that is supported by blackfriday library is supported here. The only difference is that I am adding some metadata to the files.

This metadata is using exactly the same format than the one used on Pelican or Jekyll, but we don't support exactly the same keys. If you thing that some of the keys that they support and we don't are needed, please, create an issue or send a pull request.

Supported tags:

• title: if it's not on the metadata info, the first line is going to be used to create it.
• date: format YYYY-MM-DD hh:mm
• tags: comma separated.
• slug: if it is not defined the first line is going to be slugified.
• status: if it's draft the page is not going to be rendered.
• summary: an introductory paragraph. It will be empty if the metadata tag is not defined.
• author: this will override the default author in the config file.

This is one auto explainable example for Pelican:

Title: My super title
Date: 2010-12-03 10:20
Tags: thats, awesome
Slug: my-super-post
Author: Federico

And here is just the content.

In this case we are overriding the values of your site configuration for the title, slug & author.

If you prefer the Jekyll format, or you are migrating a Jekyll page:

---
title: My super title
date: 2010-12-03 10:20
tags: thats, awesome
slug: my-super-post
author: Federico
---

And here is just the content.

The keys are case insensitive in both cases.

This functionality is in a kinda early stage. I think, that we will need to split the templates in much more files, and this way we will be able to override them quite easily, but that will require some work (PRs welcomed! :)

You have a default theme on templates/. If you just installed polo this theme is going to be part of the binary but it can be override.

In case that you want to override the theme, you don't need to provide ALL the files. Just providing the ones that you are overriding is more than enough.

For example, imaging that you want to override the header to use another bootstrap theme:

1. Wherever you want (but it needs to be the same place where you run polo from) you create the folder templates/base.
2. Then you edit templates/base/header.html, adding the following content:

{{define "header"}}
  <link rel="stylesheet" href="/static/css/bootstrap.min.css">
  <link
    href="http://netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap-glyphicons.css"
    rel="stylesheet">
{{end}}

3. Now you run polo from the folder that owns templates/ and
4. PROFIT!

If you want to do changes on the default theme, you need to remember that you MUST recreate the binary data, you should do it this way:

$ cd src
$ go-bindata -o src/templates/bindata.go -pkg=templates -ignore=bindata.go src/templates/...
$ cd -

It's quite important that you cd to src before doing it, if not the paths will not match.

There is a issue open to automate this.

You can use your favourite CI/CD platform to generate the sites. I wrote a blog post about how to do it with CircleCI here: http://agonzalezro.github.io/how-to-automagically-generate-your-polo-blog-with-circleci.html