Pages

Subscribe:

Ads 468x60px

Labels

Labels

Unordered List

Ordered List

Sunday, 15 November 2015

Popular design news of the week: November 9, 2015 – November 15, 2015

Every week users submit a lot of interesting stuff on our sister site Webdesigner News, highlighting great content from around the web that can be of interest to web designers. 

The best way to keep track of all the great stories and news being posted is simply to check out the Webdesigner News site, however, in case you missed some here’s a quick and useful compilation of the most popular designer news that we curated from the past week.

Note that this is only a very small selection of the links that were posted, so don’t miss out and subscribe to our newsletter and follow the site daily for all the news.

15 Reasons Why a Grid Based Approach will Improve your Designs

Filter Blend – CSS Blend Modes and Filters Playground

Lomography Effect Using CSS

CSS-only Colorful Calendar Concept

5 Web Design Takeaways from 2015

Google Launches New Search Results Interface for Tablets

How Apple is Giving Design a Bad Name

I Thought the Amazon Store was a Terrible Idea. Then I Actually Went There…

Squire – The Pen is a Mighty Sword

The Problem with Being a “UX Designer”

Are You Getting Cheated When Buying a WordPress Theme?

Dropsource – Build a Native App with the Dropsource Drag and Drop Editor

How to Design a Website with Emotional Impact

Why Designers Can’t Stop Reinventing the Subway Map

Why You Should Want to Be a User Experience Developer

Refactor.io – Share, Review, and Learn Best Code Practices

F.lux – Auto Adjust iOS Based on the Time of Day

ProShot – Turn your iPhone 6/6s into a GoPro!

Pantone Smoothies

No UI is the New UI

Gmail, We Need To Talk

Firefox for iOS Released

Misused Mobile UX Patterns

What are the Real Merits of Material Design?

Gill Sans is Reborn for the Digital Age

Want more? No problem! Keep track of top design news from around the web with Webdesigner News.

Lifetime Access to ALL WordPress + HTML Themes from TeslaThemes – only $65!

Source

si pide pass es: Cameron Chapman

Saturday, 14 November 2015

Comics of the week #313

Every week we feature a set of comics created exclusively for WDD.

The content revolves around web design, blogging and funny situations that we encounter in our daily lives as designers.

These great cartoons are created by Jerry King, an award-winning cartoonist who’s one of the most published, prolific and versatile cartoonists in the world today.

So for a few moments, take a break from your daily routine, have a laugh and enjoy these funny cartoons.

Feel free to leave your comments and suggestions below as well as any related stories of your own…

Royal email

 

Arms talks

 

Just don’t look behind the curtain

Can you relate to these situations? Please share your funny stories and comments below…

Get Ready for Winter with the Snow Text Generator – only $7!

Source

si pide pass es: Jerry King

Friday, 13 November 2015

The New Republic launches mobile-centric redesign

To mark its 101st birthday this month, and following on from a redesign of its print version this Summer, America’s oldest liberal political magazine, The New Republic has launched a redesigned website.

TNR reaches over 7 million readers each month, via newrepublic.com, and across social media. And whilst its readers are typically thought of as older, over 4 million of its online readers are aged under 45; more than 2 million access the site exclusively on smartphones.

So it makes sense that TNR’s redesign takes a largely mobile-first approach: panels, adverts, and even navigation have been stripped out for a streamlined reading process; it’s so minimal it might even be called sparse.

We’ve historically appealed to a pretty traditional demographic, but we’re now making a concerted effort to reach out to a much younger and diverse group of people…and the data says those people are more likely to read our site on mobile phones. — Chris Hughes, The New Republic

The main navigation on the new TNR is infinite scrolling; when you reach the bottom of an article, the next article loads, mimicking the continuous reading of a social media news feed; perhaps not surprising as TNR’s main shareholder since 2012 has been Chris Hughes, co-founder of Facebook.

All other navigation has been hidden away behind a hamburger menu, not just on mobile, but desktop as well. It’s an assumption — albeit a popular one — that younger users recognize a hamburger menu, and it certainly alienates less experienced users. The usability of hamburger menus is a contentious issue, but they demonstrably obscure the available options for users; hamburger menus are always mystery meat navigation.

In the case of TNR, the hamburger menu has been used because they had to use something. It feels very much as if it’s been slapped on the desktop because it had already been designed for the mobile version. Concealing items like ‘Advertise’, ‘Contact’, and ‘Jobs’ is one thing; hiding major content sections like ‘Politics’, ‘Culture’, and vitally the ‘Subscribe’ link is another. Even the search function — which many users turn to as a primary navigation tool — has been hidden away.

Where the TNR redesign does work is its focus on content. The designers have approximated the typography of the print version, with both display and body text using Lava, and info text using Balto.

The site has received a significant speed boost, by dropping Drupal, and replacing it with a custom-CMS. And the frontend feels crisp and responsive having been built with ReactJS.

The big problem with the TNR redesign, isn’t so much that it’s mobile-first, as mobile-only. Whilst desktop browsing may be on the decline, a desktop is not simply a big smartphone, and just as ignoring mobile five years ago cost you 20% of your audience, ignoring desktop now will cost in excess of 40%.

 

Images use device mockups image, via Shutterstock.

Winter Collection of 100+ Graphic Elements – only $7.50!

Source

si pide pass es: Benjie Moss

Free download: 49 free promo backdrops and gradients

Created by LA-based designer, Vladimir Kudinov, Hue is a collection of 49 backdrops and gradients that lend atmosphere to layouts and product shots.

The collection is photo-realistic, blending seamlessly with product photographs; and reminiscent of Scandinavian design, with cool greys and warm pastels dominating. The atmospheric Wolverine, the stylish Golden Leaf, and the calm Milky Way are particular favourites.

Designed for use in Sketch, the files are supplied as a .sketch file; however 2800px by 2000px PNG files are also provided for each gradient, so Photoshop and Affinity Photo devotees will find them equally usable.

The Hue collection is free for both personal and commercial use. Download the files beneath the preview:

Please enter your email address below and click the download button. The download link will be sent to you by email, or if you have already subscribed, the download will begin immediately.

Winter Collection of 100+ Graphic Elements – only $7.50!

Source

si pide pass es: WebdesignerDepot Staff

Thursday, 12 November 2015

Dynamic sites at static speed: the art of website caching

A lot has been said recently about the merits of static sites. But in many situations a dynamic approach is a necessity. Whether a content management system, a customer relationship tool, or online store, they allow end users to maintain complex sites quickly and consistently. And when put together properly, they can rival static-sites for speed.

any application that needs to frequently read and write data will cause a noticeable delay

Whatever system you use, dynamic sites typically comprise of similar elements. These are a form of web server, a backend and an application, written in one or more programming languages. This combination of components give a great deal of flexibility, but each contributes its own overhead and increases load time, something all modern web sites want to avoid. This is especially true with database access;any application that needs to frequently read and write data will cause a noticeable delay.

This where caching and an appropriate caching strategy for your use case will help. The basic aim of caching is to prevent unnecessarily frequent calls between the application database layers and instead use pre-generated static HTML pages, which are much faster to render in a browser.

Browser caching

The first cache that any web user would have noticed is the cache in their browser. How many times have developers asked you to undertake a “force-refresh” to see changes? Browser caches are simple but a good starting point to begin explaining caching concepts. A browser stores representations of web pages visited on a user’s computer, typically updating them once per session if changes are detected or forced by the site.

Proxy caching

A common tool employed by site owners and administrators is a ‘reverse proxy cache’ that sits between page requests made by a web browser and the web application. It intercepts requests and renders copies of pages straight from the cache, thus providing a noticeable speed boost.

There are several major proxy cache options available for self-install or as ‘Software as a Service’. (We are ignoring cloud hosting providers who typically package everything you might need into a self-contained web stack.)

Popular proxy cache options include:

SaaS options for caching generally lie in the world of Content Delivery Networks (CDNs) which instead of placing a cache between a user and a web stack, serve users sets of cached content that are geographically closest to them. It’s a subtle difference, but one that for large sites with global audiences can make a significant difference.

Using Varnish

Varnish is available in all Linux package managers, as a Docker image and many other options, read the project’s installation page for more details.

Basic Varnish configuration

Varnish stores a default configuration file either at /usr/local/etc/varnish/default.vcl or /etc/varnish/default.vcl, written in VCL (Varnish Configuration Language). This configuration file gets compiled into a small program via a C interpreter to boost speed even more.

Depending how you installed Varnish, the configuration file will look something like this:

backend default { 
    .host = "127.0.0.1"; 
    .port = "8000"; 
}

At it’s simplest, this defines the default backend used by Varnish, defining the host and port that it should listen and intercept content on.

Backend polling

One handy feature of Varnish is checking at predefined intervals if a backend is still healthy. It’s called ‘Backend Polling’ and is configured by adding a probe section into the backend declaration:

.probe = { 
    .url = '/'; 
    .timeout = 34ms; 
    .interval = 1s; 
    .window = 10; 
    .threshold = 8; 
}

The above are the default settings provided by Varnish and tell it to visit a particular .url every .interval and that if for at least .threshold out of .window probes, the url responds within .timeout milliseconds, the backend is still considered healthy. Once considered ‘unhealthy’, content is served from the cache for a pre-defined period.

Starting Varnish

We’ll cover specific changes to the Varnish configuration under each platform option, for now let’s take a look at general options.

Ports

Initially the port for your web server will need changing from the default. For example in the Apache Vhost configuration change the port to 81 or 8080.

Start the Varnish daemon with the varnish command or using a service wrapper. The daemon has flag options, the most common and useful being:

  • -f: Sets the path to the configuration file.
  • -s: Cache storage options. Setting this to RAM will provide even greater speed boosts.

Checking all is working

Run the varnishstat command or visit isvarnishworking.com to check your Varnish server is ready and listening to requests.

What not to cache

There are certain parts of a site that we don’t want to cache, for example the administration pages. We can exclude them by creating a vcl_recv subroutine in the default.vcl file containing an if statement that defines what not to cache:

sub vcl_recv { 
    # URI of admin folder
    if (req.url ~ "^/url/")
    {
        return (pass); 
    }
    return(lookup); 
}

If you are using Varnish 4, things are slightly different, including return values. The vcl_recv function now returns ahash value instead of a lookup.

sub vcl_recv { 
    ...
    return(hash); 
}

This is also where we set sites or subdomains that Varnish should ignore by adding a req.http.host ~ ‘example.com’ to the if statement.

Cookies

By default Varnish will not cache content from the backend that sets cookies. Similarly, if the client sends a cookie, it will bypass Varnish straight to the backend.

Cookies are frequently used by sites to track user activity and store user specific values. Generally these cookies are only of interest to client-side code and are of no interest to the backend or Varnish. We can tell Varnish to ignore cookies, except in particular areas of the site:

if ( !( req.url ~ ^/admin/) ) {
    unset req.http.Cookie;
}

This if statement ignores cookies unless we are in the admin area of the site, where cookie passing may be of more use (unless you really want to frustrate site administrators).

Other exceptions

With a default installation, Varnish also doesn’t cache password protected pages, GET and HEAD requests.

Putting Varnish to use

We will now look at two perfect use cases for Varnish: Drupal and Magento. Both are highly dynamic systems that allow non-technical users to undertake a wide variety of complex tasks. This can lead to database query-heavy page loads and busy sites will become noticeably slow. Typical pages built with these systems will have a mixture of content updated infrequently and frequently.

Drupal

Drupal has default caching options that perform similar functions to Varnish, but won’t provide the flexibility or speed increases required by larger or more complex sites.

In true Drupal manner there is a module for handling Varnish integration to save some of the manual configuration outlined above.

Install the module and make sure you follow the installation instructions included in the module’s Read Me file.

Make sure that the /etc/default/varnish file has the following daemon options set (and the indentation is important):

DAEMON_OPTS="-a :80 \
        -T localhost:6082 \
        -f /etc/varnish/default.vcl \
        -S /etc/varnish/secret \
        -s file,/var/lib/varnish/$INSTANCE/varnish_storage.bin,128M"

Ensure Apache and any associated virtual hosts are listening on port 8080, not 80. Restart both services after making these changes.

You may need to set a ‘Varnish Control Key’ in the module configuration page. Find out what that key is with the cat /etc/varnish/secret command and paste it into the settings page. Select the correct Varnish version, save the settings and you should see a series of green ticks at the bottom of the page.

The Varnish module interacts with the default Drupal cache settings, so make sure you have that enabled and configured for your use case.

Run varnishstat from the command line, start navigating the site as an anonymous user and you should see stats changing in the command output.

One of the paths we don’t want to cache in Drupal are the admin pages, we can do this with a vcl_recv sub-routine:

sub vcl_recv { 
    # URI of admin folder
    if (req.url ~ "^/admin/")
    {
        return (pass); 
    }
    unset req.http.Cookie;
    return(lookup); 
}

You might want to consider not caching (logged in) user pages, system update pages and other pages generated by highly dynamic modules such as flag that make extensive use of ajax to function. Do this by adding further req.url parameters to the if statement.

Magento

A default installation of Magento ships with an internal caching system that stores static versions of site elements in a specified folder. The System -> Cache Management page provides an overview of current cache status as well as letting you clear all or individual component caches. You can clear aggregated CSS and JS files and auto-generated image files from this page.

The forthcoming version 2 of Magento will support Varnish caching by default, but for now we need to make use of 3rd party plugins, I recommend the Turpentine module. Make sure you read the project’s readme file as it notes some extra configuration steps, ignoring them may break your site.

The Turpentine module is highly configurable and will make the necessary changes to vcl files and Varnish config for you. Some key options to set are:

  • Backend Host: The Varnish host, defaults to 127.0.0.1
  • Backend Port: The port Varnish is running on, defaults to 80
  • URL Blacklist: A list of URLs to never cache relative to the Magento root. The admin and API urls are automatically included.

The Turpentine module ties into the default Magento cache, so clearing caches on the Varnish cache page will clear the relevant Varnish caches.

General tips

Aside from using Varnish with any of the dynamic systems above, here are a handful of other miscellaneous tips that will help the cache-ability of any site.

Consistent URLs

If you are serving the same content in different contexts, it should use the same URL. For example don’t mix usage of article.html, article.htm and article, though your CMS may allow it. This will lead to three different cached versions of the same content.

Use cookies sparingly

As we saw above, cookies are hard to cache and are rarely as necessary as we think. Try to limit their use and number to dynamic pages.

File handling

Loading site assets can be one of the most time consuming parts of a page render and there simple tips to reduce this burden:

Using CSS Image sprites for iconography instead of multiple small files results in less network traffic.

Hosting CSS and JavaScript libraries locally means less network traffic and more control over caching strategies. This can mean an increase in maintenance overhead to keep these assets up to date. Store these assets in consistently named folders so references to them can also be consistent.

Fast forward

I hope this introduction to speeding up your dynamic sites with caching was useful. The performance gain is worth an initial period of configuration, experimentation and tweaking. In this era of short attention spans and impatience, any speed gain you can squeeze out of your set up will make the difference to your users and competition.

 

Featured image, network cache image via Shutterstock.

LAST DAY: Complete Mandevilla Font Family – only $17!

Source

si pide pass es: Ben Cook

Wednesday, 11 November 2015

Can BPG replace JPG?

BPG stands for Better Portable Graphics, and it’s a new image format, the aim of which is to replace JPG. To do this, BPG delivers the best of both worlds: superior quality, and smaller file size.

But wait a second, there’s more: BPG also supports animation. And not just any kind of animation; actual GIF-style animations that boast MP4 quality while being smaller in size than the MP4 from which they were created.

All of this sounds like a torrent of nothing but upsides for BPG, but that would be too good to be true.

In reality, BPG isn’t completely free of problems, but it still represents a technology that’s worth exploring and can give JPG a real run for its money.

The brainchild of French programmer Fabrice Bellard who thinks BPG can legitimately replace JPG altogether, BPG shines when images are heavily compressed. In that state, it definitely shows a marked quality increase compared to JPG.

The thing that sets BPG apart is its ability to handle transparency, something that JPEG simply can’t. Interestingly, both PNG and GIF can handle transparency and are supported by the majority of browsers. BPG files, though, take some work before browsers will display them: they need a 55-kb JavaScript decoder that’s embedded on a site before they can be used.

Beyond this, it all comes down to the pros vs. cons of switching over to BPG. From the design community’s viewpoint, it all comes down to what can BPG do better than JPG to justify moving from one to the other.

A comparison of JPG quality (left) and BPG quality (right).

The benefits of BPG

For starters, as mentioned above, BPG supports animation, so what does this mean in practical terms? With BPG, you can effectively create a GIF that’s half the size of the equivalent MP4.

There’s also video inline play to consider. For instance, on mobile Safari browsers, no video can be played inline. BPGs come to the rescue: it’s possible to have BPGs that are as small as 5% of the original.

Another thing is the high compression ratio. BPG is smaller than JPG, as well as Google’s WebP, which itself is a new image format that offers lossless image compression. To put things in context further, WebP is 26% smaller than PNG. Interestingly, WebP is already supported by both Google Chrome and Opera browsers, which does make WebP more accessible than BPG.

A comparison of JPG quality (left) and BPG quality (right).

Still, there’s really no learning curve when it comes to BPG. You can begin using it today as long as you have a JavaScript decoder.

However, BPG’s benefits go beyond just the specs. There are also real, observable differences. For instance, not only can BPGs hold up better, but they can also produce images that feature much less color banding and blocking. Along the edges of images, BPGs don’t have as much step-ladder aliasing, which is why they look sharp even down to smaller sizes.

The downsides of BPG

As alluded to above, nothing is completely perfect, and that’s also the case with BPG. It does have some drawbacks, such as lack of native support, that extends its decompile time. In general, the larger your file, then the slower the decompiling time will be. Presently, decompiling time is approximately between 8 and 10 seconds. If browsers start to include native support for BPG, this time will drastically improve.

There’s also main thread blocking to contend with, when you’re decompiling larger files.

BPG is created by using HEVC video compression technology, which has been patented by a company called MPEG LA; the same company that owns the H.246 video codec. MPEG LA, being the patents’ owners, could eventually charge royalties on both software and hardware that has BPG decoders built in. In turn, this makes it somewhat unappealing for popular browsers such as Mozilla’s Firefox, open-source and free, to support the BPG format.

Last but not least is the lack of sound support. While this may be okay with some — it’s not a video format after all — it would still be nice to have sound.

Hard to change habits

Looking past these downsides, there’s the bigger issue to consider that many designers are simply used to JPG in spite of its drawbacks. While some may call it complacency, the fact is that many designers accept JPG and have become used to working with it across many different projects.

A comparison of JPG quality (left) and BPG quality (right).

As such, it’s hard to get designers to broadly change over to BPG, especially when you look at how some designers use it by default. In addition, JPG is also widely understood and supported basically everywhere you look. The fact that BPG isn’t, at least not at the time of this writing, is probably its biggest downside.

Factor in the reality that image download times have been getting better due to quicker Internet speeds, and it’s hard to believe that BPG, in spite of its clear advantages, will take over from JPG anytime soon, at least completely.

Summary

There’s no doubt about it. BPG is new, exciting and serves a need for smaller sizes and higher-quality graphics. In spite of these advantages, though, it is unlikely that designers will make a mass exodus from JPG and start using BPG overnight. That’s especially true when you consider the issues BPG may have with its lack of support from browsers and possible licensing issues as well.

BPG is a fresh, exciting format. It delivers superior quality and smaller file size. But with a lack of native browser support, and potential licensing obstacles to it gaining that native support, whether the design community will be switching over to this file format in the next few years, remains to be seen.

A comparison of JPG quality (left) and BPG quality (right).

1,500 Images with No Backgrounds v3 (optional Extended License) – only $39!

Source

si pide pass es: Marc Schenker

Jekyll against the rest of the world

I’m stood in the center of a room, confident my choice to go all static had been a good one. It’s a serene scene—nothing can touch me.

There are website owners running around wildly, chasing WordPress security vulnerabilities, while at the same time trying to plug holes, which the dubious free plug-ins they downloaded had ripped into their sites.

I see a man standing at the window, bashing his head against it in a slow rhythmic pace. It’s not a medical condition. He’s simply repeating the rate at which his PHP-based, database-driven publishing solution, accepts new requests.

From the corner of my eye I can make out a woman who was frantically flailing her arms about. She was trying to get into the room. Unfortunately, no one would let her in; her website had been infected with malware and whenever someone tried to visit it, there was a warning, urging users to run away as fast as they could.

Static publishing, oh blissful serenity. Why do I like you so much?

Dynamic is evil

It’s not, really. But bear with me for a moment…

WordPress is a wonderful but complex system that’s largely responsible for the blogging revolution of the past decade. Its security track record isn’t the best and you can like its code or not. The fact remains that it is software running on a public-facing server, installed and run by people who shouldn’t touch a server if their life depended on it. WordPress perpetuates this with their “famous 5-minute installation”. In an ideal world, they would recommend people without a clue to simply use their hosted solution, which is fine. But then, we don’t live in an ideal world.

Imagine you’re publishing a new post on your site. How often does that content change? Is it really necessary to recreate the final HTML output you deliver to your users every single time someone accesses your site? Query the database, run it through the templating engine, run it through plugins, render HTML, deliver. That’s a lot of work.

your static content should be generated statically, delivered to your visitors as is

Most likely, you won’t notice this immediately. But if your site suddenly becomes popular, chances are, it won’t scale very well. It could go down. Of course there’s options for you if you wish to stay dynamic and have that flexibility. You could use caching plugins or even full-fledged web accelerators like Varnish. To me, this is just throwing huge piles of code and applications at the problem.

The problem is: your static content should be generated statically, delivered to your visitors as is. That’s dealing with the problem in the right way.

Easy for me to say, right? There are downsides:

  • Statically generated pages usually offer no way of showing any sort of dynamic content.
  • If you need comments on your site—a common request, though why you would want that is beyond me—you would have to resort to external providers like Disqus or other commenting platforms. There’s pros and cons to this, I’ll let you decide.
  • If you want your visitors to be able to search, you need to implement it yourself on the client-side.

I really wanted search to work on my site, so I wrote it myself—can’t hurt to freshen up that rusty JavaScript. If you have JavaScript activated, a small JSON file containing the sitemap will be loaded and can be queried from the search bar up above. It’s super fast. Try it.

Externally, you could use Google Site Search.

What does Jekyll do?

Look, that’s my Terminal running Jekyll in serve mode. It launches a tiny web server and let’s me live preview all the changes in my site in my browsers of choice. Locally.

This is actually quite amazing. The setup for a database-driven CMS solution is usually so cumbersome that most people will work with the live site on a server somewhere else in the world. Bad for you if you don’t have an Internet connection. And do you really want to write your content in a browser? Really?

The setup for a database-driven CMS solution is usually so cumbersome that most people will work with the live site on a server somewhere

This setup is so easy that I can always work on a local machine and push my changes to my server. I let my server do the build (just like I could locally, but why not) and refresh what’s currently in my web root…automatically.

Whenever an article is done, I just commit my changes via git. It’s actually really simple to set up.

And it is oh so flexible. And safe! There’re hundreds of plugins to choose from to do fun stuff with your content during the build process. The end result will always be static pages — nothing to break into.

What Jekyll doesn’t do

With Jekyll, you start out with nothing. Nothing at all.

It actually allows you to generate a very simple blog-ready site with jekyll new, but it’s just something to start from and learn the structure of how a Jekyll site can be built.

You should really be interested in starting from scratch.

If all you want to do is download a theme and start writing, you should probably go elsewhere. Try Medium, it’s a well-designed service with a great community, made for people who just want to write. Now you can even publish directly to Medium from the best editor in the world.

If you think this sounds like loads of fun, go for it. You will not regret it.

Serene

So now I’m sitting here with BBEdit and Ulysses, coding and writing. Which is really all I ever wanted. I do it in the environment I desire to be in. It frees me.

I’m back to where it all began. I have a text editor and I fill it with words. When I’m done, I save the file and that’s it. I can preview to my heart’s content. And once happy, I will simply commit.

You know you want it. Simplify.

You don’t want a site that’s not really you. A site filled with social buttons and widgets and gadgets and analytics and tracking cookies and banner ads and pop-up ads and everything else that makes your visitors scream at you from afar. Generated anew every time someone visits your site. Every. Single. Time.

Be that person in the middle of the room. Perfectly rooted, smiling contentedly.

 

This article was originally posted at tobyx.com, republished with the author’s permission.

Featured image, static website image via Shutterstock.

1,500 Images with No Backgrounds v3 (optional Extended License) – only $39!

Source

si pide pass es: Tobias Horvath