In this weeks episode of the Creatively Using the Creative Suite podcast we continue on the series from last week by putting together the bakground from episode 32 together with text and graphics to make the finished featured article.
In this weeks episode we go over designing a feature article background (with a nature theme) inside of Illustrator and finish off by adding some text in InDesign. You can watch it by selecting either version (low-res or HD) below, or by subscribing to either version in iTunes, iPod/iPhone or HD.
She Said: The thoughts of Elizabeth Gast!
It seems that lately the design world is largely based on the "most popular trends" of the moment. Currently we have: "glassy reflection", "glowing glitter", "grunge", "vector swirls", and "bright light in a dark room"; and if you can somehow manage to combine all of these smoothly into one image you can pretty much bet the image will make thousands of web-listings. Your popularity will be set – but only for the moment. Because let us not forget that trends come and go and what may be popular today, may just disappear tomorrow. Also usually, by the time a trend is about to fall off the design planet, it has been so overplayed that designers and public alike, will tend to turn green at the mere sight of it. Continue reading “To Trend or Not to Trend — That is the Question!” »
photo by TMAB2003
Perhaps the worst enemy for all of us when it comes to work and time is procrastination. You rarely want to do the things that you really need to do which winds up hurting you in the long run, either by stressing out or doing bad things. Lately though, I have found batch processing to help me get control of my life. Continue reading “Batch Processing – A Path Away from Procrastination” »
I’ve been reading more and more people who are really advocates for showing clients coded designs and never Photoshop/Fireworks files. Their biggest reason for this is the fonts. You can really never get accurate font preview in a Photoshop file as compared to the final web result. This is an argument that I fully buy. It’s pointless to try to show how a design will look with fonts in a web browser, but in a jpeg file instead.
The real main con, as I see it, with this method is that it is going to take a little more time. It does mainly depend on how fast of a coder you are. It’s so much simpler just to send of a jpeg file to a client with the design in, have them change their mind as usual and then code it. To me that seem like the most logical order (perhaps since I’m used to it by now), partly probably because I’m working faster in Photoshop than I code.
There is perhaps a mid-range option here. What you’ll do is that you do the design in Photoshop as usual, save out a jpeg file (with no fonts) and then just quickly place a floating, absolute div over the jpeg file, previewing how the fonts would look on your design.
I want to bring up just another bit as well; my personal experience with this. I must say I’ve yet to get a client that complains when they get their final version that it differed like the one I showed “before”. If most people know it is sample, or don’t care about the change, I don’t dare to speculate in just now but it gets me thinking if I really need to put that much energy into finding a solution to a thing that isn’t super broke.
In the end, my opinion about this on the whole, is that if you are a quick coder. By all means, do show clients a coded version if the coding for you is one of the heavy parts, then don’t. Showing the designs in a jpeg file seems to work and I’m not sure how much difference it would mean to clients if you showed the coded one.
Now, if Adobe would just get an option in the type tool to render the text as a web browser does, I’d be much happier…