Update DS Documentation to use Sketch Naming Conventions best practices for all Sketch files

[josephrlee]

Duplicate check

• [X] I've searched for any related issues and avoided creating a duplicate issue.

This update is for:

Update documentation

What is the name?

About/Naming and About/Designers/Sketch for Teams

What is the nature of this update?

• [ ] How to build this component/pattern
• [ ] When to use this component/pattern
• [ ] When to use something else
• [ ] Usability guidance
• [ ] Accessibility
• [ ] Implementation
• [ ] Research insights
• [ ] Package information
• [ ] Addition to Forms Library documentation
• [ ] Update to existing Forms Library documentation

What problem does this solve?

Add a section to the Naming Convention documentation and the Sketch for Teams page in the About Section for working inside of Sketch specifically. Also, update the Getting Started artboard in the Sketch for Teams Template.

Allows for standardized naming conventions for designers to follow when creating Sketch files specifically for Page, Artboard, and Group names since these are not already defined in the Design System. It will help designers working on the same files to keep things consistent and more readable.

Use these rules defined by the Sketch Assistant:

• Page names should start with an emoji, e.g. 🚧 Work in Progress.
• Artboard names should start with numbers followed by a space, e.g. 1.1 Splash Screen.
• Group names, default names such as Group are forbidden.
• Symbol names should be using forward-slash grouping, e.g. Icon/Frog.

Additional Context

No response

[caw310]

@josephrlee , Would you be able to attend the Design System Council meeting on Friday, April 7 at 1pm to talk about this request? It would be helpful if you could speak to this with the group.

[humancompanion-usds]

@josephrlee - Having some consistency with page names and artboard names makes sense to me. Symbol names are already standardized via the Design System component library. How folks names their groups and symbols seems a bit pedantic. What are the goals here or the problems this would solve?

[josephrlee]

Thanks for following up @humancompanion-usds. As a newish designer on the team and the org, I think it'd allow folks like me to be able to read and digest the files faster especially when looking at other projects' files to see how other teams are approaching problems. If the Group/Symbol naming is too pedantic, then at least the page naming consistency would be helpful to have. Thanks!

[caw310]

Closing as we have migrated to Figma so this should have been addressed. Write a new ticket if this is an issue in Figma.