Sep 052011
 

Over the long weekend I took the opportunity to tweak our WordPress blog, and mock up another for a client. While WordPress seems so easy to use, I’m starting to think that impression is a bit deceptive.

For one thing, I seem to find myself spending a lot of time activating and deactivating plugins, and installing and uninstalling various widgets and other add-ons. I’ve discovered that user ratings are very important. Even a quality plugin might not work exactly the way you expect it to. If you are lucky, this will only lead to some unexpected time spent scratching your head until you figure out the problem, or find an alternative. Worst case scenario(which does not seem all that infrequent), when something goes wrong, you may lose access to the platform altogether, and be faced with 404 pages, and figuring out what code is out of place over ftp.

The biggest issue seems to be quality. So this is fair warning: make sure you go with the highest quality you can find, and save yourself some headaches. That means highest quality add-ons, that are well-maintained and come highly recommended. It also means quality information. One issue I ran into: information about what you are trying to do(whatever it is)is all over the web, but it may not apply exactly to your situation. I mentioned that I was working on our blog and a mock-up. I thought, “there has to be a way to have more than one blog on the same domain.” I discovered WordPress Multisite. It seemed simple enough; a tweak here and there, a few lines of code, and I would be good to go.

Not so fast.

A couple of days and a downgrade, and complete second installation later, I knew better. What I learned from piecing together low-quality info from around the web is that a) there are a few more steps than at first glance, b) many of the steps are quite server specific, and the biggie, c) for some reason you can’t successfully convert blogs older than 30 days to multisite. Well, not for ‘some reason,’ rather some reason I don’t care to remember at this point.

Bottom line: save yourself time and headaches by finding the best quality information you can, know the steps to your project, and know the information necessary for your specific situation.

-James Andre

Aug 312011
 

 

 

Every website needs a favicon, if for no other reason than to avoid littering your server logs with 404 errors. If you still haven’t got a favicon on your site, check out Faviconist, a new favicon generator from developer Michael Mahemoff.

via Faviconist: Create Beautiful Favicons with HTML5 | Webmonkey | Wired.com.

Aug 302011
 

 

 

As more and more graphic designers and illustrators gain web design skills, illustrations can increasingly be found on the web. UK designer Mike Kus showcases his 10 favourite examples of websites using illustration to enhance the user experience.

via 10 beautiful examples of illustration on the web | Feature | .net magazine.

Aug 302011
 

 

 

Responsive design is no longer just something you’ll find on the portfolio websites of the designers and developers who pioneered the idea. These days using media queries to adapt to varying screen sizes is well on its way to being a mainstream design goal.

Head over to a responsive design showcase like Media Queries and you’ll find plenty of “real world” websites — like Opera or Arizona State University — using media queries to build responsive websites.

via Build Faster Mobile Websites with ‘Adaptive Images’ | Webmonkey | Wired.com.

Aug 252011
 

The word gradient has many different meanings, but in CSS, a gradient is strictly defined as a gradual transition between a range of (at least two) colours. CSS gradients are a fairly recent development but have already been through a number of changes. They were originally proposed by the WebKit team in April 2008, modified from the syntax proposed for the canvas element in HTML 5.

The W3C’s CSS Working Group later proposed a modified syntax, and this syntax is in the latest revisions of the Image Values Module. The first browser to implement this was Firefox 3.6, and the WebKit team weren’t far behind, so Safari 5.1 and above and recent versions of Chrome also use this syntax (The Book of CSS3 explains the old WebKit implementation fully).

via Master CSS gradients | Tutorial | .net magazine.

Aug 252011
 

 

 

According to jQuery support, training and consulting company appendTo, the popular open source library has now ‘overtaken’ Flash, in terms of how many websites have deployed each technology, at least when it comes to the world’s ‘top’ websites.

via jQuery overtakes Flash | News | .net magazine.

Aug 232011
 

As introduced/coined by Ethan Marcotte in both his article “Responsive Web Design” as well as his recently released book, one needs three elements to make a site responsive:

A flexible/fluid grid

Responsive images

Media queries

There are plenty of other great articles that cover motives, concepts, and techniques regarding responsive web design, so we’ll keep the focus of this article on some top tools that will help you become responsibly responsive.

via 21 top tools for responsive web design | Feature | .net magazine.

Jul 112011
 

 Ethan Marcotte coined the term responsive design to describe the process of using liquid layouts and media queries to scale websites so that they fit any screen size.

via Tips, Tricks and Best Practices for Responsive Design | Webmonkey | Wired.com.

Forget Photoshop, build your comps in the browser. It’s virtually impossible to mock up liquid layouts in Photoshop, start in the browser instead.

Scale images using img { max-width: 100%; }. For very large images, consider using something like Responsive Images to offer the very smallest screens smaller image downloads and then use JavaScript to swap in larger images for larger screen.