SiteGrinder outputs always valid XHTML 1.1 and CSS. It does not use tables for layout and no slicing is required.
The code is very light and very easy to edit. SiteGrinder maximizes re-use of CSS entries, as well as graphics. If a graphic repeats on a page, or repeats across different pages, SiteGrinder will make just one graphic file for it, not multiple. If a Photoshop layer is a solid color rectangle, SiteGrinder just outputs an HTML <div>, no graphic needed at all. When there are lots of overlapping non-interactive graphics, SiteGrinder automatically merges them together. The CSS is automatically organized such that shared elements appear in a file used by multiple pages. It's very slick.
Instead of slicing, you name your Photoshop layers for what role you want them to play in the final document (example: click me-button & click me-rollover ). These little words at the end of layer names are known as "hints". Most layers don't need a hint, but you'll typically use some.
Here are some video tutorials, most users start with these just to get the feel for it, though they are somewhat elementary: SiteGrinder Screen Movie Tutorials And, here is a full list of hints, which should give a sample of what it can do, although CSS borders, links, and many other things are done in the UI, not through hints: SiteGrinder Support complete_hint_list
Chris |
. 
I d/l the trial.
