Naming is supposed to be one of the two hard problems in software. I've made it easy for myself by committing to a theme and refusing to overthink it. The theme is coffee. Specifically Philippine coffee, because that's where I am and what I drink.
Barako is kapeng barako, a bold, strong varietal grown in Batangas. It's the kind of coffee that doesn't apologize. So barakoCMS is the name, the logo is a coffee bean, and I didn't agonize over it for a week the way I have with lesser names on lesser projects.
Once you pick a theme it starts doing work for you. The full build, every module included, is "Barako," the real thing, caffeinated. The stripped-down core with nothing added is "Decaf." That's not just cute, it's genuinely the clearest way I've found to explain the difference in one line. "Do you want Barako or Decaf" lands faster than "do you want the full suite image or the core-only image."
It kept going without me forcing it. Modules are shots, the extra thing you add to your cup. The admin UI is the milk, the part that makes it approachable. There's a kit for turning a site into an installable app, and that one's the to-go lid. My other projects have their own names but they all sit under baryo.dev, and baryo means village, so the whole thing is software from the village, which I like more than any tagline I could have written on purpose.
This is the least technical thing I'll post and I'm fine with that. A project you work on alone for years has to be a place you enjoy being, and small deliberate choices like a consistent, slightly silly naming theme are part of how you make it that. Every time I type "Decaf" into a docker tag I smile a little. That's a better return than most of my clever code gets.
Anyway. I spent more words explaining this than I spent choosing it.