Non-Published Publishing Tools

Nowadays, every indie publisher seem to develop his or her own custom publishing tools, be it a custom website and newsletter tool or some fancy iOS app generator. While most of these tools will never see the glaring light of the general public, some are made available commercially, so that anybody willing to pay may use them.

Funnily, quite some of these tools are somehow made available, but not really. The Glide platform, used by Jim Dalrymple’s Loop Magazine since more than one year, is announced to become available only “over the next few weeks”. Curated, the website and newsletter tool used by iOS Dev Weekly, is currently looking for exactly 45 customers, paying $995 each for one year of access. On the contrary, tools like TypeEngine are available to everybody.

While I don’t agree that such publishing tools are unnecessary as such, we have two fundamentally different business models here. On the one side, there are tools that are marketed and sold as just that, being tools, computer software. On the other side, there are tools that are just the tip of the iceberg of a much bigger product, which is a publishing service. So, if you also have a publishing tool ready for distribution, please think twice if you want to be a software company or a publishing house, or, to have it ever better worded, if you want to sell software or consultancy services.

If I were a writer, I would probably buy software, instead of publishing services, but that’s my personal opinion.

Back to WordPress

Today, I’ve migrated my blog back to a WordPress installation, after having used Jekyll for a while. I really like the command-line approach of Jekyll, but mobile blogging has proved more difficult than expected, and static blog generation needed to be done on my MacBook instead of on the server, which was another reason blogging got more and more difficult and I became more and more silent here. Shared hosting and Jekyll are probably not the perfect fit at the moment.

Preparing the migration of my blog back to WordPress turned out to be slightly more difficult than I had expected. I wanted the blog to remain exactly like it was, including the site design, mobile UI, the URLs and the exact behaviour of everything. I ended in writing my own WordPress theme and plugin for custom image uploads and a Python script to import all my Markdown posts into WordPress.

I will always remain a fan of Jekyll, but I’m happy now that the migration worked and I can happily starting posting again – “blogging is preparing for a comeback”!