I’ve gone through two phases of blogging :
- 2012 ～ 2014: buy web hosting, cloud hosting, tossing performance and technology. At this stage, my blog has gone through several rounds of changes, but also because I didn’t do a good job of separating the production environment from the test environment, resulting in a lot of data loss. The current blog can only go back to 2016 is thus.
- 2016 ~ Present: stopped tossing around blogs and started focusing on content writing and keeping it updated every year to be a living blog.
I’ve been writing for ten years, and I’ve kind of done my share of WordPress-related stuff, but, as time goes by, those engineer’s thoughts in my head inevitably resurface — should I write my own Blog system. For me, it may not have been easy, I don’t have that much development experience. But for me today, it’s really not that difficult.
However, there should always be a purpose and an assessment of the benefits of writing, not ‘writing for the sake of writing’, but a clear purpose and an assessment of the ROI.
Why do I want to write?
- Think WordPress is still too bloated and has quite a few capabilities I can’t use.
- My own Blog system should have a well-defined Feature List so that the requirements don’t balloon indefinitely.
- My needs have gradually stabilized and I don’t really need new themes/plugins anymore.
- It’s true that over the years it’s mostly been about updating content, and the format of the blog, content and whatnot, has basically stabilized.
Why can’t I write?
- Writing a Blog is not particularly rewarding for me.
- After all, there’s no way to sell this stuff, and unless there’s something else to gain from the writing process, which might be okay, the odds are that you’ll lose money.
What Features do I need if I want to write a Blog system?
- Article system: contains several core attributes and entities such as Title, Description, Content, Slug, Catalog, Tags.
- Slug needs to be translated automatically: I especially rely on this feature. Too lazy to translate Slug myself
- Support for automatic image upload S3
- I’m using external links for all my images now so that the server itself isn’t stressed as much.
- Supporting comments
- Comments also need to be able to automatically send email updates.
- Comments should be able to achieve anti-spam.
- History of 600+ comments can be imported
- Simple and stable theme design
- Frankly, I’ve done very few theme changes in the past few years, basically just switching back and forth between a few attraction themes.
- Support for RSS feeds and other capabilities
- Support for online writing (may not be necessary, recently began to gradually write in Ulyssess, in fact, for the web page to write the article of the claim is getting smaller and smaller, maybe Hexo is an acceptable solution).