What about good old server-side include (.shtml). (Takes slight
apache/webserver config if no already setup.)
Is any of the content dynamic or is the point to just include (if the
latter than I can think of no better way than .shtml).
With love in peace,
--
Joseph Francis Frana
Student Pastor
Duke Divinity School -----Salem - Harris Chapel UMC Cooperative Parish
On Mar 19, 2008, at 12:03 PM, Nathaniel Green wrote:
One way to do this would be to use a templating system. We use
Template Toolkit ( http://template-toolkit.org/ ) at work.
The basic idea is similar to php, in that you embed code in your html
files. This would also let you create a wrapper, so you could define
your tabs once in one file, then use that file to wrap the actual
content of an individual page. The difference between templates and
PHP is that instead of executing the script every time the page is
served, you compile your templates into static html. Then you serve
that to the client.
One downside might be that this is more obscure than something like
PHP. But it should be more secure.
Nate Green
'04 Alumnus
Wow, I'm old.
On Tue, Mar 18, 2008 at 11:12 PM, Huan Truong <[EMAIL PROTECTED]> wrote:
Thanks for your kind words, Scott. I was talking about the site on
IRC, and I have received something that we need to consider from
Entheogen:
In order to keep the uniform look for the site, I must apply some
sort
of dynamic page generation, in this case PHP, so we don't need to
edit
all the files just to add or change a tab. I think it is
important to
plan ahead because we need to plan for the future when we will
have at
least tens of pages and it won't be easy to manage all the pages
_individually_ as it is now.
And in reality it is not a good idea to enable an scripting language
in a server that opens to almost everybody in campus like the FSCK.
And the second drawback is that not many people can understand
what's
going on with my way to organize things and it would make
students who
are new to manage the site in the future. I have an idea to restrict
changing files just in /static/ directory and disable PHP
execution in
that directory, to make the site more secure.
So basically, we have two choices, leave it as it is, with old-style
HTML so everyone can (easily?) change *or* do the new way with more
restrictions on editing pages.
- H.
On Tue, Mar 18, 2008 at 11:12 PM, Huan Truong
<[EMAIL PROTECTED]> wrote:
Hi,
Thanks for your kind words, Scott. I was talking about the site on
IRC, and I have received something that we need to consider from
Entheogen:
In order to keep the uniform look for the site, I must apply
some sort
of dynamic page generation, in this case PHP, so we don't need
to edit
all the files just to add or change a tab. I think it is
important to
plan ahead because we need to plan for the future when we will
have at
least tens of pages and it won't be easy to manage all the pages
_individually_ as it is now.
And in reality it is not a good idea to enable an scripting
language
in a server that opens to almost everybody in campus like the FSCK.
And the second drawback is that not many people can understand
what's
going on with my way to organize things and it would make
students who
are new to manage the site in the future. I have an idea to
restrict
changing files just in /static/ directory and disable PHP
execution in
that directory, to make the site more secure.
So basically, we have two choices, leave it as it is, with old-
style
HTML so everyone can (easily?) change *or* do the new way with more
restrictions on editing pages.
- H.
On Tue, Mar 18, 2008 at 9:46 PM, Scott Thatcher
<[EMAIL PROTECTED]> wrote:
Huan,
I didn't visit the old page very often, but I think the new one
sets a good
image for the group. I've been quietly glad that you're taking
this on as a
project.
Scott Thatcher
--
Scott Thatcher
Associate Professor of Mathematics
Truman State University
[EMAIL PROTECTED]
-----------------------------------------------------------------
To get off this list, send email to [EMAIL PROTECTED]
with Subject: unsubscribe
-----------------------------------------------------------------
--
"Ubuntu" is an ancient African word, meaning "Slackware is too
hard for me".
http://tnhh.info/
--
"Ubuntu" is an ancient African word, meaning "Slackware is too
hard for me".
http://tnhh.info/
-----------------------------------------------------------------
To get off this list, send email to [EMAIL PROTECTED]
with Subject: unsubscribe
-----------------------------------------------------------------
-----------------------------------------------------------------
To get off this list, send email to [EMAIL PROTECTED]
with Subject: unsubscribe
-----------------------------------------------------------------
