Indentation of root level patterns in navigation confusing

[renestalder]

I am using Pattern Lab Node v5.15.0 on Linux, with Node v16.0.0, using a Vanilla/Twig Edition.

The visual hierarchy of the menu items is off due to the used indentation.

Expected Behavior

The patterns on the first level in the navigation should be in one line with the groups/folders of that level. The next level then should have the indentation.

Actual Behavior

Both level of items have the same indentation, thus seems to be in the same visual hierarchy, while in reality, they are not.
Users aren't able to visually distinct the items of the group/folder "tag" from the rest of the elements that are outside of the group.

Steps to Reproduce

1. Create an example pattern_patterns/test/test-1.twig and an example pattern _patterns/test/test-group/test-2.twig.
2. See the result listed in the navigation as "Test", with a group "Test Group" and an item "Test 1".
3. Expand "Test Group" to show the item "Test 2".

[mfranzke]

@renestalder thanks a lot for this important and well-documented issue.

Do you have the chance to even also analyze the problem further and provide a solution via a pull request?
The background of my question is that this project is mainly "backed" by the contributions from the community, be it feedback or even bugfixes and optimizations, and the project would highly benefit by spreading the workload over several shoulders. I even also found myself struggling with some issues before and then started to contribute to the product myself; so especially if these are important topics to you, this would heavily speed up the process to bring those into the product as well.
If you can't that's fine too, maybe somebody else could take up those tasks.

[renestalder]

I will take a look at this.

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!