We have another tool that we use on top of Github that automatically exports our artboards, but aside from that its all pretty vanilla Git.

Right now every designer merges directly to Master and we've managed to avoid issues with conflicts pretty successfully, but I anticipate this will start breaking very soon, so from early next year we'll start requiring designers to work in branches and make PRs when a piece of work is finished.

I do find viewing files through Github a pain in the ass. Do you have any tools or suggestions that could make this easier?

Hey Rob, that is so, so cool – thank you for sharing, I've passed it onto the full design team.

You're right, it's very strict and very opinionated, and will bring roadblocks unless you're willing to work within its parameters. So when we do a public v2 of this (probably mid Jan), we're going to include exactly those things. I think it makes a lot of sense to have these things configurable.

For the moment the source is available on Github if you'd like to manually make the changes.

Thank you very much!

Thanks Vince! So, I was waiting for someone to point this out. To answer your questions:

1: I would argue that they don't contradict. They're different things and their naming conventions serve different purposes. Files/folders are named as such for quick, intuitive access through Spotlight and Github search. Artboards aren't navigated like this, and so we've prioritised their naming for how they are exported and shared, hence the ordered number.

I'd also mention that in a scenario where you're discussing designs, eg. a handover meeting, it's easier for an engineer to say "hey can you go to 503" than "hey can you go to the Account View – Profile Dropdown (Selected) screen", which would lead to ambiguity as to what artboard content they're referring to and where exactly it lives on the page. Obviously a complete hypothetical but hopefully that makes sense?

2: I touched on this a bit here: https://twitter.com/zancler/status/1072792693774970880. Short answer is through communicating in person and via the handover tools we use. Maybe you could also argue that if a screen's purpose isn't clear from looking at it, then its not doing its job anyway. Though I appreciate thats avoiding a whole load of nuance.

Great questions :)

Hey Romain, thanks for the feedback.

With regard to the master page, is it that you wish the name "Master" to be different, or that you don't want the page name validation there at all?

And for margins, I think that's totally fair, maybe a next version could offer configuration of padding, though right now we don't actually have a fixed margin, as its the co-ordinates of the grid that dictate the margin.

Thanks for sharing Artboard Tricks, it looks great and has lots of the same functionality – I'm gonna have a dig around and see how it works!

Yes. It has 1.5 billion monthly active users.

True, though I guess lots of product companies don't want it to be too easy to see their team and each employee's role, as it makes it a lot simpler for other companies/recruiters to know who to get in touch with.

Edit: My bad, this was actually meant as a reply for Daryl's comment. I'm very silly.

From this and your tweets you seem to care a large amount about disliking this website.

Sorry, I should have been more clear. By huge, I didn't mean mass-market, take over the world huge, I just meant enough for Tidal to be potentially sustainable. It's definitely true about Spotify, but I wouldn't assume that they haven't done anything because they've tested and proven it, more likely that there's just never been any pressure. Just a theory though :)

That's definitely a good point that the physical different, even self-claimed experts, would hear isn't even substantial. But the psychological difference of knowingly paying for quality is what would turn people to this product.

As for the bandwidth problem, has this been proven to be a problem yet from Tidal users? Not saying that you're wrong, as it would make sense, but just to substantiate your point with proof before calling BS.