We tend to get a PDF that represents that web page. It's usually up to us to turn that into HTML. Since this HTML is then sliced up and component-ized, it becomes very cumbersome for an HTML designer to pull the pieces together in their environment. So, these days I only have separation concerns that address simple organization -- not work flow.
Most environments just aren't as simple and self-contained as what CountZero describes. I wish they were.
jeffa
L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)
In reply to Re^3: HTML::Template vs. Template::Toolkit vs. ??
by jeffa
in thread HTML::Template vs. Template::Toolkit vs. ??
by Rodster001
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |