here's something for anyone who has ever done web design: this template phenomenon. unless you have two different departments working on the front and back ends of the site, I fail to see how templates do more than make you type the layout for a page twice: once for the template and once for the script that fills in the template.
granted, you can use one template with more than one script, but you still end up with a bunch of ugly template-filling code in each script that could be replaced by integrated html that otherwise would be on the template.
it just seems like too much work to me and I think I am about to change everything to non-template design and although that, too will be extra work, it will result in less server overhead now and a different approach for later so that I don't have to try to decide what should be templated and what not and where and how you can interleave php with them, which is difficult.
I just don't quite see the point in templates if you are working alone. can anyone enlighten me?
granted, you can use one template with more than one script, but you still end up with a bunch of ugly template-filling code in each script that could be replaced by integrated html that otherwise would be on the template.
it just seems like too much work to me and I think I am about to change everything to non-template design and although that, too will be extra work, it will result in less server overhead now and a different approach for later so that I don't have to try to decide what should be templated and what not and where and how you can interleave php with them, which is difficult.
I just don't quite see the point in templates if you are working alone. can anyone enlighten me?
- Current Mood:
skeptical
Page Summary
Designed by 
chasethestars
chasethestars
Comments
intresting site, too.