My unit is currently reviewing our CMS setup. Currently, our site consists of two types of pages:
* "built" pages that take a content page, wrap it in our navigation template, and save the resulting HTML to our htdocs directory. * Dynamic pages that run CGI::App, which passes any output through the same process as the above, but returns the resulting HTML rather than writing it to a file. The system is a simple but flexible mix of CGI::App and Template Toolkit. Metadata (such as hierarchy) is maintained in our database. We have a workflow for content changes where our users grab a content file, edit it in an extremely crippled version of Dreamweaver, upload the content to an app that tracks the metadata. Once it has been modified by any editors and designers, the new content overwrites the old content, and the pages are built. That workflow is showing its weaknesses, and while we're looking at updating it, we're reviewing the entire system to see if we're better off using someone else's wheel. Our review criteria: * Our content managers are, to be blunt, not trusted. We need to be able to restrict what they can do, HTML-wise. (They are not hostile) * Our sites use little-to-no Javascript, and we serve the lowest uncommon denominator. (The content manager can use Javascript, but the resulting product shouldn't). * As noted above, our dynamic pages tie into the same system, so we need some way to maintain this connection. * I distrust highly complex systems, they make it painful to move between systems, which we have done in the past and may do again, even if the system is otherwise perfect. Currently the two systems I'm looking at are: 1) Bricolage 2) Keep the current system and replace the Dreamweaver aspect with javascript-based WYSIWIG editor lifted from any of a dozen sources. Bricolage isn't faring well so far due to its complexity, but it's not out of the running. What else would people recommend I consider? -- SwiftOne / Brett Sanger [EMAIL PROTECTED] _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
