I disagree. Pages are a flat concept. (ie: Books do not nest pages within pages.)
Similarly, Artboards cannot (and should not) be nested.
However, it is reasonable to group items with slashes, similar to Component or Style name grouping. (Once again, the styles do not "contain" other styles, they merely group them as a convenience.)
Perhaps Page names could be grouped in a similar fashion, but I think would be better to group Artboard names this way instead, since there are other areas of the app it would be more useful than Page grouping (as when specifying a prototype target). Grouping *both* Page names and Artboard names could be a problem or simply confusing. It would also be more familiar to name Artboards with slashes since it would be very similar behaviour to naming of components. (If instead, it was Page grouping, this would require a larger scale change to the sidebar Page UI and behaviour)
Comments
I disagree. Pages are a flat concept. (ie: Books do not nest pages within pages.)
Similarly, Artboards cannot (and should not) be nested.
However, it is reasonable to group items with slashes, similar to Component or Style name grouping. (Once again, the styles do not "contain" other styles, they merely group them as a convenience.)
Perhaps Page names could be grouped in a similar fashion, but I think would be better to group Artboard names this way instead, since there are other areas of the app it would be more useful than Page grouping (as when specifying a prototype target). Grouping *both* Page names and Artboard names could be a problem or simply confusing. It would also be more familiar to name Artboards with slashes since it would be very similar behaviour to naming of components. (If instead, it was Page grouping, this would require a larger scale change to the sidebar Page UI and behaviour)