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 was recently in a meeting where we were talking about building an end-to-end pipeline for publishing using Jupyter notebooks + md files etc as inputs.
It made me wonder if we could define another TOC format that is designed for a collection of papers. This would essentially be a way to generalize the jb-article format to include multiple papers, so maybe it'd be as simple as:
format: jb-journalroot: indexarticles:
- title: some titlesections:
- The rest is the same as jb-article
- title: some othersections:
- The rest is the same as jb-article
What would be even more interesting is if we could trigger different doctree logic depending on the TOC format. For example, maybe if it's an article, then sections have the option of being concatenated into a single page, rather than existing as unique URLs each (basically, the same behavior as singlehtml but at the level of a toctree rather than for the whole site.
(obviously this is a future issue and not blocking on an early release)
The text was updated successfully, but these errors were encountered:
What would be even more interesting is if we could trigger different doctree logic depending on the TOC format.
well this will already actually the case with jupyterbook-latex; where it will auto-infer the toplevel sectioning based on the format (executablebooks/sphinx-jupyterbook-latex#55)
I was recently in a meeting where we were talking about building an end-to-end pipeline for publishing using Jupyter notebooks + md files etc as inputs.
It made me wonder if we could define another TOC format that is designed for a collection of papers. This would essentially be a way to generalize the
jb-article
format to include multiple papers, so maybe it'd be as simple as:What would be even more interesting is if we could trigger different
doctree
logic depending on the TOC format. For example, maybe if it's an article, then sections have the option of being concatenated into a single page, rather than existing as unique URLs each (basically, the same behavior assinglehtml
but at the level of a toctree rather than for the whole site.(obviously this is a future issue and not blocking on an early release)
The text was updated successfully, but these errors were encountered: