"We use Stackable every day. At first it was used solely for content management, but we've recently found it to be a great tool for prototyping our own applications."
Steven Carmo, Creator of Stackable CMS
We developed Stackable CMS for two reasons. First, to give clients the ability to update their websites and second, to give us a simple way to maintain and upgrade all of our websites.
As we continued to develop Stackable, it grew into much more than a standard content management system. We built the WYSIWYG editor from the ground up to be simple enough for a novice to use, but also something that could solve the common quirks that an experienced developer faces every day. What we came up with was Stackable, an editor that exceeds anything on the market today.
We rolled Stackable out into two separate applications. The client application can be deployed to individual servers or to a multi-site hosting environment. The other side is our administrative application. Separating the two makes the system as a whole more scalable and secure. In a cloud environment we can load balance the client applications across any number of servers. In a brick and mortar environment we have the ability to deploy the client in a DMZ, and the administrative/backend in a secured network.
All of our products use this system, which means consistent deploys. When something new is added, all of our clients benefit. We also turned the client application into a Ruby Gem that we can drop into just about any of our other applications. This makes creating application-specific blogs, support articles, and static content a breeze.