…but Drupal is still on my mind :)
I told myself that I’m not going to use WordPress anymore. Because of the relentless push for the Gutenberg project to become part of the core software in 2018 — despite the thousands (millions?) of voices against it — WordPress is no longer as easy to use as it once was, and it’s no longer as reliable and stable. For me and for many others, the most annoying thing is that the Block Editor (which has replaced the word-processor-like Classic Editor) has made writing and publishing very difficult. It forces you to think in terms of layout and style, when all you want to do is to focus on your content.
But there really isn’t many choices out there, for a CMS that a relatively new webmaster like me can use. ClassicPress, a fork of WordPress before Gutenberg was introduced, is not yet a viable option. Too slow a development. And too few developers. Not to mention the fact that, increasingly, many WordPress plugins and themes are now incompatible with it. ClassicPress has its own extensions, but not many.
As for this blog, it runs on Textpattern. And I like Textpattern very much. I like the simplicity and elegance of it. But the problem with Textpattern is the lack of ready-made plugins and themes. And so, unless you really know HTML, CSS, and PHP, there isn’t much that you can do with it. However, Textpattern does have its own “powerful tag-based template language that’s easy to learn and provides a wealth of ways to structure a website and manipulate content.” Learning this language is something that I look forward to — but not now.
A month ago I wrote a post and said that I’m going to start learning Drupal, which is an enterprise-level CMS. And I did start that process, but I was repeatedly interrupted before I got far in my study. Besides, the going was very slow. Learning Drupal, even without programming, is really as difficult as they say. It is described as a gigantic LEGO tool kit for making websites. You can do (almost) whatever you want with it. The catch is, you have to know how to put together the many different pieces, and you also have to know, in advance, the details of the website you’re going to build. In short, it’s not easy, and it’s not for someone who’s in a hurry, like me.
But I haven’t given up on Drupal. I’m only postponing my journey with it. After all, it is still the best CMS that I can use for my future ministry websites for OnlineBibles.net.
And so, for now, here I am… back to using WordPress. And I will embrace it, Block Editor and all. And the main reason why I’m using it again (despite my reluctance) is not because I don’t have other choices, but because I’ve been given the chance to participate in a soon-to-be-opened WordPress community that focuses on Knowledge Base and Support. It’ll be a community where anyone can join, and write articles and ask questions on how to use the software and its many extensions. As a new freelance writer of both Christian and technical writing, such a community can be an important platform for me — a place to showcase my technical writing skills.
So what am I going to build with WordPress? Three websites for my writing business. Yes, three. Not one, not two, but three.
For ten months now I’ve been planning and preparing for my new freelance writing career. There’s still much to do, and except for a few articles I’d written for a client, I’m not yet actively looking for projects. What I need most right now are the three websites: the first one will be my main website as a freelancer, the second one my portfolio for Christian writing, and the third one my portfolio for technical writing. They need some time to be built, and so my focus will be on them in the coming weeks.
Note: Besides showcasing my writing skills, I’m also planning to monetize my two portfolio sites with affiliate products later on, when I’ve built my audience. So the new business career that I’m looking forward to is both freelance writing and affiliate marketing.