custom css and js files, having them in document tree or not

Hi

I was normally have all my css under assets/templates/mytheme/xxx.css or js files under assets/js/
I read an article at modx wiki about moving this files to document tree and i thought its cool but cant understand much which is better and why shuold i prefer .

It will be good if power modx users, stuff share how to use them, put their inputs pros/cons about it thanks

Using CSS as a document allows you to have logic in your PHP and to dynamically change it with snippets.

Quote from: rthrash at Apr 04, 2007, 11:43 AM

Using CSS as a document allows you to have logic in your PHP and to dynamically change it with snippets.

Thanks rthrash, is it also good if we use js files like that ?

You can use this technique to generate any kind of content dynamically. I’ve used it to generate various XML formats, including RSS, GeoRSS, and several proprietary formats for custom applications (Flash remoting, AJAX, etc.), JSON responses for AJAX requests, traditional javascript files, and even dynamic graphs generated as .gif’s. Any content you can produce with a PHP script is fair game.

Thank you OpenGeek ill go reset my test site with this updates

Wouldn’t it speed-wise be better if css and js-files are static documents instead of being parsed by the modx-engine?
I would think that it’s only when you need to have the css and js to dynamically adapt to your content that having these in the database/document tree would be beneficial.

It would indeed likely be faster to have js/css as static regular old files on the filesystem. But if you turn on caching, then that kinda-sorta happens, though with a tiny bit more overhead. You could then cache the documents but call the always changeable bits uncached.