Twan Kogels wrote: > Zo is de documentatie zoals eerder gezegd slecht. (freely translated: The documentation sucks.)
I agree that documentation need be improved, though I think parts are quite well documented. Taglibs is quite extensively documented, and we are working on the editwizard docuemnation, which will be written in Docbook. But overall we can do with more docuemntation, epsecially concernign installing, the inner working sof MMabse, and how to actually use and set up an object cloud (esp. concerning relations). Unfortunately, most peopel actrively involved in improving the system are developers - notorious for producing lousy documentation. We hope some more talented (technical) writers will help us produce better documentation, Henk of MMatch is working on some - but we feel the MMBase Foundation (anything happenign there? anything AT ALL?) could do their share. In short, we are dependent on goodwill for documentation, which means it is progressing quite slowly. > MMbase is geen cms opzich, eerder een basis (free translation: MMBase is not yet a 'finsihed' CMS) Well, a CMS is, essentially, just a lot of data and a tool to manage it. In that view, MMBase is definitely a content management system. Better so than systems such as Zope, which are moer akin to WEB management tools. Ofcourse we are need to keep improving those tools. Feel welcome to particpate and shar your ideas. > Het zou beter zijn geweest als ze zoiets als op > <http://enhydra.enhydra.org/> hadden gedaan, daar bestaat het ontwerp > uit custom HTML tags. (free transalation: why not use custom HTML Tags, such as Enhydra?) I am not sure if Enhydra/XMLC is - in basis - much different than the taglibs we use for MMBase. Taglibs are a type of custom HTML tags - you can use them to obtain data and display it in the HTML page. I find they are relatively easy to use, and - to MMBase standards - well documented. -- Pierre van Rooden "All your MMBase are belong to us"
