Re: Template::Toolkit::Session

[simon.proctor]

From what you have said, the Session plugin you have written affects the content displayed (if user has this.... if user has that... then display this...). If that assumption is correct then I would argue your module is affecting what is displayed and not how the core engine operates in creating that display.

If that assumption holds true then your plugin should, IMHO, follow the standard plugin structure that every other plugin follows.

I agree with the distinction made between content production and content management. I feel this distinction holds true to your plugins purpose (management not production).

Perhaps this plugin is something you could post into craft (or here) so we can see it?

But....thats just my opinion :) Have fun!

PS: I would argue that its equally as valid to instantiate your module as an object in your main code and pass it as a var in the template setup. But that really depends on the structure of your plugin.