Forum OpenACS Q&A: Re: Arbitrary Template File Extensions

Collapse
15: Re: Arbitrary Template File Extensions (response to 1)
Posted by Dave Bauer on 08/22/03 01:09 PM
Hmm, after having this in the back of my mind I have the ideal solution, but it will require some work.

Store the CSS attributes in the database. Then you can manage them in one place, but still use multiple CSS files with almos t the same contents. Using the content repository you could build up the CSS file and publish it to the filesystem.

This won't work without some code, and any CMS effort we work on should include at least some support for CSS files.

Collapse
17: Re: Arbitrary Template File Extensions (response to 15)
Posted by Ralph Hempel on 08/22/03 01:55 PM
This won't work without some code, and any CMS effort we work on should include at least some support for CSS files.

Dave, it's clear that leaving stuff in the back of your mind helps you understand the problem 😊

I think what you are suggesting will work, but I'm not sure that the support has to be specific to css files. The css is really just a special case of the general problem of generating page contents based on location in a file system.

That being said, it _would_ be nice to have a UI that allows one to browse attribute/value pairs and assign them based on location in the published file tree.

ie, if you're asking for a css file for a file being published to foo, then make the P tags orange. If the file is published to bar, make them blue, and so on.

Ralph