Donncha: WP Super Cache 0.9.9.7

WP Super Cache is a full page caching plugin for WordPress that makes your website run much faster!

I’ve just released a new version and the biggest change in this one is the addition of Content Delivery Network (CDN) support thanks to Mark Kubacki who allowed me to integrate his OSSDL CDN Off Linker plugin. (Please go visit his blog and say thank you if you use this feature!)

The CDN support simply rewrites images, CSS and Javascript files so they point at a different hostname. That hostname can be another virtual host on your own server (aka “Poor Man’s CDN”) pointing at your WordPress install or a fully fledged CDN. If your CDN supports “origin pull” then all the files on your server will be copied there as they are requested by visitors. Otherwise you’ll have to transfer the files over manually.

Apart from that, bugs have been fixed, a few features have been tweaked including the uninstall script which has been streamlined somewhat.

I also added links (on the “Easy” settngs page) to some plugins and tools you may find useful in making your site run faster.

Problems? Go to the forum and someone may already have had that problem and solved it. If not, post there and you’ll get a reply.

Related Posts

• WP Super Cache 0.8.4, the garbage collector
• WP Super Cache 0.8.7
• WP Super Cache 0.9.9

How to auto suspend expired account ?

/scripts/chpass and MySQL password

Mod_rewrite no so good

Take the WordPress Users Survey, win over $3,000 in prizes

Today we’re happy to announce the 2010 WPCandy WordPress Users Survey, as well as a WordPress giveaway valued at over $3,000.

WordPress is used every day by bloggers and professionals all over the world—but how and what for? Just who is using WordPress? This survey aims to compile survey data on these sorts of questions into a report for the benefit of the community.

By participating in this quick WordPress Users Survey, you will get three things:

• Access to the final survey report in January. Just make sure you include your email with the survey. It will only be used for the one-time email delivering you the survey report.
• Entered to win a $3,000 grand prize. More on this below.
• The satisfaction of contributing to a community-driven endeavor that will benefit everyone. Also know as the feel-goods.

The survey will be available through December, and the final report will be created in January. Take the 2010 WPCandy WordPress Users Survey today!

Take the survey for a chance at over $3,000 in WordPress prizes

Such a project just wouldn’t be as much fun without a massive giveaway, right? That’s what we thought.

We’re very thankful to have so many supportive sponsors who have generously donated items for this giveaway. But let’s get right to it; the giveaway items are (in no particular order):

• 1 copy of Headway, from Headway Themes
• 1 copy of Startbox and 1 child theme (winner’s choice), from WPStartbox.com
• 1 copy of Builder, from iThemes
• 1 copy of BackupBuddy, from PluginBuddy
• 1 year membership at WebDesign.com
• 1 year Developer Subscription at WooThemes
• 1 standard license of Standard Theme
• 1 standard license of Live Theme
• 5 themes (winner’s choice) from Themify
• 1 copy of Relay, new from Press75
• 1 copy of Enterprise, from StudioPress
• 1 copy of Traction, from The Theme Foundry
• 3 themes (winner’s choice) from Gabfire
• 1 copy of Elemental, from Pro Theme Design
• 1 year membership at Themeopoly
• 1 Lifetime Theme Developer Membership at Dev4Press
• 1 Lifetime Plugin Bundle Development Membership at Dev4Press
• 1 year membership at FlexiThemes
• 3 themes (winner’s choice) at Gorilla Themes
• 1 theme (winner’s choice) at ThemeJam
• 1 copy of Gravity Forms

Yes, one winner will be chosen from the survey participants to win the list of prizes you just read.

Will it be you?

Other ways to enter

You can also be entered to win up to two more times (in addition to taking the survey). To be entered again, you can:

• Tweet about the survey using the #wpcandy hashtag.
• Blog about it, linking back to this post or the survey itself.

We’re very excited about this survey, and think it can provide some valuable insight into how WordPress is used all over the world. The more we can spread the word, the better!

Take the 2010 WPCandy WordPress Users Survey today!

Xmarks Lives: LastPass Buys Downtrodden Bookmark Syncing Service

Just when we all thought we’d never see it again, the cross-browser bookmark syncing service Xmarks has received a life-saving injection.

The company has been acquired by LastPass, maker of a cross-browser password manager and form filler add-on. The deal was announced Thursday, and terms were not disclosed.

Xmarks will live on as a freemium service. The initial cross-browser syncing tool you’re already familiar with will be free, but users will be encouraged to upgrade to a paid subscription to unlock more advanced features. It’s the same model employed by LastPass for its own Premium version of its (otherwise free) password-syncing service.

Xmarks Premium will be offered for $1 per month ($12 per year) and it comes with some new features like apps for the iPhone and Android phones, and technical support. You will also be able to bundle the premium offerings from LastPass and Xmarks together for $20 per year.

There’s already an iPhone app for Xmarks, and the company just recently released an Android app, too. Xmarks says anyone currently using the iPhone app can continue to use it without upgrading to the premium service, but they will have to buy in to the $12 per year plan to get future upgrades.

It looked like curtains for Xmarks in September, when the company announced it would shut down its service in early 2011.

Apparently, there’s no money in a free bookmark syncing service, and the company was facing new competition from the cloud-based syncing systems being built into Firefox and Chrome. Even though Xmarks one-ups those built-in single-browser services by syncing bookmarks across all your browsers, it couldn’t stay afloat.

The service has some 4.5 million users, and there was an outcry when Xmarks announced the shutdown. Later, the company asked its fans if they would be willing to pay a subscription fee to keep Xmarks alive. Over 30,000 of them pledged to do so, and that was enough to attract the attention of LastPass.

The two companies will continue to operate under independent brands, though they may merge everything later.

So, it turns out this dark story of cloud computing had a silver lining after all.

See also:

• Xmarks to Continue Syncing Bookmarks, Thanks to Loyal Fans
• Xmarks Mulls Switch to Premium Service
• Popular Bookmark Syncing Tool XMarks to Shut Down
• Xmarks Syncs Open Tabs Across Browsers, iPhone

Chrome Browser to Start Sandboxing Flash Player

The latest developer channel release of the Chrome browser now supports sandboxing for Adobe’s Flash Player on Windows 7, Vista and XP.

This feature should provide extra protection against malicious browser exploits through the Flash Player. The dev channel releases of Chrome on Windows already support sandboxing for HTML rendering and JavaScript execution, two of the most common paths people can use to run malicious code on an unsuspecting user’s machine. Sandboxing keeps these sensitive parts of the browser more secure while still allowing web pages and apps to access the other, less-sensitive parts of the browser.

Windows users on the dev channel should see the update arrive automatically. We should note that the sandbox does have some bugs and may break other parts of the browser — this is a developer release, after all. Once the kinks are ironed out, all of these sandboxing features will begin making their way into proper stable Chrome releases.

Google’s Chromium team has been working with Adobe to build better Flash controls into Chrome, and to utilize Chrome’s sandboxing technology for the plug-in. Google says Wednesday’s update makes Chrome the only browser on XP that sandboxes Flash. For more about sandboxing and how Chrome is implementing it, read the overview post on the Chromium blog from October. Also, Wednesday’s release comes less than a month after Chrome introduced click-to-play controls for Flash and other plug-ins.

Adobe’s Flash Player is the most widely-used browser plug-in on the web, and it’s the dominant choice for video playback and games online. Even so, the technology gets beat up for performance issues and its security shortcomings, and it’s still falling out of favor among standards enthusiasts who are pushing HTML5 as the better solution for displaying multimedia in the browser.

Adobe also released a new beta version of the Flash Player on Wednesday that improves some of its performance issues.

See also:

• New Flash Player 10.2 Goes Easy on the CPU
• Chrome Now Offers Click-to-Play Option for Flash, Other Plugins
• Chrome 7 Arrives With Bug Fixes, Better HTML5 Support

Can WAI-ARIA Build a More Accessible Web?

Accessibility in web design has come a long way since the days of table-based layouts with single-pixel .gif spacers. But even current best practices are far from perfect.

Today, we’ll tell you a bit more about these accessibility troubles as they relate to dynamic web apps — fitting, as today is Blue Beanie Day. For four years now, design guru Jeffrey Zeldman has encouraged web authors to wear a blue beanie on November 30 to show their support for web standards. Also, you’re encouraged to take a picture of yourself wearing a blue beanie and upload it to a Flickr pool. So, with standards quite literally on the brain, we’ll tackle the topic of rich web apps.

One of the coolest things about web apps is that elements refresh inside the browser without reloading the page. But most screen readers used by those with disabilities can’t parse these changes, so users who rely on them will remain unaware of any dynamically refreshed elements on the page. That’s just one of the many problems that WAI-ARIA, an emerging specification for Accessible Rich Internet Applications from the W3C, is hoping to solve.

At its core, WAI-ARIA is a means of annotating page elements with the roles, properties, and states that define exactly what those elements do. Take a navigation element as a simple example. In HTML5 we might do something like this:

<nav>
    <ul>
        <li>Home

        <li><a href="/about/">About</a></li>
        ...etc...
    </ul>
</nav>

While it might seem that the

tag would defining the nav element’s “role,” not every browser will understand it (just because the browser can display it, does not mean it understands the tag). Also, the purpose of a navigation element may be obvious to most users, but to a screen reader being used by somebody who can’t see, the navigation strip could be just a jumble of words. Leveraging WAI-ARIA’s syntax, we can double up to ensure screen readers will know that this chunk of code is navigation:

<nav role="navigation">
    <ul>
        <li>Home</li>
        <li><a href="/about/">About</a></li>
        ...etc...
    </ul>
</nav>

The

attribute is what’s known as a landmark role and is designed to let non-visual browsers know where they are.

It seems simple, and indeed when the spec is finished and fully supported by all the major screen readers, WAI-ARIA promises to make the web more accessible without overly complicating your markup. Unfortunately, there are numerous problems with WAI-ARIA at the moment, which make support uneven and can be confusing for web authors trying to do the right thing.

Our friends at A List Apart recently waded into the confusion and uneven support with two great posts on WAI-ARIA and how you can use it (and not use it) on your sites. The first article, The Accessibility of WAI-ARIA, dives into what WAI-ARIA is, what it’s trying to do, and why it’s not yet a panacea.

The second piece is more hands-on. ARIA and Progressive Enhancement looks at how ARIA fits within the progressive enhancement approach to web design. That is, when starting with valid HTML and enhancing it with CSS and JavaScript, how can you also work the WAI-ARIA attributes into your code?

The ARIA and Progressive Enhancement article also has a very informative table listing the varying levels of support in the latest versions of popular screen readers. Unfortunately, one of the main problems with WAI-ARIA today is that there’s no way to know the level of support a user agent has. Unlike CSS or JavaScript, there’s no reliable way to test which features a user agent supports (if any).

As Derek Featherstone writes in his ALA piece:

The problem that we have right now is that ARIA is an all or nothing deal. And writing scripts that respect both an ARIA supported methodology and a non-ARIA methodology is going to be incredibly difficult, because we have no reliable way of knowing the status of a user agent’s support for ARIA—it depends on something we can’t detect: the right combination of browser, assistive technology, and full ARIA implementation.

For more information on the various levels of support in screen readers and web browsers, have a look at Accessible Culture’s article, HTML5 plus ARIA “Sanity Check.” The post highlights some of the bugs, pitfalls and gotchas in current screen readers, as well as some workarounds and other non-ARIA solutions.

As Detlev Fischer writes in the first of the two ALA articles, “as long as older screen reader/browser combinations incapable of interpreting WAI-ARIA still constitute a significant part of the installed base, web designers who care for accessibility should use WAI-ARIA markup only to enrich their sites.”

In other words, use WAI-ARIA, but don’t rely on it. Make sure you have fallbacks in place until the spec is finalized and browser/reader support more widespread.

Unicorn photo from Wikimedia Commons/CC

See Also:

• Microdata: HTML5’s Best-Kept Secret
• W3C’s Unicorn Validator Checks Multiple Standards at Once
• Using Microformats in HTML5
• Add Semantic Value to Your Pages With HTML 5

Transparent CSS Sprites

One of the most useful front-end development techniques of recent years is the humble “CSS Sprites”. The technique was popularised by Dave Shea on A List Apart in 2004 with his article CSS Sprites: Image Slicing’s Kiss of Death. CSS Sprites are a relatively simple technique once you understand the fundamentals and it can be applied in all manner of ways. A common use is for a graphic intensive navigation, but it can also be useful for buttons or even styling headings with the corporate font.

Sprites are simply a collection of images which are merged together to create a single file. You then use CSS, changing the

the image, to display the correct part of the image you need. I often use the analogy of a large object passing a window — you only see what is within the frame.

Over the last couple of years CSS Sprites has been one of the most widely adopted CSS-related techniques. Popularised by the Yahoo’s research and documentation around speeding up your website, many high profile websites implement the technique, including Google and Amazon. There are numerous tutorials which help you get to grips with the techniques and sprite generators which help you create the graphics themselves.

The Benefits and Potential Problems

CSS Sprites have become a de-facto way of improving the speed of your website or web application. Merging multiple images in to a single file can quickly reduce the number of HTTP requests needed on a typical website. Most browsers only allow for two concurrent connections to a single domain so although individual files can be large, the overall request and response times are considerably lower. Combining images with similar hues also means the colour and compression information is only need once, instead of per file, which can mean an overall reduced file size when compared to the files individually.

The benefits of reduced file size and HTTP requests are often publicised, but potential problems are rarely ever discussed. One of the main techinical issues with CSS Sprites is memory usage which is explained in the article “To Sprite Or Not To Sprite”. Another issue is the maintenance of the sprites, the images and the CSS, both of which can become rather complicated.

A Technological Solution

A common practice in solving slow-down in computing seems to simply throw in more hardware. We all know hardware prices are dropping all the time, so this seems like a reasonable solution. However, I feel there is a fundamental flaw with this philosophy and ingrained mentality. Developers have access to more computing power and as such they code their applications to be handled in these environments. With each new feature the application becomes slower and slower, but this problem has already has a solution — upgrade your hardware. This is an endless cycle.

Many of the user interfaces people come across today are on the Web. This means the user has to download most of the related material (images, CSS, JavaScript) before interacting with the content, so the same philosophy must be applied to the Web. Websites, or more recently web applications, are becoming more complex, even replacing many desktop applications, therefore the user must first download more and more information before beginning their experience.

Although file sizes required to view a website have increased dramatically over recent years, more and more people are upgrading their Internet connections, with broadband becoming the norm in many countries. This cycle conforms to the hardware upgrade philosophy and in theory should negate any potential user experience problems.

However, web developers are falling in to the same trap which many application developers have before. As layouts become more complex, more images are required and so the developer creates more images — even if they are sprites. This seems like a reasonable assertion, but it doesn’t mean it is the best solution.

A Twist on the Technique

Due to the limitations of the Web, there have been many inventive solutions to problems. But the Web isn’t the only place where there can be very tight limitations. Innovation strives on limitation. A great example of this was in the iconic game Super Mario Brothers where the bushes were just recoloured clouds.

This very simple but extremely effective implementation made me think about how to reuse common interface elements, trick the user to believe something the same is different!

Now on to the twist, this idea is to create a transparent sprite allowing the

to show through. If you are familiar with CSS Sprites, you should be able to grasp this twist relatively easily.

Simply, an image with a transparent “knocked-out” transparent center is placed over a background colour. Changing the background colour changes the appearance of the element. The only thing you need to pay attention to is that the colour surrounding the transparent part of the image matches the background in which you are using the techinque. This stops the background colour bleeding in to other parts of your image.

Anyway, this technique is much easier to understand in an example…

Example

The following example is only made up of three images. One for all the font samples, one image for both sets of droplets, including hover and active states, and one for the all buttons.

The Images

Fonts
The font image contains transparent typefaces on a white background, meaning they aren’t viewable on a white background. Save the file from the example, open it in your favourite graphics editor and you will see the transparent typefaces.

Drops
The drops image is used on the example above as the colour picker. A single graphic containing the gradient drop on the two different backgrounds, so the

is masked out correctly. The image contains all three states used in modern interactive interfaces — static, hover/focus, pressed/active.

Button
The button technique is the most flexible and probably most useful way to use this technique. A simple sprite image containing two states — static and hover/focus — which is then placed over text to create the button. Simply adding a

will make every use of this button the same style across your application or website.

Below is some CSS which styles simple fixed width buttons with a grey background colour, but also has two different treatments, “warning” and “go”, which have red and green background colours respectively.

a.button {
  display: block;
  width: 80px; height: 30px;
  margin: 0 20px;
  font-size: 14px; line-height: 30px; color: #fff;
  text-align: center; text-decoration: none;
  background: #4a4a4a url(button.png) no-repeat 0 0;
}
a.button:hover,
a.button:focus,
a.button:active {
  background-position: 0 -40px;
}
a.button.warning {
  background-color: #ea1d22;
}
a.button.go {
  background-color: #309721;
}

The CSS above produces the following buttons:

• Normal
• Button
• Continue
• Go!
• Stop!

Conclusion

This techinque could be useful when providing a range of themes for a website. You could create one set of buttons and icons then add the background colour which best suits the selected theme.

Although this technique will never be as broadly useful as the original CSS Sprites, the idea can be useful for websites which allow user theming. The technique could also be used when creating HTML mockups, allowing you to easily update colours based on client feedback.

The main benefit this technique has is that it reduces the number of HTTP requests. But it also reduces browser memory usage compared with what would be needed if you created a larger sprite to handle all the colours you need.

I would like to mention one caveat though, IE6, because it does not natively support transparent PNGs. There are PNG fixes, but none¹ of these support

which is needed if you are using this technique with CSS sprites, such as with the buttons and droplets above. However, you could provide a slightly less optimal experience using GIFs instead.

1. The IE PNG Fix from TwinHelix does include support for

, but the solution requires JavaScript.

Further Resources

If you are interested in any aspect of CSS Sprites, check out the following extra resources.

• Fast Rollovers Without Preload – the initial inspiration for CSS Sprites.
• SpriteMe – a bookmarklet to generate sprites based on an existing website.

Below are a list of links used within the article:

• CSS Sprites: Image Slicing’s Kiss of Death – the A List Apart article by Dave Shea.
• Yahoo! Performance Guideliness – best practices, tools and research from Yahoo!
• CSS Sprite Generator – a tool to help you create your sprites by Ed Eliot.
• To Sprite Or Not To Sprite – an article about some potential system performance caveats with sprites.

© Trevor Morris for Smashing Magazine, 2010. | Permalink | Post a comment | Add to del.icio.us | Digg this | Stumble on StumbleUpon! | Tweet it! | Submit to Reddit | Forum Smashing Magazine
Post tags: CSS

Take The Initiative and Create Your Own Projects

During my last job with a large corporation, people started to get laid off. Many fellow creatives came to me, as they had no idea what they would do if they were let go. I had come to that small city from New York and my experience was varied and impressive to those who started their careers with this company. Their parents had hoped for their own children to work there and eventually retire in the same homey place. They were anchored in this town that held no other industries. Like layoffs in a town that has a steel mill, there weren’t many options to those looking for work.

“You’re creative,” I would tell people before my turn came in the next to last round of layoffs (which is some comfort). “You can do so many things that are creative. If you get pushed out the door, make your own projects!” Then advise them where to go and spend the rest of the day creating a book, or painting a series for a gallery show, or create postcards, greeting cards, dolls and websites. This was usually followed by the persons to whom I was speaking to, to ask about something they obviously wanted to explore; leading to a discussion, usually joined by others as well, on how to achieve it. The dividing line is how badly does one want it?

Take The Initiative!

Tailor (A) gives creative (B) a snappy new “power suit”, SO irresistible that the client (C) hugs the suit (D) causing it to hit paddle (E), smashing expensive vase (G) and wasting a perfectly goof head of cabbage (I). Further destruction reigns havoc (K – P), dousing all competitors with a toxic chemical (Q). Illustration by Rube Goldberg.

I’m a big believer in self-propelled initiatives. It’s how I make a living. Writing for Smashing Magazine is an initiative. Everything is done before Smashing ever sees it. Authors have to come up with the idea, research it for presentation, get the approval and then write it and submit it. It’s initiative. As with what you may perceive as easy to pitch an article, most initiatives are simple!

All of my career I’ve had people come to me to relay that they have written a book and need a cover or images for the inside so they can send it to a publisher. I tell them they don’t need all that. Just send in the manuscript with a self-addressed-stamped-envelope (many publishers have digital submissions on their sites) and the publisher will choose cover designers and illustrators themselves.

Some people smile at the realization that their dreams were an easy step closer. Some didn’t believe me and insisted I design something for them (and draw, because I’m an “artsy-type!”). I look over the pages and tell them it’s an idea that shouldn’t be “set aside lightly”. They smile and then I tell them it should be “thrown with great force” (with apologies to Dorothy Parker). Some people want it to be done for them. Maybe it’s the prompting of a contest or a “might-as-well-take-it” project.

Would you rather be working on a low-paying project that is screwing you up at every turn or invest in yourself with the time put towards your dream project? It’s not hard coming up with an idea and creating the images, code or what-have-you. The difficult part is making yourself do it and then selling it and that’s where most people fail.

One of my recent favorite self-initiative stories was about an injured creative with time on his hands and a need for income. Dave is a designer at the Iconfactory and responsible for the ultimate Twitter icon Ollie the Twitterrific bird; he had broke his foot while playing soccer over the Fourth of July. That meant that the poor guy was relegated to staying off his feet at home. Rather than wallow in self-pity, he decided to use the opportunity to keep himself from going completely Rear Window and offer up his design skills to the large Web community — and successfully so!

Self-initiative is not easy for most people. Working for someone else provides a regular paycheck, security, after a fashion, and someone telling you what to do. No self-motivational projects needed. As one person commented on a past article on crowdsourcing,

“I recently participated in the LG “Design the Future” contest (yeah, I didn’t win)… but rarely do I get the chance to design a cell phone like product… it was a great exercise in creativity and it really let me flex my muscle… and they had some substantial cash prices (first prize was $20,000)… I feel like competitions like that are great for the industry. The rules were pretty relaxed and it really let people go hog wild and show off what they can do. Too often you’re forced to roll with the clients vision. It’s great to have a contest that let’s you be you.”

As I was arguing the pros and cons of crowdsourcing in that article, I just had to reply for his edification:

“I understand your point, but let me play devil’s advocate and explore another option. So you submitted something you really enjoyed designing and it stretched your creativity. You loved your final submission. You didn’t win and the client, I assume, owns it anyway. What if you had designed it but not submitted it and then sought out companies that might purchase the rights to the design? You would have taken a cue to create your own initiative and owned the product rights.”

Was the prize worth giving away all rights to the winner? What would the client have paid a design firm or freelancer to do the work? I’m guessing that the prize cost was considerably less than the one that would have run the company. So, who was the real winner? Which avenue held a better chance for him? The odds of him winning the contest and giving up the idea anyway without winning, or the odds of him being able to sell the design on the open market, or  maybe not, but owning it to try again? I can’t say.

Persistence in selling the idea and protecting it can be daunting. Even though, sometimes even an e-mail comes back right away that says, “I love it!”… and a check eventually arrives. (Note: you shouldn’t participate in such speculative design work as a professional in the first place and here is why — Smashing Editorial)

What Will Get You Started?

A tidal wave of ideas or bills (A) will motivate another creative nearby to foolishly open an umbrella (E) in a lame attempt to hold back the flood, causing what looks like a giant earring (H) to fall and pull the hammer (J) so it strikes a piece of metal (K), waking up the baby (L) who must be rocked to sleep (N) by a trained and poorly-paid dog (M), causing the attached backscratcher (O) to tear at your flesh until you decide it’s better to get off your rear and do something. Illustration by Rube Goldberg.

Your idea. Your dream. No one will do it for you. Even if you have to work at something non-creative — use the money to live, but make your dream the priority. Crappy job gets in the way of your dream? Find another crappy job! They’re everywhere and except for the slaughterhouse idea, they won’t drain your creativity. Have the idea? Now set your plan. Just like your previous boss who had always made projects go around and around, it’s finally time to make your own plan, knowing it will work better, and make it happen!

First, research who your customer is. Using Web sources or going to stores are the best way to find out some helpful examples of consumer habits (yes, marketing people never leave the office, they rely too much on figures supplied to them). See what people are buying and talk to them. I used to go to stores that carried products made by the company for which I worked for, and watched what people bought or didn’t and asked them why.

I would smile as I approached them, excuse myself and explain what I was working on and gathered their opinions. This is probably why my products sometimes sold very well. Know your consumer base!

Also, figure out costs and how you will cover them. You may need a loan or investors. What website and functionality will you need? Packaging, having stock, shipping, advertising, taxes? Is your dream project for you to start a business or do you want someone else to produce it? If you are producing it yourself, you can get a business loan, but you are about to take many, many risks. Get legal and financial advice next. It’s well worth the money and will give you the final tally of whether or not this will be your dream or nightmare.

If you are creating something to pitch to a company for their purchase or licensing a property (certain photos for calendars and cards, for instance), there are a similar but different set of rules.

Start with the idea and marketing, create a style guide and/or presentation. A friend of mine wanted to publish a graphic novel for a pitch for a property she was trying to sell but couldn’t afford upfront fees for an artist and writer and printer, so I told her to use a WordPress blog to post her promotional material that she already had and that would give her a great presentation — the easy way.

Research which company you think would want to take on the project. Again, go online or to a store and look around. Want to really impress potential clients? Ask the store’s permission to set everything up; take videos of shoppers and their answers. What better way to produce proof of a need and then give clients the means to fulfill it!? Let your imagination run wild! As with the man who was so excited by the contest he entered, stretch yourself creatively.

Found the perfect prospect? Do your research and find the people you need to reach. There are many business networking sites. Search the company and find people and their titles. Get addresses and phone numbers. Call the receptionist and ask her/him who is the head of marketing or if they have an R & D contact person. If they don’t know, ask to speak to the secretary of the VP of marketing. Maybe she/he can get you closer. Also, use your network. Do any of your contacts know someone you are trying to reach?

Sounds difficult? It isn’t really; just keep in mind that it takes a lot of persistence, patience, as well as a good sense of humor. Once you lost one of those, you won’t make it.

A Non-Disclosure Agreement Is Standard

While feeding yourself (A), the spoon pulls the string (B), flipping a piece of drilled iron into the head of a parrot (E), who is knocked unconscious and knocks it’s beak into a bowl (G) which spills parrot food into a bucket (H) that sets of fireworks (K) inside your house with a razor sharp sickle (L) attached to it, cutting the string (M) and forcing you to remember the paperwork to enforce your rights by smacking you in the face with a contract repeatedly! Illustration by Rube Goldberg.

It’s standard to either have your own Non-Disclosure Agreement or pick up a copy of Tad Crawford’s book on contracts and forms. Bigger companies will insist on using their own. Bigger corporations, to their own detriment, usually have no access point for outside ideas. They are afraid your idea may be something they are working on and they will be sued down the line. Middle-sized companies will just tell you they happen to be working on the same idea. Document your contacts and submissions well.

I was recently told over a dozen product designs would not be used. I later heard the products were available in every catalog world-wide. Did they think my price would go up if I found out how well the work did? You bet it will! Keep your expectations high (expect the middle to low high) when negotiating. A recent question came in from an artist in Mexico who ran across a sleazy representative in the United States who was basically ripping her off for one of her licensed characters. She had jumped at the chance because it was her first time working in a licensing arrangement. I hope she followed my advice.

As with any business transaction… think! Anyone who rushes your decision is up to something. Do your research and see what you find.

Bless The Web And All Who Surf It!

Extended and dangerous hook (A) catches old fashion sign (B), causing electrical shorts that start a fire and the boot to swing back, kicking the football (C) over the goal post (D) and into a colander (E) which tips the watering can (G) to soak the creative’s back, pants and shoes, which will lead to misunderstandings and new nicknames. The string (I) pulls open the cage (J) allowing the bird (K) to go to eat the worm (M), as the bird had been starved in retaliation for all the Twitter fails, causing the shade to be pulled down (N), which reminds the creative to mail that proposal in his pocket. Using theiWeb only takes half the steps. Illustration by Rube Goldberg.

The Web holds a billion of possibilities. As I mentioned about my friend who built a blog, rather then going through the costs of print, you can hardly lose with a great idea and the ability to bring it to life on the Web. With e-commerce made so easy, how can you not have a site that sells something? At least most of the people I know have a Cafepress or Zazzle “shop”.

When I first started with web design, back in the days when processors ran on mud and sticks… and fire, which was new, I put up sites for my infamous chili recipe, one for each of my kids, a site for toy collectors, and it went on. Why? The Web was young and there were probably only 73 sites live and forty of them were mine!

Use your down time. Partner with friends and split the rewards. Ever hear of a group of social outcasts who got together and created something called “The Onion?” No? I haven’t either, but I do hear good things and that they crawled their way up to be, I believe, the number one humor site in the world. It must have started with an idea and someone’s dream.

(ik) (vf)

© Speider Schneider for Smashing Magazine, 2010. | Permalink | Post a comment | Add to del.icio.us | Digg this | Stumble on StumbleUpon! | Tweet it! | Submit to Reddit | Forum Smashing Magazine
Post tags: creative, initiative, projects, spec