I'd be curious to know myself. It's getting to be a pretty noisy feed, and I'd love a version with only front page stories.

I work in Consulting, and my firm had an interesting constraint of needing to make the process of building pattern libraries scalable to multiple teams on multiple projects.

We built a tool called PatternPack which allows you to:

• Build the interface
• Document it in a static site generator
• Share the code across multiple applications

It's working very well on several of our clients. If you're interested, check out the Quick Start.

+1 The Dell Ultrasharps are pretty highly regarded. Some reviews I've seen even say they use the same panels as the Apple. They recently refreshed their 27" model: http://amzn.to/19JZ23D

If you don't care for a warranty and possibly dead pixels, Jeff Atwood advocates for Korean alternatives that run in the $300-$400 range: http://blog.codinghorror.com/the-ips-lcd-revolution/

You're thinking about this backwards: that you have an "idea" and then need to push it to an audience.

Your job should be to find a very specific audience, research their pains and dreams, and then build something that addresses those.

I'm not sure that another generic anonymous texting app is doing that - find a niche it can target and help them solve their problems.

I think that's where you might be spending too much time in Photoshop! The idea behind my article is that you'd lay down your initial visual styling in your design tool of choice, but then build that component in code where you could test it at various responsive levels.

The idea is not to "easily deploy" pixel perfect comps across dozens of comps.

The idea and process for design is spot on: that's how designers should be thinking (i.e., reusable components across pages).

But you're going to hurt any time you ask a design app to generate your HTML/CSS for you. This is where an effective front-end developer comes in handy: you need to have someone write this stuff in DRY, re-usable components that are well organized and documented.

Cutting that corner is only going to hurt you in the long run because you'll have awesome Photoshop files and bad code.

How do you structure what's in there?

Ideally you're not throwing PSDs over the fence to your dev team, but instead have a designer that can be involved in the front end dev process.

I've had a lot of luck recently with building out pattern libraries for projects where new components in a design get built and styled independently of the pages. It's like building your own Bootstrap for every project.

The other upside is that building independent, reusable components in CSS leads to much more maintainable code in the long run than the "slicing PSDs" approach.

Thanks! I just saw this code ope' sourced.

Echoing the other comments so far that you need to decide what you are wanting to build. There's probably two good answers:

First, do you know HTML/CSS? That's going to be a prequisite of anything, so if you don't already, get learning it! Codecademy has a good web track for free.

Assuming you know HTML/CSS:

If you want to build out the interfaces you are designing, JavaScript/jQuery is your friend. If you are only doing design and can move to being able to build out an interface with HTML/CSS/JS, it doubles your value you can deliver, and it helps to know what you are designing for.

If you mostly want to build out a full application, I can't recommend Rails enough. You'll get Node.js recommended a lot these days, but you can't beat the amount of resources there are out there for it. Railstutorial is free, and the best full stack development tutorial I've seen in any language/framework. It'll teach you source control, front end, and more. If you're new to development, I'd suggest just copy and pasting the Rspec testing stuff - it'll confuse you the first time through.

Then just get working on a small project. Even small projects will have difficult hangups that you'll have to learn to work through.