> A lot of people recommend mt for a basic, free CMS, but I > don't think it would really be applicable in this case. MT is > really a CMS designed for news items. Somthing that gets > created, then archived. Not really for content that gets > constantly accessed and modified.
I did get that impression when I looked at it - It was just a quick look though so wasn't sure if I was missing something. Your right in your assessment of our needs - I want a page with pictures and text that people can constantly update and add to. If a new version of the product comes out it needs to be added as the latest model on the range guide, if a spare part is replaced with something different we need to modify the technote to show the old type and the new type and perhaps a note of why it was changed. Maybe a customer brings in a sample of something we've never seen - we can take a photo and add it to the guide. They are basically constantly growing and evolving documents as we encounter new problems and or information about products. Also due to the quantity of the pages I need an interface that allows one to select the page to edit from the actual page itself without having to login to the admin screen and then find it amoungst what will become an enormous list, even catagorising will not help that much. I also noticed it ran on perl as does the wiki Peter VanDijck mentioned - I'm a bit reluctant to install perl as I have no knowledge about it whatsoever and I'm having enough fun learning .net, vb.net,C# and SQL Server without adding another one into the mix at the moment. Thanks Morkai -- http://cms-list.org/ trim your replies for good karma.
