You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would love to use elm-book for a documentation site I am currently planning out but I see no way to deeply nest chapters currently. For example, imagine a sidebar like so for example:
As things stand, it seems not possible to implement such nested groupings, is this understanding correct and if so, is it addressable or is there a reason why it isn't or shouldn't? For me it would definitely be a helpful thing to have the possibility of as the rest of the implementation works like a charm AFAICS so far for the use case.
The text was updated successfully, but these errors were encountered:
@jamesrweb hey! thanks for opening this issue - this is currently not possible but you're right that nothing prevents it from happening on the design. I'm currently working on elm-book v2 and this should be a good thing to add to the features but I don't think it is something to be released in the next month or so (but not much longer than that!)
Is there any kind of roadmap / feature set that is in stone for v2? Would be great to see whats upcoming if there is.
in the next month or so (but not much longer than that!)
So this is probably something you could have released in the next 2 - 3 months is what I take away from that, or have I misunderstood? 😄 (update: I did misunderstand but still 🤷🏻)
I would love to use elm-book for a documentation site I am currently planning out but I see no way to deeply nest chapters currently. For example, imagine a sidebar like so for example:
As things stand, it seems not possible to implement such nested groupings, is this understanding correct and if so, is it addressable or is there a reason why it isn't or shouldn't? For me it would definitely be a helpful thing to have the possibility of as the rest of the implementation works like a charm AFAICS so far for the use case.
The text was updated successfully, but these errors were encountered: