Hi @luisjure
As of 6.0, the template system has been completely refactored. It is the main change that prescribed the major version bump.
-
The default template applied when exporting to HTML now produces the same DOM structure as JupyterLab, and is styled using JupyterLab’s CSS. The pygments theme in use mimics JupyterLab’s codemirror mode with the same CSS variables, so that custom JupyterLab themes could be applied. The classic notebook styling can still be enabled with
jupyter nbconvert --to html --template classic
However, we do not allow for the
custom.css
anymore. -
Nbconvert 6.0 includes a new system for creating custom templates, which can now be installed as packages. A custom “foobar” template is installed in Jupyter’s data directory under
nbconvert/templates
and has the form of a directory containing all resources. Templates specify their base template as well as other configuration parameters in aconf.json
at the root of the template directory. More information can be found at: https://nbconvert.readthedocs.io/en/latest/customizing.html