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
We then look at the docs (install the hooks, or view static rendered documentation):
nbdev_preview
Expected Behavior
We expect to see the correct fonts and background colors applied to the documentation:
Current Issue
Currently, the _brand.yml is not being copied across from the ./nbs directory, where the _quarto.yml, sidebar.yml and custom.yml are stored, to the ./_proc directory:
While these file can be copied across manually, the _proc directory is temporary, and is unexpected behavior, given the nbdev documentation on website customization:
"file in the same location as your _quarto.yml file to override any values in _quarto.yml"
Possible Fixes
Similar to changes made the the extensions directory, released in 2.3.11, a single line could be added to nbs/api/serve.ipynb:
if (path/'_brand.yml').exists(): files.append(path/'_brand.yml')
In the Quarto 1.6 release, support for a
_brand.yml
was added, based on thebrand.yml
specification.Minimally reproducible example
Creating Repository
A public repository has been made available, with a working Github Pages URL, based on the commands below:
nbdev
repository:_brand.yml
, based on the example given in Quarto's Documentation:Expected Behavior
We expect to see the correct fonts and background colors applied to the documentation:
Current Issue
Currently, the
_brand.yml
is not being copied across from the./nbs
directory, where the_quarto.yml
,sidebar.yml
andcustom.yml
are stored, to the./_proc
directory:While these file can be copied across manually, the
_proc
directory is temporary, and is unexpected behavior, given thenbdev
documentation on website customization:Possible Fixes
Similar to changes made the the extensions directory, released in 2.3.11, a single line could be added to
nbs/api/serve.ipynb
:see: #1484
The text was updated successfully, but these errors were encountered: