I wanted to build a bit more on my game blogging. What fuels this blog and the framework I use to build it out.
My face to face gaming feeds this blog. The actual play as well conversations around the game session itself. I reflect on the highlights (and lowlights), looking for the magic.
I prioritize reading. I typically get about 40 books in per year; Ranging across genres, fiction and non-fiction alike. I also read a lot of game sourcebooks.
I follow numerous blogs. From these blogs, I read the more deliberate conversations. The majority of my feed is gaming blogs, but I also subscribe to a plethora of other blogs.
Over the past month, I switched from using Feedly.com to using Inoreader.com. I use Inoreader to star, save posts to Google Drive, categorize, and subscribe to blogs.
I find less fuel on Social Media that sparks a response—Aside from clicking on a blog post and adding it to Inoreader.
A Tangent that Loops Back
I started blogging in 2010 as part of my day job; I used a campus provided Wordpress instance. In 2011 I started my game blog leveraging Wordpress.com. I had thought about Blogger, spending a bit of time in an aborted migration, but opted to remain on Wordpress.
I switched roles on campus, and moved my professional blogging to ndlib.github.io: A site powered by Jekyll. We sought to build-up a team blog. During this time, I actively engaged in Github code contributions. Github leverages Markdown for its rich text comments. I find Markdown more legible than HTML* . I will often write Markdown in Atom.io—my text editor of choice. I use the markdown-preview-plus plugin to preview the Markdown as HTML.
I prefer Markdown over HTML or WYSIWYG* editors. I spend time thinking about the content and not poking around formatting the content.
On September 9th, I started once again migrating from Wordpress. . I had stumbled upon the Tufte Jekyll theme. One that purported to be a “Minimal Jekyll blog styled to resemble the look and layout of Edward Tufte’s books.” I became enamored with the layout of the demo page
I dove into the migration, starting first with Jekyll Import. I performed a full clean-up; I wanted to embrace the new theme. I also wanted to preserve links from other pages. This involved a mix of scripts, manual changes, and patience.
I have scripts that:
- Create proper aspect ratio derivative images for side, main, and full images.
- Create an AMP* compliant version all pages, while maintaining a the foundational fast non-JS* dependent site.
- Extract image metadata to have proper aspect ratio for the AMP version of the site.
- Beautifies the HTML generated from Jekyll by normalizing indents and spacing.
- Takes a tag and adds new tags to posts that already have the tag.
In other words, once I cutover from Wordpress to my new site, I’ll have full control over my blog’s data. And I love it.
Until I switch over, I write my post first for takeonrules.com, then do some HTML antics and copy it into my Wordpress site.