Moving to Hugo and AsciiDoc for the Site

I use AsciiDoc all the time. At work, at home. I have written and published books with AsciiDoc. I like how the text lasts forever. I’ve lived long enough to see various rich text editors change over the years and stop backwards supporting their original formats. I do not want this for my own work.

I thought it would be nice if I could develop my site content in this text format rather than with WYSIWYG apps like Word or Pages or the site generators that mimic the rich text input methods.

First I tried Pelican since I am familiar with Python. But Pelican requires some jumping through hoops for AsciiDoc that I did not feel like spending my vacation time working on.

I had heard about Hugo. So I installed it and started configuring the site with a theme for the look and feel, so I could begin to focus just on the content and less on the format.

I got one theme working, but I did not like the way it was only blog-oriented. So I started looking into the Hugo Docs to determine how to add the pages I wanted for family history content.

I’m not done yet, because with family in town, I can’t spend the time right now digging into this and testing hypotheses.

I will come back to it in early January.

comments powered by Disqus