I have a data-driven site with about 6 pages. I was using the Application.cfc onRequestStart with a cfswitch against cgi.script_name to run queries to fill the pages. I want to move those out of the Application.cfc to their own CFC because it's getting crowded in there. Would a "pages.cfc" with a function for each page that would run the queries make sense? Would there be value in instantiating the object as a session variable so I could make the page calls that way? Is this a best practice? Any place to look to verify? Thanks all!

Don't put CFCs in session. 'best practice' is an MVC pattern. You're basically rolling your own framework here. for a six page site, eh, might be fine, but 6 page sites have a way of being 60 page sites. if I came into work tomorrow and had to take care of that site, I'd put it in an actual framework, and we spent 5+ years with one we built ourselves that worked decently. there's just not an up side to having infrastructure that runs your site that re-invents every wheel

That does make sense. This is part of a larger site that uses an old version of fusebox for simple MVC.

they're all super light.

I'll take a look at the current version of fusebox.

what's discouarging?

fusebox.org is dead, it doesn't look like the github page has been lookeed at for a while, and yeah what you said...

FW/1 is still used a lot but it's pretty much in maintenance mode

ColdBox is the only one that's being updated on a regular basis.

I don't really know what 'heavy' means in this context - you only have to learn the parts you want to use and if that's 10% of Coldbox or 50% of another framework, it's still the same learning curve, you just know less about the stuff you didn't need in Coldbox's case