Live data from Hacker News

Show HN: Github for Designers

pixelapse.com

71–80 of 85 posts

Re: Show HN: Github for Designers

#71
How do I fork a design? Can I make another layer and merge it into the PS file so that others can tweak my changes?

Just ideas that popped into my head looking at this. It's pretty awesome, great job!

Re: Show HN: Github for Designers

#72

I've been thinking about how a GitHub for designers would work. This doesn't quite seem like "it" to me. Don't take that remark the wrong way, I like what's been done here. It's well designed and I could see a use for it. But that's just it, I have to find a use for it. It isn't immediately obvious to me. I'm not the typical designer as I don't have clients and my job isn't 100% design but I have been designing every…

I agree with you on the collaborative part. Add in a "deviantart" component, and you got a killer product for designers.

Re: Show HN: Github for Designers

#73
I would be interested in fooling with this, but I'm an Illustrator addict! Photoshop used to be basically what hosted my scanner drivers, and now that I do most of my work direct in AI, and TWAIN seems to be a dead standard, I don't even use it for that.

Re: Show HN: Github for Designers

#75
I store all my designs in dropbox. This has worked pretty well. If I need a design I just go into dropbox and grab it and make changes to it. It works, but I'm guessing their is a better way. And when I need feedback I use a combination of droplr and instant messaging. Their is definitely room for innovation.

Re: Show HN: Github for Designers

#77

I would be interested in fooling with this, but I'm an Illustrator addict! Photoshop used to be basically what hosted my scanner drivers, and now that I do most of my work direct in AI, and TWAIN seems to be a dead standard, I don't even use it for that.

Hey there! We didn't mention it in the demo but Pixelapse works with Illustrator files as well.

Re: Show HN: Github for Designers

#79
post #71

How do I fork a design? Can I make another layer and merge it into the PS file so that others can tweak my changes? Just ideas that popped into my head looking at this. It's pretty awesome, great job!

I think this is the key part of git's workflow that improves on older simple versioning systems. the fork and merge model is really needed in other spaces too.

I wonder if it would be possible to turn design files into something textual to leverage git's builtin merge capabilities?

Re: Show HN: Github for Designers

#80
Love it but I fear it's not the right solution and I even don't think it's the right problem it's trying to solve.

When a designer is working in photoshop they are not actually part of the development process yet. They are still in design mode, they are for the lack of a better word sketching.

Not until they start to actually output assets for developers do the github concept start to make sense.

Designers often have different versions of the same design inside the document in the layers and groups and smart objects.

They will for instance have a couple of version of a header or some styling on their elements, perhaps different layout for main content.

So for this to be useful it would need to create a kind of master psd that save the state of which layers and groups are turned off and on.

This way you can sketch away and not have to worry about creating a billion different versions inside the documents that just make them bigger.

But that is a different problem.

Post reply on HN