New Pelican Theme

I’m working on a new theme for my Pelican installation, based off the bootstrap theme for same. The default Bootstrap3 theme is amazing if all you want to do is chuck up a new Pelican site with a template that doesn’t suck shit, but I’ve become rather accustomed to the very specific way that my site works.

Which unfortunately means that this theme breaks on a lot of the little nuances on my blog, so I had to go through and edit a bunch of the templates.

I still have a fair amount of editing to do, but it’s mostly feature-complete with the old theme, so I’m going to deploy it in the next couple of days. I’m just concerned that there will be something else that I will want to change in the base template, which will necessitate a complete re-push to S3 and eat up a bunch of my requests.

I would like to get rid of a few of the requests, even though they’re mostly cached - my site is usually rather zippy (in fact, most of them are) and I don’t really want to bog that down with a heap of JS/CSS requests. I’ve started using timeago for example, but it’s another .JS request - is it worth it?

A possible solution is concatenating all the libraries and CSS I’m using, minimizing and gzipping the resulting file and only calling one, easily cacheable request.

I can also see that I’m going to have to break down and either configure Less or Sass on my build box, because Bootstrap is rather unwieldy if you want to customize it without them (despite the on-the-surface-great “Customize” page).

Horsham, VIC, Australia fwaggle



Filed under:


Horsham, VIC, Australia

Navigation: Older Entry Newer Entry