Tag: pelican

Getting Lost in Rabbit Holes

Rabbit Holes

In retrospect, I should have known there was going to be a problem. It seemed like such a simple thing, after all. I just wanted to switch to YAML to define my post front matter. YAML, which stands for YAML Ain’t Markup Language, has a very simple job: it provides a structure for keyed data (or metadata) that is human readable and portable1. Even more importantly, my markdown editor (Typora) has this neat little feature that lets me set up a YAML front matter section right in the post. It is a nice little bonus in what is, already, a gorgeous markdown editor.

The Python Markdown processor that Pelican uses doesn’t require YAML, but I prefer it for cross-compatibility with other platforms and processors (pandoc, Jekyll, etc). Luckily, there was a YAML plugin already designed for Pelican, so I decided to check it out. I won’t deny that I was a bit dubious about the plugin. It has been quite a while since it was updated. Nevertheless, I added it to my config and set it to build.

And crashed.

I expect this from time to time. One of the real joys of working with open …

More

Blog Engine Revamp - Full Cirle”

Ghost 2.0 was just released. In a lot of ways, it is an excellent release. The entire engine is elegant and easy to use. I can absolutely see why so many people love it.

Unfortunately, I didn’t love it as much.

Here are the issues that I saw. I want to note here that these are issues that are tied, very clearly, to my corner case. I think that the Ghost developers are making a product that best suits a large portion of their user-base. They should. I am just not a part of that base.

Editor

The new editor is gorgeous. The dynamic cards absolutely add excellent functionality. They also make the editor far busier and much more clumsy.

Ghost claims that:

Ghost’s editor is still about doing one thing, really well: Writing.

I don’t think it is. I think the editor is more about providing formatting tools and rich content than it is about writing. From my own experience, the writing process was certainly degraded by the cards. The movement away from a simple Markdown editor (or at least leaving it as an option) definitely figured heavily in my decision.

Note, too, that in …

More

© Geoffrey Gimse. Built using Pelican. Except where noted, all photos are my own. Other images used on this site are in the Public Domain and available from Openclipart, or have been purchased for use via The Noun Project.