Copy the upstream file and change just the necessary parts
to have the same content as before.
Switches to have the main menu declared in Hugo's config file.
Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This is the recommended way to use it now.
Also I couldn't get Hugo to work with Docsy v0.8.0 as a git submodule.
Uses a development branch on my personal fork for now,
until changes are merged in matrix-org/docsy.
Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
* Configure syntax highlighter to use CSS classes
the inline `style` attributes cause CSP errors (and don't work). Instead, we
can use proper CSS classes.
* Configure response headers for Hugo dev server
make the dev server serve response headers which match the live site, for
better testing.
Now that we've dropped the old build pipeline (and an assets directory does not exist in the repo any longer, we can rename the hugo version of the assets (assets-hugo) created during the build tools migration back to simply assets.