Learning WordPress Then Jekyll (Daniel Brinneman)

In theory, I’m happy with this setup. No more database and security issues tied to that. No more slow loading. Twig and Collections are enough for creating the functions and section pulls that I need and the last thing I’m wrapping my mind around is images and I’m sure that Gulp (runs tasks you write to do functions you need, like resizing thumbs for images) will be next on the list for creating responsive images for mobile screens.

I don't get paid for web development anymore. I still use WordPress on my main website because I want 100% ownership and control of my content. I want to allow comments from the community and other readers who won't have a website and those who can't be bothered with Webmentions. That rules out the use of static site generators such as Jekyll and Hugo. I don't trust Disqus with my comments. They can shut down or change the terms of service just as easily as Google+ can be shut down.

However, one of my websites is mostly just static content and I don't need a commenting system. I am creating a plan to move that website to Hugo. I am not interested in learning more than is necessary to create and maintain the site. I don't want to learn the Go language. I don't want to learn more than necessary about the underlying technlogy. I care about the content. Anything that detracts from that will be ignored.

If I run into a technical problem, I will resolve it and then move on.

My youngest kid is in a senior in high school and the eldest is a junior in college. I want to spend more time with my youngest before she leaves for college next year. I want to spend time with my wife doing some of the things we put off while the kids were younger.

Island in the Net used to be more about technology and geekery but in the last few years it has been focused on my photography.

Author:Khürt Williams

A human who works in information security and enjoys photography, Formula 1 and craft ale.

5 thoughts on “Content”

Comments are closed.