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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.