-
Notifications
You must be signed in to change notification settings - Fork 136
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
FEATURE: Exclude content from TOC #33
Comments
Hi @timtribers , The features is added to newest version of Epub-gen, you can set option 😉 |
Hi all! Again, I was able to do this by simply leveraging the options for custom OPF and TOC templates, by feeding a bit more 'internal' data into the templates, and making the book 'spine' my way - such as passing a I've got some comments about the config 'API' for this, |
Thanks @cyrilis for the new version. I am just testing it now. The beforeToc is working great, but not sure about the excludeFromToc yet. Also, as noted elsewhere, the images have got broken - but I see someone is on the case. Many thanks for all the good work you guys do on this. |
|
Can confirm @matejcsok-istvan's report, this is happening to me as well. |
Hi all. Nobody feels like the ToC entry in the ToC is somehow ouf of place? I would like have an option like excludeTocFromToc. |
Was having the same issue described by @matejcsok-istvan and @waylaidwanderer. By setting the option Full disclosure, not super familiar with ePub standards / best practices. Nevertheless, here's a workaround that seems ~okay-ish:
to:
and line 67 from:
to:
Excludes the section from ToC but the data still renders in the actual Epub... Again, I'm not sure of the full repercussions of this yet... so no PR. I've also only tested with Mac and iPhone using Apple Books. Maybe there's a better way? |
Hi,
It would be nice to see the features that Nodepub has which allows content to be:
a) excluded from the TOC, and
b) also placed before the TOC
(see: https://www.npmjs.com/package/nodepub#addsection--title-content-excludefromcontents-isfrontmatter- )
This could be by flags added to the content config - e.g:
Thx.
The text was updated successfully, but these errors were encountered: