I've read this: http://www.smashingmagazine.com/2011/06/23/a-web-developer-s-guide-to- adobe-indesign-2/ and I was confused. I always thought something like Photoshop was best for this kind of work. I create a banner img in InDesign and I could not figure out how to save for web and devices and optimize the design for web. Was I wrong to use InDesign? Should I stick to Photoshop for Web?
Export format JPEG or PNG. If you are using OSX this script will open layered ID pages as layered Photoshop pages:
See this thread for usage:
I love working with InDesign but to use it for anything like this is pretty much the same as driving nails with the back of a wrench instead of using a hammer.
It’s the wrong the tool for the job.
I guess it’s not as bad as designing a brochure in Photoshop.
Because Photoshop doesn't compose text as well or as easily as ID. A banner ad, (or web page wire frame design) could be all or mostly text.
I'd actually like to revisit this. InDesign is the absolute best page LAYOUT tool available. For comps, repurposing, Master Pages and, yes, styles, it actually makes perfect sense to DESIGN your webpages in ID. I simply cannot use PS for page layout. I've tried for years. And don't get me started on Fireworks.
I am not looking for ID to generate my code, so on that level I agree with Bob Levine that it's not the right tool for the job. But I *do* want to export my artwork accurately, and that's where it would be great if there were an easier way. Export to PSD does not retain layers (though I'm going to try that script linked above as soon as I finish this post!) and exporting to any image format leaves one with everything anti-aliased -- even square/rectangular boxes. Less than ideal. I really just want slices in ID and I'd be an extremely happy camper.
And, yes, it would be great for an export function to exist that allowed me to XML tag each item so that I could output the structure of the page and reference the styles already being used (or about to be used) on the main site. Then export the artwork and have a leg up on coding. As XML is all about the structure of the document, and XML functionality thoroughly permeates ID, it seems a logical next step to allow its functionality to be more than a niche "automate-your-bookmaking-in 90-complicated-steps" feature and mature into the fulcrum for proper web export.
Just my $0.02. Any opinions?
and exporting to any image format leaves one with everything anti-aliased -- even square/rectangular boxes.
The script does let you choose whether to anti-alias, but usually you want to check antialias and set rectangles on whole pixels in the layout so that things like text and curves get anti-aliased and rectangles don't