A year after this thread, I'm wondering where people stand on use of these bigger templating frameworks/portals. I want to pick up what I started with OpenInteract but there seems to be almost no activity there. I'm wondering if maybe just using Template Toolkit directly or switching to something like EmbPerl would be just as good. I also looked at Slash. I like the maturity and widespread use of it but it seems more oriented towards a discussion/news type of interface. What I'd ideally like is something that offers templating, the ability to make use of our existing Perl packages in dynamic pages without a ton of effort, and an inheritence type of model that allows all pages to share common characteristics in one place. Ideally I'd also have some sort of authentication/access settings to control access (e.g., have admin-type pages only privileged users can access). Content would be primarily presentation of data, mostly oriented around a set of jobs we run within an existing framework. Data would come from both databases and other sources (logs, files, etc.). We'd also want to hang documentation there, including automated POD extractions of packages we use and build.
Any recent thoughts?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|