2 min read
Satisfying an itch I've had for a while, I am working on migrating the back end of pilch.me from Known back to Wordpress. I love Known, but this has been a long time coming. It's probably my own fault for migrating 6 weeks before becoming a new dad (and taking on more at work), but I thought I would have more time to familiarize myself with the inner workings of the platform, to tinker and break things and fix them. I decidedly did not, so I'm heading back to the familiarity of Wordpress.
When I initially migrated, Known had a lot of the Indieweb elements baked in (webmention, early micropub, post formats, etc), and the WP plugins lagged a bit behind. Now they are caught up, while Known development has slowed significantly. I feel a bit like part of the problem, since I'm not sticking with it. But I also do not currently have the time nor patience to figure out how to modify mySQL elements, or maintain URL rewrite rules and .htaccess files. I need to step back into a platform where I don't have to worry about nuts and bolts, and customizing basic/intermediate elements is taken care of in a GUI.
I'm doing the migration manually, post by post. Known exported as RSS, and I was able to import that to start (WP's built-in RSS importer threw errors, so I had to use this). This method created a lot of formatting issues with line feeds, lists, etc., which is why I am doing each post individually. This gives me a chance to review some old posts I forgot about, and also the ability to idly update posts during down time at work (the network there is extremely locked down, and would not allow external SSH/FTP connections).
The current WP install is at blog.pilch.me. I'll probably keep the Known install, and figure out a subdomain for that when I am ready to switch the two.