7 Pro-Tips for Web Design

Here at The Site Slinger we live and breathe web development – we’ve been experts in turning design to code since 2009! All too often, website design files get submitted to us missing some of the fundamental components for effective and efficient web development. Whether you are a designer working on a website for a client, or a client who isn’t sure what they need to get from their designer, following these pro-tips will get your design ready to be turned into code.

Here at The Site Slinger we live and breathe web development – we’ve been experts in turning design to code since 2009!

All too often, website design files get submitted to us missing some of the fundamental components for effective and efficient web development.

Whether you are a designer working on a website for a client, or a client who isn’t sure what they need to get from their designer, following these pro-tips will get your design ready to be turned into code by our team at The Site Slinger.

7 Pro-Tips for Web Design


DO 
design in Photoshop, it is the best for web design (sorry, Illustrator, Fireworks and InDesign fans!)

DO design all of the pages you want to see as HTML or on a WordPress site — We match your designs exactly!

DO design all animation states, javascript validation, button states (click, hover, off), modals and anything else you can think of. If you don’t see it in the design, we can’t see it to code it!

DO label and organize your Photoshop design “PSD” files — 1 page per PSD, organized into labeled folders and layers.

DO say “I’m not sure, I will have to check” to a client if you are unsure on complex functionality or implementation — Its okay to say “I don’t know” – that’s why we are here!

DO
 talk with your developer and spec out your project before signing off on designs.

DO ask questions and get to know your friendly Austin, Texas web developer. We are always happy to answer questions about turning designs into code!

Have a question about one of these pro-tips or want to know more? Chat with a Site Slinger from 8am-6pm CST here on our website, or contact us.

*Image courtesy of Wikimedia Commons, used under the Creative Commons license.

10 Reasons NOT to code your own HTML

At The Site Slinger, we see LOTS of different kinds of web designs from our customers, and we hear lots of different reasons why they choose us to turn their designs into code. I wanted to share 10 of these reasons with you to show you the ways The Site Slinger helps you bring your designs to life, whether you are building a simple landing page, a complex web application, a WordPress theme, or even a great looking HTML email.

10 great reasons not to code your own HTML for your next project.

10. You can’t code.
Design to code services are for people just like you, no technical experience required. Don’t worry, developers don’t bite.

9. You are on a deadline (or multiple deadlines)
Rapidly approaching deadlines are not good for your stress level. If you don’t know how you will get the job done in time we have RUSH PSD to HTML options available.

8. You need jQuery or JavaScript animations
Most design to code services charge extra for JavaScript animations, we include it in the per page price.

7. Your client doesn’t want to pay for you to code by the hour
Using a design to code service for your website will be a fraction of what it would cost to code by the hour. We’ll even give you a PDF estimate to take to your client!

6. You don’t know any reliable web developers
Finding any good developer is hard, finding reliable outsourced development is even harder. You need someone you can count on who knows how to make you happy.

5. You have a LOT of pages to develop
If you build large, complex applications with extensive views, design to code services save you time so you aren’t wasting developer time coding HTML.

4. Your development team is backlogged
Your team is great, but they are busy building out your application. Don’t slow them down!

3. You are building a WordPress theme
WordPress sites are overtaking the web — everybody wants one and now you don’t have to be an expert to give it to them.

2. You build lots of web applications
We work with Bootstrap, 1140gridCSS, 960gsZurb and many other responsive web application frameworks. Get your prototype up in 5 days or less.

1. You are the smartest person on the planet and realize The Site Slinger should code your designs, not you.
We are happy to help!

Want to Learn More? See Examples!

The Easiest way to order PSD to HTML, from The Site Slinger

The Site Slinger turns designs into code, and sets itself apart from other PSD to HTML companies with its quality, reliability, & speed. We are the only company to offer easy online ordering and a fully transparent development process.

We’ve implemented a new online ordering system!

Check out this walk-through and see how easy and fast it is to get your project from design to code with PSD to HTML from The Site Slinger.

LOG IN/REGISTER

Enter your email address and password, or select CREATE ACCOUNT at the top to register as a new customer.

The easiest PSD to HTML

 

UPLOAD PROJECT FILES

We make it a breeze! In the SUBMIT A NEW ORDER section upload your PSD file(s) via drag-and-drop, or click ‘Pick File’ to browse and select your file. We’ll see the files right away, and you can always add more later.

The easiest PSD to HTML

 

ENTER PROJECT INFO

While your file is uploading, let us know your Project Name, and select your Project Type & Project Deadline from the drop down options. Tell us a little bit about your project, or ask any questions you might have – we’ll see your order immediately and are ready to help.

The easiest PSD to HTML

 

VIEW ORDERS

To view an existing order, select YOUR ORDERS from the left menu. Your current orders, and completed orders, will be listed. Select the VIEW PROJECT button to see an order’s details. A consolidated list of your order history makes for easy reference – each and every time.

The easiest PSD to HTML

 

REVIEW ORDER DETAILS

We want you to feel happy, not sad, during development so we built a fully transparent ordering process. In the project details screen you can view the Project Status, Project Price, Confirmed Delivery date and even view an Invoice in the left sidebar. You can also leave your comments about the project and check for our replies. You will receive an email notification whenever we comment or have an update for you. That’s how we keep you updated at each step in the development process!

The easiest PSD to HTML

 

REVIEW/ADD ORDER FILES

On the ORDER FILES tab within the same screen you can review the file(s) you’ve already uploaded, and add more files, if you need to. As always, we’ll promptly review your order & files, and ensure everything’s in place for a quote. That’s just the first step in getting the project turned around as quickly as possible – we make sure all PSD to HTML projects are completed in 7 business days or less.

The easiest PSD to HTML

 

OTHER FEATURES

Click the BACK TO YOUR ACCOUNT button in the upper right to go back to the main account page. From here, you can also Edit Your Profile, or get your Referral Program details. Spread the word about The Site Slinger and receive a credit on future orders!

The easiest PSD to HTML

 

What we do.

PSD to HTML

Built for designers and headquartered in Austin, Texas, The Site Slinger makes building custom websites easy.  Send us your PSD files and we return HTML code in 7 business days or less. Take our HTML and use it to create custom websites, WordPress themes, web apps, enterprise software or whatever else you can think of. This is the fastest way to get building for all your web projects.

PSD to WordPress

Our PSD to WordPress product is the best starting point for custom WordPress development. We hand code your PSD files into static HTML views and then compile them into a basic WordPress theme for custom development. We deliver the WordPress theme files and SQL file for your developer to customize.

If your project requires additional development and your team is without a developer we can recommend great developers.

We want to give web design and development teams an upper hand with easy PSD to HTML and WordPress. Our easy online ordering, personal 24/7 service, and expert developers take the pain out of outsourced development.

Test us out! Submit a design for a free quote today and we’ll be happy to give you a $100 discount off your first order. If you have any questions, just let us know!

Design Rules for PSD to HTML

Want to make your development team love you? Learn how to design your PSD (Photoshop design files) into clearly labeled, appropriately layered files for PSD to HTML!

If you’re coding PSD to HTML/CSS, you know that there’s often a disconnect between the person creating the designs and the development team coding them. With well organized and labeled files you can avoid many of the worst web development pitfalls.

By following these simple steps you can hand your PSD designs off to a good PSD to HTML team and they will come in back pixel-perfect, just like you imagined. This makes PSD to HTML easy for both you and the development team.

Some basic rules to follow:

1. One PSD file per page template or folders for each page in a single PSD file. What is a PSD?

2. Label all folders with the section of content on the page they refer to (Top navigation, Content, Footer, etc) Example

3. Separate folders for “on” and “off” states.  Make sure to separate your on/off states into different folders so the development team can easily identify the different states in the design.

4. Provide a text file or .pdf that clearly outlines all functionality for the individual pages (this includes things like animations, slide transitions, etc.)

5. Be sure to design all animation states, javascript validation, button states (click, hover, off), modals and anything else you can think of. If you don’t see it in the design, we can’t see it to code it!

 PSD to HTML Example

This is an example of a PSD single page with well organized folders for the content of the page. The organization of this is is clear and easy to follow.There are subfolders for each portion, clearly labeled.

PSD File Structure

Within the folder structure each page has its own subfolders that are all appropriately named. The elements for each group are within the subfolder and vector images are imported to the file when necessary (logos or other images). Make sure to show different on / off states. Rather than show multiple flat files for each state, they should be organized and named within the PSD in a way that the development team can understand.

Below is a good example of how files should be organized when you hand them off to your development team. You will see that there is 1 PSD per page with all of the necessary states for web development included in each PSD file.

Photoshop (PSD) File Structure

FileStructure

 

If you hand us well organize and labeled PSD files, our team will code the HTML/CSS and hand you back pixel perfect, markup!

Final Markup (HTML, CSS, JavaScript)

File_Markup

 

If you have questions about the process we would love to hear your thoughts in the comments!

HTML5: The Language of the New Web

No longer a novelty, HTML5 has already changed the way web developers code and the way users interact with websites. Contributing to the decline of Flash, HTML5 is an undeniable force utilized by countless modern websites.

HTML5 Logo

The New Standard.

HTML5 is setting the bar for the ever changing web landscape. In addition to being integral to the single-site, multi-device experience, HTML5 serves as a standard for video, Flash-like interactivity, and is even creeping into the ad space. With HTML working hand in hand with CSS3 and JavaScript, HTML5 brings us to the next level of web development.

HTML5 is paving the path of the future for the Web:

It will be the go-to language for cross-platform development. According to Web Developer Juice, “Almost every platform – mobile or web – is now making the shift to HTML5 (this includes Blackberry OS, Palm WebOS, and Windows 8).” And Strategy Analytics predicted that HTML5 phones are a hyper-growth market, and global sales will increase 365% by 2016, from 2011. Developing for the desktop now includes developing for mobile. Which means faster and more cost-effective reach.

Ads will continue to shift from Flash. Apple adamantly denounced Flash, so, unsurprisingly, their iOS devices lack compatibility with those traditional Flash ads you otherwise see blinking at you across the web. With so much of mobile web traffic coming from iPhone and iPad users, advertisers can’t ignore that fact. Even on desktops, HTML5 aims for faster loading and better integration. Google Mobile Ads now offers a feature to easily convert Flash ads to HTML5 in Adwords and offers HTML5 banners. Pointroll goes as far as calling HTML5 “the future ‘Secret Sauce’ in online advertising.” HTML5 proves, once again, it is the solution for more effective and efficient reach.

It’s a robust and clean coding standard aimed at streamlining coding, publishing and browsing. HTML5 has been designed to do away with the need for add-on browser plugins. Many features are intended to improve site discovery and overall SEO, translating into more traffic. HTML5 includes the use of Canvas, which provides the potential for more graphic interactivity and an alternative to loading images the ‘old’ way – even on the fly! With better support for feedback forms, drag-and-drop tools, chat, and other popular interactive elements HTML5 aims to make developing and using the new Web much easier.
You can reference a useful infographic about HTML5 features and the benefits for future web development here.

To make the most of the new Web, the HTML5 experts at The Site Slinger code with the future in mind, utilizing the latest tools to provide robust user experiences, beautiful and clean websites. We’re happy to turn your vision into a pixel-perfect site via our best-in-the-world PSD to HTML coding, so contact us or submit your design and let’s get it done!

*Image courtesy of W3C, used under Creative Commons licensing.

So what IS responsive web design, anyway?

With the world going mobile there’s no way around it: your site has to adapt to any and every device that’s out there. Think about it… How many devices have you used today? I can count checking my email on three already!

Don’t get lost in buzzwords, understand why/how responsive web design works.

With the world going mobile there’s no way around it: your site has to adapt to any and every device that’s out there. Think about it… How many devices have you used today? I can count checking my email on three already!

In the past, the solution to differing device screens was to build an alternate version of your site, or even multiple apps optimized for the various mobile OS’s. However, these options often prove to be too costly in development and cumbersome to perform maintenance and updates. So what is today’s solution? Responsive web design!

Well, you ask… what IS responsive design? It’s one of those buzz words being thrown around a lot right now.

Responsive design allows for a single site to be designed and developed, yet performs effectively and beautifully across devices of varying screen sizes and orientations.

There are a few key features that allow this to work:

A flexible framework for content – the ‘grid’

The foundation of the responsive design, the grid provides easy content management across varying screen sizes through the repositioning of content areas or boxes.

Check out some great info on how to use the grid in design and download some basic templates here.

Responsive web design
Content moves based on screen size, but should still relay the same message in an aesthetically pleasing way. (Image courtesy of DezignMatterz)

Adaptable visual content

From images to backgrounds and graphical motifs, a solidly designed responsive site must be able to communicate your vision consistently, regardless of device and screen size. These elements of the page must be able to move around and make sense from a user perspective and still effectively tell the user what you’re saying/selling.

Check out some great examples of sites that do this here.

The ability to respond to devices

Generally done via ‘media queries,’ a responsive site must determine the best display configuration and adapt in an instant to changes in screen orientation and size. This should be done in such a way that the user doesn’t notice the site changing.

Check out some great examples of this here.

The Site Slinger understands the need to develop websites in a cost-effective, multi-platform manner. We love coding PSD to responsive design! You shouldn’t spend all of your resources managing updates or site variations across a seemingly infinite sea of different mobile devices. That’s why we build effective, high-value, responsive sites, giving you the ability to deliver content consistently and reliably to all visitors, whether they’re on a desktop, tablet, or smartphone.

If you’d like to discuss the options for translating your web design into a fully responsive site, please contact us, or submit a quote. We’re happy to turn your vision into a pixel-perfect site via our best-in-the-world PSD to HTML coding.

*For further reference on responsive elements see, “Understanding the Elements of Responsive Web Design

The Site Slinger Makes Design to Code Easy.

The Site Slinger makes design to code easy. Headquartered in Austin, our quality, reliability, and speed makes us different than other PSD to HTML companies. We are the only company to offer easy online ordering and a fully transparent development process.

The Easiest Way to Order PSD to HTML

We’ve just recreated The Site Slinger from the ground up focused on offering you the easiest PSD to HTML option, and we want to know what you think! Create an account, upload designs and we will get you a quote in 24 hours or less. Our easy to use online ordering system makes it simple to check the status of your current projects, submit new projects, see order history, and connect with the developers.

We love to code and we know how bad outsourced development can be. Try us for your next PSD to HTML project and get $100 off your first order. Please reach out if you have questions or comments, we would love to hear your feedback!

Follow us on Twitter and Facebook for the latest updates.

Photoshop to CSS Conversion: 3 Methods Compared

Converting Photoshop mockups to live web code is an extremely common practice among web designers. We’ve all done it a million times by hand, so it’s pretty exciting when we start seeing solutions pop up that will help us automate this process.

 

screenshot

Converting Photoshop mockups to live web code is an extremely common practice among web designers. We’ve all done it a million times by hand, so it’s pretty exciting when we start seeing solutions pop up that will help us automate this process.

The latest version of Creative Cloud Photoshop CS6 has a built-in feature for converting Photoshop styles to CSS, and if you need another solution, there are two solid extensions that you can check out. Today we’ll compare the results of all three methods: Photoshop, CSS3Ps and CSSHat to see which is best.

 

Our Three Candidates

This article is all about comparing the results from three different methods of achieving the same goal. We have a design in Photoshop and we want to see it built in HTML and CSS.

Our three methods include Photoshop itself (version 13.1) as well as two extensions CSS3Ps and CSSHat. I recently created a screencast for Psdtuts+ that introduces and does some comparison between Photoshop and CSS3Ps, which you can find here.

I didn’t cover layer group functionality in that tutorial though so I thought it was worth another go and decided to toss in CSSHat as well so we really cover the bases well.

Our Test Case

We’ll need something to test the different conversion methods on, so I whipped up a generic UI panel that could hold anything you want:

screenshot

This is basically comprised of three different layers: the text layer, the top bar and the background. Here I separated them out a bit so you could get an idea of how they were constructed.

screenshot

Below you can take a look at our layers palette. Note that this object is structured very intentionally. All three of the methods that we’ll look at today convert layer names to class names in CSS, so you want to be sure that you’re very careful about how you name your various pieces. Also note that the shapes are made from vector shape layers.

screenshot

Some of the methods that we’ll try out support layer groups, which means we’ll want to convert the structure here to a div structure in our HTML.

HTML

Photoshop can take care of the CSS for us, but we’re still on our own with HTML. Here’s a quick attempt at an HTML structure that will work with the code that Photoshop is going to generate. Without this in your HTML, the CSS won’t do a thing!

	
		<div class="panel"> <div class="paneltop"> <p class="type">Quick Panel</p> </div> <div class="panelback"></div> </div>

Photoshop

Let’s start off with the built in Photoshop functionality. The process here is extremely easy, all we have to do is select our layer group in the Layers panel and go to Layer>Copy CSS (you can also access this command with a right-click).

screenshot

Photoshop provides pretty much zero feedback that anything has happened at this point. There are no options to tweak, no panels to inspect, just the menu command that we clicked above, which places a big chunk of code into our clipboard. Here’s the output, straight from Photoshop.


.panel {
  position: absolute;
  left: 180px;
  top: 25px;
  width: 360px;
  height: 427px;
  z-index: 7;
}
.type {
  font-size: 19.913px;
  font-family: "Helvetica";
  color: rgb( 255, 255, 255 );
  line-height: 1.11;
  text-align: center;
  -moz-transform: matrix( 1.70449868947994, 0, 0, 1.72443193254442, 0, 0);
  -webkit-transform: matrix( 1.70449868947994, 0, 0, 1.72443193254442, 0, 0);
  position: absolute;
  left: 83px;
  top: 25.902px;
  width: 180px;
  height: 27px;
  z-index: 6;
}
.paneltop {
  background-image: -moz-linear-gradient( -90deg, rgb( 1, 98, 171 ) 0%, rgb( 0, 52, 91 ) 100%);
  background-image: -webkit-linear-gradient( -90deg, rgb( 1, 98, 171 ) 0%, rgb( 0, 52, 91 ) 100%);
  position: absolute;
  left: 2px;
  top: 1px;
  width: 351px;
  height: 81px;
  z-index: 4;
}
.panelback {
  border-radius: 20px;
  background-color: rgb( 224, 225, 226 );
  box-shadow: 1.5px 2.598px 5px 0px rgb( 0, 0, 0 );
  position: absolute;
  left: 2px;
  top: 1px;
  width: 351px;
  height: 418px;
  z-index: 3;
}

The Result

If we toss this into a code editor and take a look at the result, the results are a little disheartening. Photoshop didn’t do a great job with the conversion. For starters, the top bar doesn’t have rounded corners. Also, the shadow seems to be at full opacity (too dark) and the type placement is off. If gives us a strong start and genuinely saves us a lot of time, but it’s probably not the magic solution you were hoping for from Photoshop.

See it live: Click here

screenshot

To make things worse, if we jump back and look at the code, there’s plenty to complain about. There are some really wonky things going on here such as the unnecessary transform on the text. It seems that you can let Photoshop write CSS for you, but I’m not convinced that you should.

CSS3Ps

Our next candidate is CSS3Ps, a completely free Photoshop plugin that predated the built-in Photoshop functionality. The website shows some pretty complex examples so hopefully this will tackle our project a little better.

screenshot

With the CSS3Ps extension installed, go to Window>Extensions>CSS3Ps. Then select the layer group and click the logo that pops up inside of the CSS3Ps panel.

screenshot

Once you press that button, a web page opens up and presents you with a timer. You’re forced to wait twenty seconds and look at an ad, which sucks but given that the extension is free, it’s understandable.

screenshot

From here you’re taken to a page containing the code, which I copied and pasted below. Note that this time around, I had to add in periods before the class names. CSS3Ps takes the layer name exactly as it appears in Photoshop, so you add in the “.” or “#” symbols there.

	.type {
  font-family: Helvetica;
  font-size: 10px;
  color: #fff;
}

.paneltop {
  width: 351px;
  height: 81px;
  -webkit-border-radius: 20px 20px 0 0;
  -moz-border-radius: 20px 20px 0 0;
  border-radius: 20px 20px 0 0;
  background-color: #000;
  background-image: -webkit-linear-gradient(top, #0162ab, #00345b);
  background-image: -moz-linear-gradient(top, #0162ab, #00345b);
  background-image: -o-linear-gradient(top, #0162ab, #00345b);
  background-image: -ms-linear-gradient(top, #0162ab, #00345b);
  background-image: linear-gradient(to bottom, #0162ab, #00345b);
}

.panelback {
  width: 351px;
  height: 418px;
  -webkit-border-radius: 20px;
  -moz-border-radius: 20px;
  border-radius: 20px;
  background-color: #e0e1e2;
  -webkit-box-shadow: 2px 3px 5px rgba(0,0,0,.34);
  -moz-box-shadow: 2px 3px 5px rgba(0,0,0,.34);
  box-shadow: 2px 3px 5px rgba(0,0,0,.34);
}

The Result

There’s a lot to like about the CSS3Ps output. For starters, it treats each individual layer as its own object and doesn’t attempt to position them over each other. I actually prefer this and always immediately strip out the absolute positioning code that the built-in method uses. This keeps the focus of the conversion where it should be: on style.

See it live: Click here

screenshot

Speaking of style, the results in that area are improved as well. Notice how the top bar actually has a border-radius this time around and how the box-shadow uses an alpha value to reduce the opacity. This version might be a little prefix heavy on things that no longer require prefixes, but otherwise the code isn’t half bad.

Also, the fact that you can get the output reformatted in Sass or SCSS is a killer feature that easily makes this method better than the default Photoshop feature.

screenshot

CSSHat

The third and final method that we’re going to check out is CSSHat. Like CSS3Ps, it’s a Photoshop extension, but this one will run you about $30.

screenshot

To use CSSHat, simply select the layer that you want to convert and open the CSSHat panel (find it in the extensions menu as with CSS3Ps above). Unfortunately, CSSHat currently doesn’t support layer groups, so you’ll have to do it on each individual layer. This is a serious strike against CSSHat, but it makes up for it in versatility.

screenshot

I love that I finally have some options to tweak. The other two methods were easy, but if you don’t like something, tough! Here I can toggle four different options: comment explanations, browser prefixes, layer dimensions and whether or not the code gets wrapped in a rule named after the layer.

Also notice that you can get the output in an impressive variety of formats: CSS, SCSS, Sass, LESS, Stylus and Stylus CSS. Here’s the output for the plain CSS version:

	.type {
  color: #fff; /* text color */
  font-family: "Helvetica";
  font-size: 10px;
}

.paneltop {
  width: 351px;
  height: 81px;
  -moz-border-radius: 20px 20px 0 0;
  -webkit-border-radius: 20px 20px 0 0;
  border-radius: 20px 20px 0 0; /* border radius */
  -moz-background-clip: padding;
  -webkit-background-clip: padding-box;
  background-clip: padding-box; /* prevents bg color from leaking outside the border */
  background-color: #000; /* layer fill content */
  background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDM1MSA4MSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+PGxpbmVhckdyYWRpZW50IGlkPSJoYXQwIiBncmFkaWVudFVuaXRzPSJvYmplY3RCb3VuZGluZ0JveCIgeDE9IjUwJSIgeTE9Ii0xLjQyMTA4NTQ3MTUyMDJlLTE0JSIgeDI9IjUwJSIgeTI9IjEwMCUiPgo8c3RvcCBvZmZzZXQ9IjAlIiBzdG9wLWNvbG9yPSIjMDA2MWFiIiBzdG9wLW9wYWNpdHk9IjEiLz4KPHN0b3Agb2Zmc2V0PSIxMDAlIiBzdG9wLWNvbG9yPSIjMDAzMzViIiBzdG9wLW9wYWNpdHk9IjEiLz4KICAgPC9saW5lYXJHcmFkaWVudD4KCjxyZWN0IHg9IjAiIHk9IjAiIHdpZHRoPSIzNTEiIGhlaWdodD0iODEiIGZpbGw9InVybCgjaGF0MCkiIC8+Cjwvc3ZnPg==); /* gradient overlay */
  background-image: -moz-linear-gradient(top, #0061ab 0%, #00335b 100%); /* gradient overlay */
  background-image: -o-linear-gradient(top, #0061ab 0%, #00335b 100%); /* gradient overlay */
  background-image: -webkit-linear-gradient(top, #0061ab 0%, #00335b 100%); /* gradient overlay */
  background-image: linear-gradient(top, #0061ab 0%, #00335b 100%); /* gradient overlay */
}

.panelback {
  width: 351px;
  height: 418px;
  -moz-border-radius: 20px;
  -webkit-border-radius: 20px;
  border-radius: 20px; /* border radius */
  -moz-background-clip: padding;
  -webkit-background-clip: padding-box;
  background-clip: padding-box; /* prevents bg color from leaking outside the border */
  background-color: #dfe0e2; /* layer fill content */
  -moz-box-shadow: 2px 3px 5px rgba(0,0,0,.34); /* drop shadow */
  -webkit-box-shadow: 2px 3px 5px rgba(0,0,0,.34); /* drop shadow */
  box-shadow: 2px 3px 5px rgba(0,0,0,.34); /* drop shadow */
}

The Result

As you can see above, the chunk of code this time is pretty huge, mostly due to the fact that the gradient is converted to a data URL. Below is the result if we paste directly into our code editor.

See it live: Click here

screenshot

As you can see, just as with CSSPs, the elements are merely styled, not positioned, we would have to push them into place ourselves. On that front, the styles look perfect with the exception of the text, which is tiny. I expect this has to do with the fact that I built the Photoshop version on a Retina screen though so you may not experience this bug (CSS3Ps actually did the same thing).

Who Wins?

“I recommend both CSSHat and CSS3Ps over what you get inside of Photoshop 13.1.”

None of the methods for converting Photoshop styles to CSS outlined above are perfect. The Photoshop version works, but the code is pretty ugly and the results don’t utilize the advanced CSS3 techniques that you’ll need to match things like opacity and complex border-radius setups. CSS3Ps is free and performs better than Photoshop, but the method of turning you to a web page that is hidden behind a twenty second ad delay is pretty annoying.

CSSHat is the best in the bunch as far as customization, but it doesn’t support layer groups. The default Photoshop method is the only one that positions your multiple items in a way that matches your canvas, which could be a good or bad thing (I wish it were an optional feature). Ultimately, nothing is going to give you the accuracy, power and versatility of coding by hand, but these tools can get you off to a strong start and save you some serious time.

Personally, I tend to favor CSSHat in this bunch. It’s a little pricy, but the functionality is stellar. It’s frankly a lot closer to what I wanted to see from Adobe. I think they really dropped the ball on this feature and I recommend both CSSHat and CSS3Ps over what you get inside of Photoshop 13.1.

What Do You Think?

Now that you’ve seen my assessment of these three tools, it’s time for you to chime in. Which of the above methods have you tried? Which do you think is the best? Let us know in the comments below!

50 Amazing Resources for Dribbble Lovers

Here at The Site Slinger, we’re huge Dribbble fans. Sort of a Twitter for design, this awesome site is home to beautiful bite-sized work samples from the web’s best designers.

screenshot

Here at The Site Slinger, we’re huge Dribbble fans. Sort of a Twitter for design, this awesome site is home to beautiful bite-sized work samples from the web’s best designers.

To showcase our love for Dribbble, we’ve put together a collection of fifty fantastic resources for anyone and everyone who uses Dribbble. From open source developer projects and quirky web projects to desktop and mobile applications, we’ve got enough Dribbble goodness to keep you occupied for months.

 

Developer

Dribbble API

The official Dribbble API documentation. If you’re a developer and you want to build anything related to Dribbble, start here!

screenshot

Jribbble

Jribble is a jQuery plugin that opens up various aspects of the Dribbble API. Grab shots, users, comments, rebounds and more.

screenshot

Rebbbounds

If you want to keep an eye on what developers are doing with the Dribbble API, hit up Rebbbounds, a Tumblr blog that’s chock full of great examples.

screenshot

GitHub Goodies

There are a ton of Dribbble related projects on GitHub, here’s a quick list of some that you should check out.

  • dribbble-php – PHP wrapper for the Dribbble API.
  • swish – Ruby wrapper for the Dribbble API.
  • Dribbble.js – Dribbble.js is a one file, library agnostic javascript file that will add your most recent dribbble shots to your website.
  • dribbble_desktop – A ruby script that scrapes rss feed of “shots” from dribbble.com, puts the images in a folder, generates an html file that you can load using WebDesktop. Poof – dribbble shots tiled nicely on your desktop.
  • Objective-Dribbble – A wrapper for the Dribbble API, written in Objective-C.
  • dribbble-codeigniter – Dribbble API Library for CodeIgniter.
  • Dribbble-node – Client API for Dribbble web site in node.
  • dribbbleCFC – ColdFusion wrapper for the Dribbble interface showcase API.
  • dribbble-dotnet – A Mono and .NET library for the Dribbble API, built using C#.
  • Dribbble-Sync – Drupal 7 module that syncs shots from Dribbble.
  • Dribbble-Retinizer – Chrome and Safari extensions that add a few nifty retina features to Dribbble.
  • dribbble-sass – Sass demo for Dribbble Show & Tell.
  • dribbble-dimmer – Chrome extension that enables the viewing of shots over a dimmed background.
  • Dribbble_Wrapper – Dribbble Wrapper takes the mobile Dribble website and put it inside phone gap to create a native android application.
  • dribbble-screen-saver – Pulls down popular shots for easy use in a Mac OS X “picture show” screensaver.

WordPress Plugins

WP Dribbble Shots

Adds a template function that grabs the most recent shots from the Dribbble user of your choosing.

screenshot

RainyShots

Similar to the one above, this plugin returns an array of 15 recent shots from any player.

screenshot

Web Apps

Liiikes: Top Players

Liiikes is like a Dribbble scoreboard. It shows you the statistics for all of the major players and scouts (recruiters).

screenshot

Jump Ball

A simple and fun memory matching game built with the Dribbble API.

screenshot

Nibbble

Nibbble is a web app, but it’s specifically built to allow a better Dribbble viewing experience for the iPad.

screenshot

Who Drafted Who?

Type in a Dribbble username, see who drafted that person.

screenshot

Box Seat

Box Seat is a no distractions, one-at-a-time shot viewer with keyboard controls.

screenshot

Full Court Shots

An infinitely scrolling grid of recent Dribbble shots. Great if you need a quick shot of design inspiration.

screenshot

Alley Oop

Search Dribbble by color. Really helpful if you have one color that you like and want to find some others to complement it.

screenshot

bbbrowser

Another simple grid full of Dribbble shots. This one doesn’t require scrolling though, just load up the page and watch.

screenshot

Mac Clients

Play by Play

Play by Play is the Dribbble client that I personally use the most. It has the feel of a desktop Twitter client, only it’s full of Dribbble shots. What could be better?

screenshot

Dribbbler

Dribbbler isn’t meant for viewing shots but for making them. Drag it over the area you want to shoot, click the button and upload.

screenshot

Nibbble — A Dribbble screensaver for OS X

Love Dribbble? Why not make it your screensaver? Mac users can do just that with this free software.

screenshot

iPhone Clients

iOS developers have definitely embraced Dribbble and its API. There are quite a few really sharp iPhone clients. Here are the ones that I found.

As far as I can tell, they pretty much all share most of the basic Dribbble browsing and interaction features. It really comes down to which interface you like the best. I personally think that PlayBook is pretty slick. It’s also free so it’s a good place to start.

Asssist for Dribbble

screenshot

Shotz – A Dribbble Client

screenshot

Swish

screenshot

Balllin ~ a Dribbble client

screenshot

PlayBoook

screenshot

Backboard

screenshot

Travveling for Dribbble

screenshot

Air Ball App

screenshot

Dunk

screenshot

Drishots

screenshot

Alley Ooop – A stream of inspiration shots from dribbble

screenshot

scoreboard! (coming soon)

screenshot

iPad Clients

Dribbble on the iPad is an entirely enjoyable experience. The large screen and touch interaction makes for an unrivaled browsing experience. It’s definitely one of my favorite ways to keep up on recent activity.

If you’re looking for a suggestion, the first two are my favorites. Dribbblr is from Tapmates so you know it’s awesome and Pick’n’Roll is just gorgeous.

Dribbblr for iPad

screenshot

Pick’n’Roll for iPad

screenshot

Courtside for iPad

screenshot

Dribbbits for iPad for iPad

screenshot

Dribbble Flow for iPad

screenshot

Android

Not an iOS user? Fear not, there are a couple of good Android Dribbble apps as well. Check them out below.

Pixle for Dribbble – Android

screenshot

Asssist | The Dribbble client for Android powered devices

screenshot

What Did We Miss?

This collection includes the absolute best Dribbble resources that I was able to find, but I’m sure that I missed a ton of great stuff. Leave me a comment with a link to your favorite Dribbble app, service or code project. Also be sure to let me know what you think of the resources above.

Do We Still Slice PSDs?

The other day a friend of mine said something that caught my attention, “I’m trying to learn how to slice a PSD.” It’s a simple enough statement. As soon as he said it, I knew exactly what he was talking about, and yet, there was something in there that didn’t quite set right.

 

screenshot

The other day a friend of mine said something that caught my attention, “I’m trying to learn how to slice a PSD.” It’s a simple enough statement. As soon as he said it, I knew exactly what he was talking about, and yet, there was something in there that didn’t quite set right.

Upon seeing my hesitation my friend responded with a question, “Do we still slice PSDs?” Great question! For beginners, jargon isn’t merely jargon, it implies a process and suggests a method of action. For this reason, it’s often helpful for more advanced developers to define their terms in a way that is meaningful to others. Today we’ll dive into the theory behind the process of converting a PSD to to a web page and end with a discussion on the ups and downs of designing in the browser.

 

Our Sample File

We won’t be actually converting a PSD to HTML/CSS today, we’re merely discussing the how and why so you can fully understand the typical approach taken by today’s web designers.

I needed a PSD to reference throughout the article so I grabbed the awesome free Creative Studio Minimal PSD from GraphicsFuel.com.

screenshot

What Is Slicing?

The first thing we should talk about is what it means to “slice” a PSD. Put loosely, the term simply means to chop up your Photoshop document into pieces, which then get served up to the web server, put in order by HTML and styled/positioned by CSS.

On a more specific level, slicing can refer to a specific set of tools inside of Photoshop. Using the Slice Tool, we can partition our document up into little pieces. Basically, we just draw a rectangle around every item that we want to separate into an individual image.

screenshot

Why Slice?

The slicing tools in Photoshop are merely there for convenience. There are a ton of great web designers today that never touch them and there’s nothing wrong with that.

The point behind the slicing tools is to make the process of saving out a bunch of images easier, both in the short run for the initial build and in the long run to make revisions. Basically, what it does is save you the trouble of cropping out each portion manually and saving it.

Though the process is kind of a pain, I have to admit that a nicely sliced PSD is a thing of beauty. Here’s a clear example where I have several elements that need to be saved out as images. Without slicing, each one of these would represent a crop and save process that I have to go through.

screenshot

When they’re sliced though, a single Save For Web action can convert all of thes slices to standalone image files. This really cuts down your time on the repetitive task of cropping and saving if you’re working with a single Photoshop file as your source.

screenshot

Make Slicing Suck Less

If you’re still unsure about the Photoshop slicing tools or think that it’s all a big fat waste of time, you should check out our piece titled, How to Make Slicing Suck Less: Tips and Tricks for Slicing a PSD.

In that article, I thoroughly explain the process of slicing and how all of Photoshop’s slicing tools work. Most importantly, you get a look at some great tips on how to make the process of slicing much better. Things like Layer Based Slices and hiding Auto Slices really go a long way towards making it a bearable process.

Why Slicing Is Old School

So that’s slicing. Now that you know what it’s all about, it’s time to explore how this process has changed over the years to a point where slicing is a fundamentally different activity than it used to be.

Once upon a time, no one used CSS (I know, the horror!). Even when CSS did come along, the tools that it provided web designers with were pretty limited compared to what we know today.

Consequently, websites that tried to push the limits by not looking like crap tended to use a ton of images. Every time a design contained a custom font, simple gradient, drop shadow or rounded corner, an image had to be used to pull the effect off in the browser.

Consequently, slicing was a big deal. When you created a Photoshop mockup of a website, if you decided to implement any sort of aesthetic icing, which was huge before the minimal kick we’re on now, then you had to slice every little portion of your design up into tiny pieces that you likely then used HTML tables to reconstruct. Brutal right? Especially when you consider that we were all on amazingly slow web connections back then so all those images took ages to load.

CSS Kills The Image

As CSS evolved and grew, a new trend popped up in web design: imageless design. If you looked around on design blogs a few years ago you would see a ton of articles titled something like, “Create a Fancy Button Without Images!” To this day you still see titles like this pop us as people perform unbelievable feats with CSS.

This trend wouldn’t be possible without the amazing CSS features that we now enjoy. Suddenly you can round corners, add shadows, implement multiple backgrounds, build gradients, use custom fonts and a lot more using pure code. The general goal of many web designers now is to leverage CSS and use as few images as possible in our markup. “Imageless” isn’t necessarily something to be achieved (you almost always need a few images) but rather strived for, meaning you generally want to get as close to it as humanly possible while keeping support high.

Pros and Cons of Imageless Design

This trend comes with its ups and downs. The up side is that, despite what non-coders might think, CSS is a beautifully easy way to maintain and adjust a design in the long term. If you want to change something small such as a font or a background color, you just find/replace a few lines of code and you’re good to go. There’s also the benefit that even thousands of lines of CSS can be minified to the point that its effect on loading times is nearly negligible.

The huge, not to be understated downside is compatibility. With images, PNGs were pretty much the only thing we had to worry about (aside from loading times of course). Now with CSS we have support issues across the board. Browsers that do support a new feature do so only with a unique prefix, making for ridiculously repetitive coding, many features are only available on a single browser engine, others are supported everywhere but IE (some things never change); it can be a real mess.

The ultimate goal is to keep what’s best for the user in mind. If using an image for something results in the greatest amount of good for the most people, go for it.

Less Images, Less Slicing

Building on this foundation of information, we can finally address the question of whether or not web designers still slice PSDs.

For the most part, when we look at a Photoshop document that is meant to be converted to a website, we try to see code wherever possible. It’s like that moment in the Matrix where Neo looks around at what he once saw as the normal world and suddenly sees the code behind it. Web designers don’t see layers and layer effects, we see divs and CSS properties.

Given that this is the case, the majority of the work involved in taking a static design live is more in the realm of rebuilding than slicing. Instead of slicing that glossy button and serving it up as an image, I’ll use CSS to rebuilt it from scratch. This process is repeated throughout the whole of the site, often with images used primarily for actual content rather than design (though there’s still plenty you can/shouldn’t do with pure CSS).

Designing In The Browser

The question that no doubt comes to the mind of many web design newbies as they read about this process is of course, “Isn’t this all a bit repetitive?” First you design and build a site in Photoshop, Illustrator, Fireworks (yes, I remember that Fireworks is great for web content so don’t yell at me in the comments) or any other layout tool of choice, then you basically start over in the browser and rebuild what you just created using code instead of images wherever possible.

The answer is a resounding “yes.” The result is a movement of folks that encourage moving the design process right to the browser. Start in code, finish in code, use Photoshop only when you need to create an image and virtually eliminate all this repetitive nonsense.

I’m all for this process. It’s super lean and really streamlines your workflow. Unfortunately, it’s not always easy to get the creative side of your brain to produce your best work utilizing this method. Sarah Parmenter recently addressed this problem in her post, “I can’t design in the browser” in which she reveals the “guilty secret” that even though Photoshop isn’t a good way to display the kind of dynamic and responsive web content that clients need today, it does foster more creativity than going straight to HTML and CSS.

How Do You Design Websites?

This post represents a long answer to what seemed to be a simple question. However, under that question is something that we’re all struggling with lately, from beginners to professionals: What’s the best process for designing a website? Should the creative design process be distinct from the coding process or should they be one and the same? Should we build mockups in a layout application and then slice them up for the browser or is there a better way? Is Fireworks really the answer or is there still a missing solution?

I want to hear your thoughts on this. What does your current workflow look like, from beginning to end? Where do you begin the design process and how does that flow through to a live website? What tools do you find invaluable along the way? What would your ideal web design tool be like?