We’ve all heard the golden rule of system administration: double-check your commands in the terminal before pressing Enter. As a part-time system administrator and web developer, I always believed I was cautious enough to avoid a catastrophic typo. But yesterday, while performing routine maintenance on my production websites, I lived through every sysadmin’s absolute worst nightmare.

In my last post, I explained why I decided to roll back from Drupal CMS 2.0 to Drupal Core. While Drupal CMS 2.0 is a fantastic "move-in ready" product, I realized that for my own websites, I prefer the additive development approach. I want to lay every brick myself to avoid the "div soup" and module overhead.

Today, I'm uninstalling Drupal CMS 2.0 and setting up a fresh instance of Drupal Core 11.3.8.

As an open-source enthusiast, I have been using Drupal to build websites for over a decade, starting with Drupal 7. I have always viewed Drupal (now Drupal Core) as a bare-shell apartment: the structural foundation is rock-solid, but you have to install every wire, pipe, and tile yourself before it’s livable.

But as I started planning my new blog daweibro.com — a space where I'll be exploring the intersection of digital assets and financial independence — I realized that time is my most valuable asset. Instead of the old manual way, I decided to embrace a new path: Drupal CMS.