Our team has a standardized naming convention for how we name parts. When we start submitting parts to the app, we want to make this very easy for the user to understand, to make sure we are very consistent as we are naming parts.
Consistently naming parts makes it easy to know what season a part is for, what robot the part will eventually be on, and which part you're talking about! This is critical to a well-organized part system, and we need to make sure to handle this correctly.
[x] Talk to the design team about how they name their parts. Figure out what documentation exists for how parts are named, and make a Google Docs document with all of your notes here
This will be very important - we will eventually have our app handle all of the part namings for our designers, so they don't need to manage this themselves. For us to get to that point, however, we need to understand how parts are named and need to make a system to handle that.
blueskye04
commented
1 year ago
Our team has a standardized naming convention for how we name parts. When we start submitting parts to the app, we want to make this very easy for the user to understand, to make sure we are very consistent as we are naming parts.
Consistently naming parts makes it easy to know what season a part is for, what robot the part will eventually be on, and which part you're talking about! This is critical to a well-organized part system, and we need to make sure to handle this correctly.
This will be very important - we will eventually have our app handle all of the part namings for our designers, so they don't need to manage this themselves. For us to get to that point, however, we need to understand how parts are named and need to make a system to handle that.