Useful Terms for PSD to HTML Services

We know how important effective communication is for our clients on any web development project. So, we’re offering up this handy ‘glossary of terms’ that you will find helpful for your next PSD to HTML project, or if you’re just beginning to learn about the design-to-code process.

We know how important effective communication is for our clients on any web development project. So, we’re offering up this handy ‘glossary of terms’ that you will find helpful for your next PSD to HTML project, or if you’re just beginning to learn about the design-to-code process. This list of web development definitions is especially helpful for creatives and designers who are migrating from print to the web space.

PSD to HTML Definitions

  • PSD to HTML – PSD to HTML is the process of taking Photoshop design files (“PSDs”) and coding them into HTML. Each PSD design file is hand-coded by a front-end developer. No code generators or automation here, pure hand-coded HTML and CSS goodness!
  • PSD – A Photoshop design file. Technically, it stands for Photoshop Document. Photoshop is the tool most widely used for web design and development and works best the design-to-code process. A “good” PSD is layered, well organized using folders, as well as layer comps to show different pages and states.
  • HTML – HyperText Markup Language. This is a simple way to refer to HTML5, CSS, and  JavaScript, the basic languges of the Web. This is the code that makes your design function as  website. Read more about HTML5 on our blog post.
  • Design to code – This is the general term for converting the visuals (design files) into code (HTML). Technically, not all design to code involves PSD files, and other filetypes like PNG and Adobe Illustrator’s AI filetype are acceptable in some cases.
  • Email template – This is the theme for a reusable email employed by businesses with an email marketing campaign. We take designs for email templates and code them, just as with a website.
  • Bootstrap  – Bootstrap refers to the Twitter Bootstrap framework, a responsive front-end development framework that is sleek and powerful. Especially useful for application development teams, it allows you to design and code in a consistent and reliable manner based on a grid which adapts to a user’s screen size, such as smartphones. It’s one of our favorites. Read more about it on the official page.
  • Responsive – The feature of being adaptable to various screen sizes, usually at least 3 breakpoints: desktop, tablet, and mobile device. Recommended widths for responsive websites are 1024px, 768px, and 320px, respectively. We break it down in further detail in this post. While Bootstrap is a favorite, we also work with Foundation, 960gs, and others.
  • WordPress – The most popular, and arguably most powerful, content management system (CMS). With SEO friendly URL management and easy page templating, WordPress is a great choice as a platform for your website.
  • jQuery – The most widely used front-end JavaScript library used to implement animation and functions such as dropdowns, tooltips, sliders, lightboxes and more.
  • Pixel perfect – The highest standard for execution of the PSD to HTML process.We aim to have our deliverables match, down to the pixel, your designs as you presented them.
  • Pop-up modals – A ‘page’ that pops up or otherwise animates into the screen upon completion of a certain action, like a button click.
  • Long page – In line with modern web design trends, we often see long pages with aim to put as much information into a page as possible, usually in the form of horizontal sections. These can be considered as two pages for coding purposes.
  • Slice – Basically, this means cutting up your Photoshop design into pieces, which are then put in order by HTML and styled/positioned by CSS. Read more about slicing on our blog post.
  • NDA – Non-disclosure agreement. We abide by NDA as a standard practice and guarantee that information about you or your project will not be made public. As this is our default policy, there’s no need to sign an explicit NDA, though we are happy to do so if you feel this is absolutely necessary. Your privacy is key, so we offer our products as white-label.
  • White-label – We produce the code for your organization, but do not brand or otherwise sign our markup in any way.
  • Markup – This is the code that we present back to you once we’ve converted your PSD files. ‘Markup’ refers to the finished product in the PSD to HTML process.
  • W3C – Shorthand for The World Wide Web Consortium. This is the international community that develops open standards to ensure the quality and growth of the Web. Our code complies with the standards established by this organization, which can reviewed here. They also offer a markup validation service.

If there’s anything else you need clarified, please let us know. We’re happy to add to this list to make the PSD to HTML process easier!

How to Use Photoshop Layer Comps

If you’re one of those designers who prefer to design within a single master PSD file, while still being able to reuse elements and see design variations, then you’ll find the Layer Comps feature of Photoshop particularly useful. For comparing different design variations, don’t waste your time remembering the different layer positions, visibility states, and layer style settings. Keep your workflow efficient and your file easily deciphered by your developer, client or project manager.

If you’re one of those designers who prefer to design within a single master PSD file, while still being able to reuse elements and see design variations, then you’ll find the Layer Comps feature of Photoshop particularly useful. We know we do with our PSD to HTML projects.

For comparing different design variations, don’t waste your time remembering the different layer positions, visibility states, and layer style settings. Keep your workflow efficient and your file easily deciphered by your developer, client or project manager.

Enter Layer Comps

Layer Comps are an underused and incredibly helpful feature Adobe introduced in Photoshop CS. Layer Comps, or compositions, allow you to create and manage variations of your design without having to resort to multiple PSD files. Simply put, it gives you a snapshot of a state of the Layers panel. For web designers, this lets you clearly define what a page state should look like. It will also allow your developer the convenience of quickly moving between views, or referring back to the original state, without toggling the visibility of layers or shifting layer positions.

How to create a Layer Comp:
1. Adjust your layers into the design variation you want to save
2. Open the Layer Comps window (Window>>Layer Comps)
3. Click the ‘paper’ icon to “Create New Layer Comp” and name it
4. Repeat these steps for all variations you’d like to later view and manage

Options you can set for Layer Comps:
• Layer visibility – show or hide
• Layer position – save the position of each layer within the design
• Layer appearance – save the Layer Styles settings applied to each layer

Layer Comps
Image courtesy of Adobe.

We recommend using the Layer Comps feature of Photoshop for your PSD to HTML projects so you can communicate your design more clearly, and developers can easily see the variation or different page states. If you wanted to later, you could even save the Layer Comps into individual PSD files (File>>Scripts>>Layer Comps to Files), so there’s no loss in flexibility there. The organization of your designs and shareability of the PSD file will be improved, and your client, project manager and developer will love you for it!

You can read more about the specifics of using layer comps directly from Adobe, here.

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!