You don't get templates in the sense of XHTML produced by web designers that you annotate afterward with a special markup. Instead, your page's rendering is defined in Smalltalk code. The downside is obvious but the advantage is that you use the same language and facilities (like refactoring tools, separate methods or components) to structure and manage your user interface.
The angle that Seaside is going for is that the software will emit the HTML, and the front-end people should be writing CSS and JavaScript to build applications.
Seaside is not a publication focused framework; the goal is to build web applications with it - so the emphasis is different.
I think markup generated programmatically is going lack readability and flexibility. I think for anything other than trivially simple interfaces, programmatically generating markup is going to be a bottleneck versus just marking it up and substituting variables. However, these are just opinions. That's why I'm not going to use this framework, it doesn't mean it's not right for other people.
...aaaand I click away from the page. A web framework without templates?