Alexis Lee alexis@turton.com writes:
My way, it would be 7. It would also be easier to get extra candy in, like a datestamp on every file. (You'd have to split tail into tail1 and tail2, then cat tail1 >> product.html; date >> product.html; cat tail2
product.html)
Any scripting language offering regexps would make it fairly easy to build the site from templates and external files. 6 pages would need 9 files (6 content, 1 template, 1 build script, 1 Makefile). This is more or less how I build my website at http://mjr.towers.org.uk/
I don't see how you arrived at a total 7 files unless you're doing some nasty things in the content ones?
MJ Ray wrote:
Alexis Lee alexis@turton.com writes:
My way, it would be 7. It would also be easier to get extra candy in, like a datestamp on every file. (You'd have to split tail into tail1 and tail2, then cat tail1 >> product.html; date >> product.html; cat tail2
product.html)
Any scripting language offering regexps would make it fairly easy to build the site from templates and external files. 6 pages would need 9 files (6 content, 1 template, 1 build script, 1 Makefile). This is more or less how I build my website at http://mjr.towers.org.uk/
I don't see how you arrived at a total 7 files unless you're doing some nasty things in the content ones?
Nasty things, I suspect you'd say. A template system would be superior, but more complicated, and my impression was that DF would appreciate the simplest thing that could possibly work. Hence my suggestion of using one function per chunk of code.
The 7 files estimate was excluding the Makefile (don't see why you'd need a build script as well really), and equals N content files plus html.php.
Alexis
-
Alexis Lee -
MJ Ray