Coexisting SSG and CMS, Moving Away from WordPress

Hello, this is Munou. Since my previous blog post, I've set up the CMS to be accessed separately from the public site itself, which is built separately. I also created a daemon script on SysVinit to detect changes within articles.

What I wanted has been achieved

Until now, I had no complaints about the usability or display when using WordPress. * The ability to edit articles from the browser as a CMS * Easy image uploads * The ability to write in Markdown

In particular, the ability to edit from a browser is quite important to me personally.
It's understandable that many sites hosted with SSG tend to be left unupdated. This is because editing in Markdown, building, and then git pushing incurs some labor costs. For a blog site, the easier, the better.

Concise code

LumeCMS has very simple code, making it quite easy to customize. It's not bloated like WordPress. This isn't a criticism of WordPress, but rather an acknowledgment that it's good when it matches what a website needs and suits the individual.

No database required

Not requiring a database means not using server resources, which is very eco-friendly. There's no need to create a separate user for the DB, and no risk of the DB crashing and getting corrupted if something goes wrong.

Easy editing screen in CMS

The /admin page is simple and very easy to view.
If I were to wish for something, it would be easier if I could choose the sorting order when viewing posts. In reality, WordPress's usability has advantages for large-scale websites with many users.
However, since mine is just a personal blog, I thought this alone would be sufficient.