Hello everyone! 
I am thinking of doing some more work on Guestaphics. A very buggy demo of the proof of concept is in my signature.
Developers
This uses PERL which I know upsets people but I have a reason: The skill sets of server-side programmers and client-side programmers (which applies to maintenance programers aswell) are completely different and to prevent them stepping on each other's toes, their respective sourcecode would ideally be completely seperate from each other.
In it's very concept, PHP merges the all the code. PHP works very well for small projects but increases the danger of spaghetti-code in large projects. It also presents difficulty for webmasters.
Guestaphics is a small project, but I would like to treat it like a large project so I can practice SDLC
HTML users & developers
I would like your input on how to construct an ideal template: the sort of thing you might edit to intergrate a product into your website.
This is a poor example. Please give feedback and post suggestions for how your ideal template solution. My idea is based on the concept of SSI, where the server parses the template and replaces <!--#SSI --> commands with data generated by the server-side script.

I am thinking of doing some more work on Guestaphics. A very buggy demo of the proof of concept is in my signature.
Developers
This uses PERL which I know upsets people but I have a reason: The skill sets of server-side programmers and client-side programmers (which applies to maintenance programers aswell) are completely different and to prevent them stepping on each other's toes, their respective sourcecode would ideally be completely seperate from each other.
In it's very concept, PHP merges the all the code. PHP works very well for small projects but increases the danger of spaghetti-code in large projects. It also presents difficulty for webmasters.
Guestaphics is a small project, but I would like to treat it like a large project so I can practice SDLC

HTML users & developers
I would like your input on how to construct an ideal template: the sort of thing you might edit to intergrate a product into your website.
This is a poor example. Please give feedback and post suggestions for how your ideal template solution. My idea is based on the concept of SSI, where the server parses the template and replaces <!--#SSI --> commands with data generated by the server-side script.
HTML:
<!DOCTYPE>
<HTML>
<HEAD>
<TITLE><!--# $title --></TITLE>
<SCRIPT LANGUAGE="javascript" src="gui.js"></SCRIPT>
<SCRIPT LANGUAGE="javascript" src="zoom.js"></SCRIPT>
<SCRIPT LANGUAGE="javascript" src="wysiwyg.js"></SCRIPT>
</HEAD>
<BODY>
<DIV ID="header">
<IMG ID="banner" SRC="" />
<!--# $timestamp -->
</DIV>
<DIV ID="guestbook">
<!--# $tab_data -->
</DIV>
<DIV ID="form">
<FORM NAME="new_entry">
<INPUT TYPE="text">
<INPUT TYPE="submit">
</FORM>
</DIV>
<DIV ID="footer" ALIGN="CENTER"><!--# $copyright --></DIV>
</BODY>
</HTML>