• Vince SchwidderVince Schwidder, over 2 years ago

    Super interesting Zander, I'm always on the lookout to improve these processes in our team too. I have a question in regards to your naming conventions.

    On the one hand you mention for files and folders "We use clear, descriptive names that refer to the part of the app and the flows it contains.". However, when it comes to artboards you mention "We don’t use descriptive names for our artboards, we number them instead.".

    1. Do you feel those contradict?
    2. How do you explain the purpose of an artboard to your team without a descriptive artboard name?
    2 points
    • Zander BradeZander Brade, over 2 years ago

      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 :)

      2 points