Try Tuts+ Premium, Get Cash Back!
Five Quick Web Design Tips From Team Envato

Five Quick Web Design Tips From Team Envato

Tutorial Details
  • Topic: Random tips
  • Estimated reading time: Not long at all..

I recently had the pleasure of spending two weeks in Malaysia at the 2012 Envato Meetup. What a place! During our stay there I took the opportunity to glance over my colleagues’ shoulders, picking up tips and tricks as they worked. Here are five brilliant web design tips from the Envato team which I reckon you’ll love..


Jump to Each Quick Tip:


Stuart Richardson
Tuts+ Front End Developer

Stu’s a big advocate of using CSS Preprocessors, specifically Sass with Compass. During the Envato conference he walked us through how he used them when building the marketplace themes, perfectly demonstrating how efficient Sass can be when working on large, multi-site projects.

Our marketplaces are all variants of the same theme:

A standard CSS approach would have you (for example) building base stylesheets to hold most of the structural styling, with additional stylesheets to alter the colors and graphics for each site. At best, you’d be maintaining multiple copies of very similar (if not identical) CSS files.

Not so with Sass. By writing a single set of base SCSS stylesheets (partials), plus a Sass variables file for each site variant, your project structure would look more like this:

Partials are chunks of style rules which can be included in your main file – they can be reused in other files too. By preceding the file name with a “_” the partial SCSS files won’t be compiled into deployable CSS themselves, they’ll just contribute to the application files you choose to build.

For example, you may have a Sass file which dictates all the form styles within your project. You name the file “_forms.scss” and bring it into your application file without the underscore or the file extension:

@import "forms";

No “_forms.css” will be generated, but the rules within “_forms.scss” will contribute to the file you’ve pulled it into.

Your variable files will set all the aspects of the theme which can alter, such as link colors, logos etc. They may look like this, for example:

/*themeforest variables*/
$link_color: #FFE59E;

This value can then be used in the main application Sass file, or any partials which are imported:

a {
  color: $link_color;
}

To generate a whole new theme all you have to do is alter the variables in one file (or drag in a different _variables.scss). To alter a feature across all the themes, you only need maintain one file; the partial where that particular style occurs.

We’ve introduced Sass and Compass on Webdesigntuts+ before now, so take a look if you’ve yet to make the jump.


Cameron Jones
Front-end Developer

Cameron has made it his personal crusade to make everything we do responsive. He’s already left his RWD mark on the new Rockable Press and Creattica sites, and will soon be working his magic on Tuts+..

Here’s a great tip to help you visualize your web layouts, at multiple resolutions, in seconds.

Get yourself over to Benjamin Keen’s site where he has a great JavaScript “Responsive Design Test Bookmarklet”. Alter the sizes of the viewports you’d like to test, then generate the bookmarklet.

All you need to do now is drag the link provided into your bookmarks. Whenever you’re viewing a site in the browser, hit the bookmarklet and the layout will appear in all the various resolutions!

But wait! There’s more! Cameron has taken this one step further and assigned a hotkey to this bookmarklet; all he now needs to do is type the appropriate phrase (for example “rwd”) in the url bar and the bookmarklet takes effect. Perfect if (like me) you prefer not to have a bulky bookmark toolbar on display at all times.

Cameron was using Firefox, which allows you to assign bookmark hotkeys with its handy Smart Keywords feature. I usually work in Chrome, which is sadly lacking this feature. However, there is a way round this, because it is possible to assign hotkeys to trigger search engines. Let’s now add our bookmarklet to Chrome in this fashion:

First, right-click the url bar and go to “Edit Search Engines..”

Then you’ll be given the option to add a search engine or query. This will act as your hotkey, so give it a name (whatever you fancy), assign a phrase (such as Cameron’s “rwd”), then paste the bookmarklet JavaScript into the final input.

Note: Your bookmarklet will have to be URL encoded, so make sure it looks like this:

javascript:document.write('%3C!DOCTYPE%20html%3E%3Chtml%3E%3Chead%3E%3Cmeta%20charset=%22utf-8%22%3E…

not this:

javascript:document.write('<!DOCTYPE html><html><head><meta charset="utf-8">...

Erik Meyer has a handy tool for encoding URLs if you need it.

So that’s it! Visit the page you’re working on, type the keyword into your url bar and bang! Instant RWD test!


Rodney Blackney
Designer

Pinterest not macho enough for you? Delicious too.. (wait, do people still use delicious?) Need a way to bookmark actual content, back it up to your Dropbox, and get visually inspired by what others are bookmarking? Rodney reckons there’s nothing better than Gimme Bar:

The modular interface will be a familiar sight to those of you who pin and bookmark with other services. Follow, favorite, backup, then share through all the social channels you’ve plugged in..

Check out what else Rodney gets up to on Twitter and Dribbble!


Jacob Zinman-Jeanes
Designer

Here’s the thing; when I asked Jacob for a quick tip, he lamely suggested a lorem ipsum extension, which will help you pump filler text into your designs.

But Jacob unwittingly taught me an alternative, invaluable lesson during the Envato conference: “Don’t entrust your iPad to Jess Hooper”. Jess works in the Melbourne office and is a member of the review team. She kindly offered to look after my iPad when she left the group and returned to the hotel one night.

The following day, while I was fighting my way through the Malaysian jungle, this came through on someone’s mobile:

A Tumblog dedicated to my iPad and its shenanigans that fateful day.

Joking aside, Jacob is a very talented designer. You’ll have seen his work in places such as the million.envato.com and 1,000 WordPress Themes sites, along with many of the Marketplace bundle and Rockable sites. The tip to take away from this is:

Build a Tumblog whenever you have the chance.

It’s straight-forward, it’s quick, it’s fun and you can practice your theming skills. Jess, I will get you back.


Jeffrey Way
Tuts+ Premium Course Producer

Watch Jeff work and, even if he’s not teaching you, you’ll learn from him. What I picked up from him this time might not sound like the biggest time-saver in the world, but here it is:

You don’t have to close your list item tags, let the browser do it for you!*

*by no means compulsory..

This feels kind of unnatural, a bit like omitting the quotation marks from your html attributes:

<input type=email>

but relax, it’s fine. Next time you find yourself churning out list items, try doing them like this:

<ul>
	<li>Here's my first list item
	<li>And here's number two
	<li>I'll finish with this one
	<li>Or maybe this one.
</ul>

Many aspects of HTML markup which we’ve been trained to think of as compulsory, are in fact, entirely optional. We tend to think of this as invalid because of the way XHTML validation used to beat us up over it. If you prefer to leave </li> tags out, if it saves you time, ditch them. Browsers will still know exactly what you mean.

The same is true of </html>, </head> and </body> . For more information on exactly why this is the case, check out Jeff’s recent Rockable book on HTML5.


Conclusion

Well, I hope you found these random tips helpful in some respect (I know I did)..

Note: Want to add some source code? Type <pre><code> before it and </code></pre> after it. Find out more
  • Pingback: Five Quick Web Design Tips From Team Envato | Shadowtek Hosting and Design Solutions

  • http://webdesignertutorials.com Web Designer Tutorials

    You still have to close items due to verification issues and for better readability.

    • Hamid

      yes i’m agree with him.

    • http://croftmedia.co.uk Greg Tyler

      I disagree completely. The spec doesn’t require endtags on list items, it validates fine all the way back to HTML 2 (save XHTML1.1), and browsers support it fine. As for readability, I personally find lists with omitted endtags much more readable.

    • http://net.tutsplus.com Jeffrey Way

      Hey guys – to clarify, for your personal projects, even though they aren’t required, it’s still might be considered best practice to leave them in. I won’t lose any sleep over it though. :)

      Alternatively, when you’re writing blog posts, and things of that nature, leave off the closing list items. The parser will add them in for you. I promise! It’s a small convenience, but does save time.

    • http://net.tutsplus.com Jeffrey Way

      About “verification,” not sure what you mean. You mean validation? If so, then you might be missing the point of validation. In terms of readability, maybe so, maybe not. Do what feels best to you.

    • http://imdev.in Devin Walker

      I’m going to still be closing my tags. It’s just too easy not to. Gimmie Bar looks awesome, I may have to give that a go.

  • http://www.theconnectorz.com/ Bragadeesh

    Hi There

    These are very useful information, now i got a clear idea. Thank you so much for the info, i will subscribe with you :-)

  • http://www.templaterange.com Joomla Templates

    great tutorials..

  • http://twitter.com/adampuddlemedia Adam Westbrook

    Coming from a XHTML background the idea of not closing tags makes me shudder! While I appreciate it’s completely valid in HTML, surely it makes the markup less machine readable? People from the design and HTML side sometimes seem to forget that markup isn’t just something that’s a hassle, and in fact strict, well formed markup can open up some fairly creative uses from external content readers etc.

  • Pingback: Five Quick Web Design Tips From Team Envato

  • http://randomtastic.com Mr. Tastix

    Not closing tags? Argh! Madness!

    Like Adam, above, I come from a heavy XHTML background. Whilst you -do not- have to close list tags and the W3C still consider this “valid”, it makes me cringe a little not doing so.

  • Mindgrinder

    I still don’t understand why people get so caught up on this stuff! close the list or don’t close it! is up to you why make such a big deal hey if it is going to save my more typing and there is no negative side effect of course I’m going to do it.

    Thanks great tip!

    FYI. I agree you can read the list better without the closing tag ;)

  • http://www.jqui.net Val

    I completely disagree with the optional ending tags.

    Just because someone says so does not mean he is right, and as you have mentioned on the page that it’s only HTML5, a true developer would develop a website that works well and will play by the rules to serve it’s website visitors the best cross browser.

    I would advise to use ending tags, and don’t be lazy as it will become a bad habit.

    • http://www.snaptin.com Ian Yates
      Author

      I think the important lesson is really in understanding how browsers interpret and render markup and styling. You say it would be a lazy bad habit, but if it isn’t a problem, where’s the issue?

      • Frank

        Your right, it does depend on how the browser interpret and render markup. However, while there are standards on how to render valid markup, there is no standard way to render invalid markup.

        If a browser renders valid markup poorly the community as a whole may come and tell them to fix their problem. If you are not using valid markup, you have no one to blame but yourself when a browser chooses to render it poorly or not at all.

        I highly doubt any web developer or designer wants to go back to the dark ages of IE6 and before. One of the reasons while IE6 lasted for so long before open standards finally broke free was that IE6 had a habit of rendering even poorly coded HTML and their were many sites with poorly coded HTML. Too this day we still have to deal with “quirks” mode. Do we want to go back like this just so some lazy schmo doesn’t need to type a few characters?

        If you are that lazy you should use an editor that automatically closes tabs, cut and paste code (including closing tags) yourself, use a WYSIWYG editor, or do the development community a favor and stop coding.

  • Mason

    I know I’m a bit late to this, but eh, felt a want to chime in.

    I’m a bit new to HTML and CSS, and the idea of leaving tags off to save you a few seconds seems…odd, at best. Now, I should mention that I come from a C/C++ background, and it sounds like similar advice to “Don’t worry about proper tabbing, the compiler doesn’t care about white space, it’ll save you time in the long run.” Which is just really bad advice. Am I off with my metaphor here?

  • http://www.franboud.com Francis Boudreau

    I also think that for readability, you have to close the tags… but don’t close them if you “read” your code well without them! But for me… I’m closing them!

  • http://Terrygooding.com Terry Gooding

    Not closing tags is a designers attitude – either do it properly or don’t do it at all…

    • http://www.facebook.com/RobertD63 Robert DeLuca

      While I’ll probably always close my tags, if it renders properly across all mediums, why have that attitude? Sure its lazy, but it works, so no big deal really.

  • http://www.aks-india.com/ Aahna Saxena

    You have covered some important elements of web design, feeling privileged to have read this article and I would recommend this to other web designers i know. Thanks for posting such useful information.

  • http://www.facebook.com/wanny.miarelli Wanny Miarelli

    Wow, just wow ! :D as always, thanks for ur articles !