Thanks for your plug-in, I've tried it on a large project with many screen variations and levels.
It would be nice to be able to have a tag for levels in the name rather than relying on the exact artboard name. This way you could be more specific about where a screen sits within a hierarchy and still have more flexible naming conventions.
An example might be:
- Your designing screens for project management software
- each project has tasks and each task has subtasks
- You can view the tasks from the projects page through either a list or grid view
The hierarchy looks like:
Projects/Tasks-list-view
Projects/Tasks-grid-view
Projects/Tasks-list or grid view/Task details
Currently even though Task details is on the 3rd level down it's relation to the variations of the views isn't displayed well.
Another example for naming convention is again for variations
If you wanted to have say an admin view and a user view variations of screens it becomes complicated to figure out how to nest and name the artboards in the current iteration of the plugin.
e.g.
Projects > Tasks-list or grid view > Task details (Admin view) > Subtask details (Inline errors)
Would be done something like:
Projects/Tasks-list/Task details/Admin view/Subtask details/Inline errors
This becomes cumbersome when really it should be more like:
Projects/Tasks-variations/Task details-variations/Subtask-variations
I hope this feedback is helpful.