Software Engineering in Web Development, Backend Services, and More
Posts introducing, updating, and covering various projects to which I’ve contributed or that I maintain.
With the recent release of WordPress 3.6 and its built-in support for audio files, I’m opting to to halt development on WP Audio Player for WordPress plugin.
Here’s the thing: This has nothing to do with WordPress folding something into core that was once available via plugins and putting a plugin “out of business.”
Mostly, it has to do with my personal preferences and opinion behind the core libraries used in WordPress 3.6.
Earlier this month, I shared that I was releasing a WordPress plugin exclusively through the guys over at Foo called PDF Comments.
However, in the last 25 days or so, I’ve received a lot of feedback generally saying that the plugin is something people need, but they need it to be more flexible in the document types that it accepts.
So I’ve officially rebranded PDF Comments as Doc Comments, updated the purchase page on Foo, and introduced support for a number of new document types.
The last time that 8BIT released a theme, it was in June of 2012. We had just dropped Standard 3 and although we’ve done iterations on the product almost every quarter, we’ve generally stayed hyper-focused on that single product in order to make it the absolute best that it can be.
As of of right now, 3.4 is in development and the theme is in a really good place.
But one of the things that we, as a team, wanted to do for the WordPress space was to give something back, and do so with the highest level of quality we could given a tight set of constraints.
Yesterday, we officially launched Required.
In the last release for Markdown Code For WordPress, I added support for `strong` and `em` tags by using asterisks, but as with all software, there are always edge cases.
And there lies the beauty of keeping source code openly available for others to download, use, and improve.
So in the latest release, there have been some edge cases that have been fixed especially thanks to GeertDD.
When I first started working on Markdown Code For WordPress, the whole point of the plugin was to create an extremely simple solution for making it easy for me to replace `lines of code` without needing to hop into the visual editor, or to install a larger plugin with full markdown support.
Over the past couple of months, the plugin has received a little bit of refactoring, some good feedback of which I hope to implement (but it’s very low priority side project so, y’know..), and a pull request to simplify the code even more.
Love it.
However, I’ve gotten a bit used to the plugin (and markdown), so I’ve ended up adding support for two new markdown features into the plugin.
Kinsta offers premium managed WordPress hosting for everyone, small or large. Powered by Google Platform and strengthened by Cloudflare, they take performance to the next level. All hosting plans include 24/7/365 support from their team of WordPress engineers. Get started with a free migration today.
© 2026 Tom McFarlin
Theme by Anders Noren — Up ↑
