-
Notifications
You must be signed in to change notification settings - Fork 0
Overview
As developers we hate stuffing a site into a content management system. It is not natural to us. We are always altering our libraries just to work with different systems. We are learning the different functions that require a CMS to work. We are dealing with the custom routing rules of the particular CMS. Cloudmanic CMS lets you develop the way you want to develop. Cloudmanic CMS gives you a robust admin panel on top of your code base.
If you look at most content management systems on the market today they all solve the same problem in different ways. They all provide a platform for non-developer types (ie. sales, marketing, and designer type people) to manage a website. Typically these systems provide a layer of abstraction between the raw HTML and the user. These systems are great for everyone but the developer that has to set them up.
If you are a senior developer the chances are pretty high you hate building websites on top of content management systems. Why do you have to point and click 100 times just to add some text to the site? Really.......we all just want to open our favorite text editor and update the text and get back to tweeting, right??
Cloudmanic CMS is a content management system built by developers for developers. Never again will be forced to build on top of some crazy developer unfriendly platform.
Best to describe the problem Cloudmanic CMS is trying to solve with an example. At [Cloudmanic Labs](http://cloudmanic.com?utm_source=Cloudmanic CMS-wiki&utm_campaign=cloudmanic.com&utm_medium=github) we have a number of marketing websites. Our core marketing site is [http://cloudmanic.com](http://cloudmanic.com?utm_source=Cloudmanic CMS-wiki&utm_campaign=cloudmanic.com&utm_medium=github). We custom build our marketing sites. There is no need for the bloat of a content management system when 90% of the content is managed by developers or employees that know how to edit an html file and commit to git. However, there is 10% of the site that a CMS can be really useful for. Our blog, our support documents, and a few other things are really dynamic in nature. Content that changes regularly or is managed by non-developer types really needs a CMS. We need a control panel to support our dynamic content, however, we do not want some clunky framework. Enter Cloudmanic CMS.
Cloudmanic CMS is a product we built to "scratch your own itch". After using almost ever content management system on the market we simply were not happy. We plan to continue to evolve Cloudmanic CMS over time because we use it everyday to support our company's properties.
-
The CMS can be an afterthought. Build your site then add the CMS.
-
An add-on to your custom PHP web application. You install Cloudmanic CMS via composer.
-
Super customizable. Your admin panel will just be for your site with no other cutter.
-
Very easy to develop locally and then push to production. Since so much of a traditional CMS is database driven working locally and then pushing to production is often a challenge.
-
Out of the box support for file storage on CDNs such as Amazon S3 or Rackspace. Most content management systems do not do this and it makes scaling a challenge.
-
No crazy database structures. Since you will likely be making queries against your database outside of the CMS you want to manage the schema not the CMS.
-
Asset manipulation. Upload and Crop your images on the fly.
-
Easy, fast, simple. Cloudmanic CMS does not do it all. But the things we do we do very well.
- PHP 5.3+
- Mysql 5.5+
- Composer
- gd
- imagemagick
Our reasons for the stupid name.....
-
Guess who Cloudmanic CMS is developed by? You guessed it, [Cloudmanic Labs](http://cloudmanic.com?utm_source=Cloudmanic CMS-wiki&utm_campaign=cloudmanic.com&utm_medium=github). We are a for profit business. While we do not intend to make money from Cloudmanic CMS (at least not in the sort term) we are using our company resources to build it. We do hope to earn some return by bring some attention to our company and paid products via this open source project. So chalk the name up to branding.
-
The last thing we want for a free product is some sort of trademark issue. By using our company name we think we can safely avoid future trademark issues.
-
Lastly, we just have not thought of a better name. If a better name ever came to us we would consider changing the name.
Cloudmanic CMS will not be the best tool for all needs. If you are looking for a complete CMS solution we recommend these tools.