-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for non-link summary items #483
Comments
In particular, I'm going for something like this: https://tokio.rs/docs/getting-started/tokio/ |
What about saying if a summary item's link points to some special value (e.g. I'm not sure how this would interact with the internal representation of a book though. I'm pretty sure at the moment each chapter/item must point to a file... |
All things being equal i would suggest to use standard markdown ontology here. Like in the case of separator items ("=========") we could just add support for standard non-linked list items ("- Some Item" vs "- Linked chapter") |
That sounds like a really nice solution! If we just have a normal list item with text instead of with a link then that's both intuitive and easy enough to handle. It'd probably be easier to implement when we land #409 though. |
Yeah lets reduce some of that technical debt first |
Currently this is not possible.
I'll get this error while running
I would like to have sections without links though..
|
+1 for this. In the Void Handbook, we currently have "sections" like this, which our users find problematic. In a number of cases, we've been able to consolidate information to avoid such sections, but it would be nice to have 'virtual chapters' as described in #592. |
Any update on this old issue? is it possible to create a directory without linking to a page? and without using parentheses () thus making it a non existing item that takes the "--sidebar-non-existant" css? |
I'd like to have a layout like this:
where the top-level chapter items are not links, but rather, each chapter begins with the first subsection.
The text was updated successfully, but these errors were encountered: