BM v4.0.0 is Released

Posted on 30 Jan 2017 by Matt Traudt

permalink

Yesterday I released yet another new major version of BM! The changelog has a summary of changes. As before, please report any issues at the issue tracker.

Important

There are two big changes that should be noted.

Your configuration file needs to move. It used to be in include/bm.conf, but that directory has been emptied out. Your configuration file now belongs in your posts directory, posts/bm.conf. BM comes with a script in tools/ to help you transition from v3 to v4, but really it's as simple as moving your configuration file. After you've moved it, you may delete the include directory. It should be empty.

The other major change is themes! Themes allow you to quickly change the look of your website. They can easily be shared as all the important bits and pieces are in one directory per theme. Here's the "terminal" theme that I created and will officially support in addition to the default theme.

terminal theme

For information how how to set your theme, see here. For information about creating your own theme, see here. It's very easy, especially if you start out copy/pasting an already good one.

Other new features

Page signing was added. Now, given a gpg fingerprint, BM will automatically cryptographically sign all output files (even the CSS!) and leave a note in the footer saying so in officially supported themes.

signature note

(Ignore the version number, this was added in v4.0.0. I should probably decide something about "in development" versioning...)

If page signing is enabled, then /pubkey.gpg will also be automatically generated with the public key used for signing.

Licensing your content has been made easier. A new config option, LICENSE_TEXT, was added. The contents of it will be placed verbatim in the footer of officially supported themes. I have set my LICENSE_TEXT to the following string in order to get the Creative Commons image link you see on my blog.

<a href='https://creativecommons.org/licenses/by-sa/4.0/'><img
src='https://i.creativecommons.org/l/by-sa/4.0/80x15.png'/></a>

The above produces

Such complicated license text is obviously not necessary.

Future

Some of the next things I want to work on include

To watch my progress or to suggest things, see the issue tracker.

If you're using BM, I would love to hear about it! Please let me know somehow.