Site overhaul to get rid of Jekyll

…and get things working again!

If you know html+css, why use a framework? Turns out, a few reasons.
other
Author

Lara Thompson

Published

September 7, 2020

I had great intentions last summer to add more regular posts: more paper summaries, worked through ideas, etc. But [excuses]. Fast forward to now, I have notes to put up but have since switched entirely from a mac to Ubuntu, discovered a far better app to edit markdown with math, Typora (not freeware but so good I’ll pay once it’s out of beta [looking back in 2024: I did!]), and I couldn’t get the new post to render properly (some strange auto-scaling was happening).

After I wasted over nearly two days debugging Jekyll (cause stuff happened outside of my template files), I gave up. In a couple of hours, I was rid of Jekyll, rid of frameworks and down to raw html+css. Gotta say, html5 once you give in to it, is damn nice compared to circa 2004 wed development (my work is still live [still live in 2024], don’t look).

A few things to share to anyone who’s thinking of doing the same:

My favourite find to convert a picture of myself that didn’t feel so […]: cartoonize project/paper + demo. It’s another style transfer GAN, predominantly trained on scenery images are collected from Shinkai Makoto, Miyazaki Hayao and Hosoda Mamoru films. The cityscapes are the best, especially those with clouds. I used a picture from the approach on Mount Rainier: love what it did to the rocks, grass, trees and background hills!

…and bringing Jekyll back

I considered getting the feed working manually, adding posts manually hereon, updating posts.html manually. But finally, I accepted the challenge of just getting Jekyll working after all. It was too much like installing a GPU for ML only — fighting against the grain — except in this case, why bother?

Main takeaways:

My Jekyll configuration is bare bones. By all means, copy as much as you like!