The strategy on the back of SharePoint Simple CMS (Part 1)

When I'm talking about the SharePoint Simple CMS something that captures the attention is how we defined our product.

In this article I will also publish information about what we are finding out and what are we planning to do with our product.

1. Trying to modify the out of the Box Sharepoint is senseless. At least from the perspective of adopting new future versions of SharePoint. Any deep modification on the current SharePoint would be expensive when a migration to a new version would take place.
2. SharePoint by itself presents many limitations when thinking on Web design. Isn't it better to start with a blank canvas? Masterpages are synonym of freedom!
3. Many users doesn't care if they use SharePoint or whatever else... the important thing is that can be "used" and serves its purpose. That means that the interface is important.

Then we thought: "We need to make an easy to use CMS that limits advanced functionality to editors, that can look great and be compliant with standards, that doesn't touch any our of the box SharePoint page and of course that uses independent custom master pages". Therefore we made the SharePoint Simple CMS.

It is great because it lets users to have good looking public facing Web sites and edit them with ease. The SharePoint Simple CMS is delivered as a STP file and it is compatible with WSS and MOSS. Having a STP file out f a Web site is great! because you can create as many sites as you wish using that template.

After a year we havediscovered some things that need to be improved:

1. The code should be simplified and optimized.
2. We should include more code on the "server side" instead of the "Client side".
3. We need to include more capabilities to customize the layout of the pages.

So.. how are we thinking to cover the challenges? we are building a community of partners that can use SharePoint Simple CMS and build solutions on top of it.