Enano CMS Project

The decision to shut down the Enano project

June 20, 2016

Hey. I'm Dan. I wrote Enano.

It started out as a small initiative I had in high school to make a CMS that didn't suck. I wanted it to be themeable - to the point where you could have no chrome on it at all - and present very well, but without feeling massive (PHP-NUKE), being super complicated to learn and maintain (Drupal), or full of security flaws (Wordpress). It was also a chance for 15-year-old me to learn how to govern an open source project and build a viable product from the ground up.

In all honesty, I succeeded. Enano still has what is possibly the best ACL system in any CMS today, still sticks to its original goals, and still doesn't feel arcane to use.

In addition, Enano is how I learned how to be a coder. I learned about best practices, revision control, patches, installation, user experience, database engineering, optimization, licensing, graphics design, release engineering, and a whole host of other topics. Enano made me well-rounded enough to handle a lot of different roles at least at a basic level, and was therefore a major contributor to my personal success.

So, even though the project is more or less dead, I don't regret developing it at all, and would go back and do it all over again if I had the time and need for it.

But, a lot as changed since then:

I want to offer my heartfelt thanks to the many individuals who contributed to the Enano project over the years:

Dan Fuhry