Welcome to Jeremy Friesen’s personal blog; I often write about games but don’t limit posts to games. Please feel free to contact me. You can subscribe to my site’s Atom RSS feed or JSON feed.

I have published and sold some game materials. I release some content on this site as Open Game License or OGL.

I do my best to tag posts and group some posts into series. You may be interested in my reviews or interviews. I have created a Metadata page where you can see different views of the site.

I also committed, for the time being, to host S John Ross’s Medieval Demographics Made Easy.

You’ll notice, I link to a lot of games. These are often affiliate links; I choose this as one small way to get a bit of jingle for my blogging efforts.

In working on this website, I’ve ensured you need not use Javascript. The site works without Javascript. When you disable javascript, the Search feature shifts from a local LunrJS system to use DuckDuckGo’s basic search.

I’ve tried to build towards an accessible experience, leveraging accessibility guidelines from Penn State. Go to the top of the page, click the top left corner, then hit the <TAB> key. I love that feature. I learned that from a Skip Links accessibility tutorial.

Beyond posting new blog posts and pages, you can see what’s changed about the site. I provide a list of updates that I’ve made to the content.

You can find me in other places.

Other Profiles

Contributor To


update: Adding content about the changelog and updates.

update: Switching Atom RSS feed from /feed.xml to index.xml and JSON feed from /feed.json to /index.json. This addressed an issue in Hugo’s ExecuteAsTemplate, which did not render absolute URLs.

update: Adding callout to Atom RSS feed and JSON feed

update: On , as an experiment, I tweaked my blog. First, I stopped using custom fonts. Instead, I’m using three long-standing fonts: Times, Courier, and Arial; I wanted to use Helvetica, but encountered an odd rendering issue beyond my skills. Second, I opted to inline the CSS files; Instead of referencing them as a link. Inlining the CSS added 14KB to each page. Both of these changes reduced the number of HTTP requests speeds up performance and improves the stability of the page.