Naming components via 'handle' makes variants two directories deep

We’ve chosen to name each of our components index.njk and supply the handle property for Fractal to resolve. This seems to force an unwanted second level of nesting when viewing variants of components:

We only want the top-level ‘Page Description’ in the screenshot above and can’t see a way around it in the docs?

[dkhuntrods]

@davidpmccormick Ok, what’s happening here is that as far as Fractal is concerned, this is a collection called ‘Page Description’ (the top level folder) with a component inside it called ‘Page Description’. Because the template file has a different name than its folder, Fractal has no way of knowing that they’re associated. Adding a handle allows you to give what would normally be an ‘Index’ component the same name as the folder, but it doesn’t directly associate it. Unfortunately, while this doesn’t help you right now, we’ve got some plans for future updates that should make this easier in future!

[dkhuntrods]

Hi @davidpmccormick, apologies we’ve taken so long on this. I’m going to take a look at this today.