What are the main differences between CMSMS and Website Baker? Topic is solved

[Marvin]

I would appreciate some help understanding the differences between CMSMS and Website Baker.

Thanks.

[Anonymous]

They are very similar.

However, I think that in Web Site Baker, it is more difficult to manage templates.  In CMSMS, you simply add a couple "content" and "menu" tags.

Also, CMSMS is constantly being developed - something I don't see as much (at least I didn't think I did) with Web Site Baker.

I'd like to here other's comments.

[Anonymous]

CMSMS has an Admin Log.  WHen I asked to see if Website Baker had one, the members asked why in the world I would need one - a stupid question for anyone who uses a content management system with multiple users.  THis was the main reason for coming to CMSMS.

Website Baker is a little better in one area: you don't have a lot of settings at the top of the "Edit Content" pages like CMSMS does.

[uptoeleven]

since the wysiwyg editor is a module you can edit the settings separately to reduce the number of buttons shown, you can even use a different wysiwyg or none at all if you like.

[Ted]

I think he means more like the number of boxes above the wysiwyg.  Menu text, page alias, etc.

[katon]

I looked at websitebaker and dropped it, because the interface looked ugly

[Marvin]

Thanks for all the helpfull replies. I have a couple of more questions if you guys don't mind indulging me.

1) Can I integrate a message board like this one into CMSMS without having to do any coding? If so what message boards can I use with CMSMS?

2) Same question but for uploading/storing/managing pictures. Something like a photo gallery?

3) Same question but for a simple/basic shopping cart?

If I can "plug" in those three functions into a CMSMS based site without knowing how to program then CMSMS would be absolutely perfect for me.

[katon]

1) Can I integrate a message board like this one into CMSMS without having to do any coding? If so what message boards can I use with CMSMS?

Look at the PunBB module.  In fact, you can use any forum, just set it up in a sub directory and tune the header and footer.  This will take some coding in the templates.

This one (SMF) is actually very nice.  If we are lucky, we can soon have an integration of SMF with the FrontEndUsers module.  This, however, will require changes in the SMF code.

2) Same question but for uploading/storing/managing pictures. Something like a photo gallery?

There are quite a few picture galleries out there.  If you need a simple one, I would recommend PiPictures.  If you need support for categories, image sorting, etc. choose SingaporeGallery or Gallery2 modules.

3) Same question but for a simple/basic shopping cart?

There is a port of osCommerce, but I haven't had a chance to try it out.

If I can "plug" in those three functions into a CMSMS based site without knowing how to program then CMSMS would be absolutely perfect for me.

From what I can judge at this point, CMSMadeSimple has a great core, combining unprecedented usability and very good internal design.  What it lacks at this point is a set of good uniform plug-and-play extensions to satisfy the needs of a common user.  Things like an integrated forum, integrated shopping cart, integrated picture gallery with albums and image sorting capabilities...  But I understand this is an enourmous piece of work...

[amygdela]

I personally think CMSMS shouldn't include all those extensions. There are not many cool, easy to use lightweight CMS's out there and this is actually one of them! I think they should keep it that way. But that's just my 2 cents.

[katon]

Sorry if I didn't make my point clear.  I didn't mean to include these modules in the standard install.  I mean that the extensions that are out there in the dev section need a bit more attention.

[nils73]

I have worked with both CMSMS and WebsiteBaker. While I must admit that WebsiteBaker wasn't that bad it sucked each time I had to do something special starting with the navigation. CMS made simple 0.12 is cutting edge when it comes to handling menus the smart and easy way. And moreover it is based on Smarty which is probably the best templating engine out there. Almost anybody can learn how to use Smarty to achieve certain goals.

The main difference is performance: CMSMS is much faster than WebsiteBaker and above all wishy and all the others do a great job maintaining and developing the whole system. The community here is much better and wehn it comes to accessibility CMSMS beats a lot of CMS out there!

However you could write a complete book about the differences, advantages and disadvantages - but in the end you need to see for yourself how much work is required for either system (setup, maintanance, etc.) and then you have to make your decision. I made mine ...

Regards,
Nils