Currently, despite intentions, the href in the hyperlink to the each subpage is formed by appending .html to the basename.
That is fine as a default, but we want to allow users to have an explicitly stated href in the content.yaml that will take precedence.
To fix this, we will need to fix the Jinja pages.html template too, which always creates the href by appending .html to the basename.
The easiest solution may be to iterate through the (currently named) pages dict and wherever the href key is missing, insert basename + .html.
That will also obviate the need for the dict get call for the homepage href inside the template render function.
Currently, despite intentions, the href in the hyperlink to the each subpage is formed by appending
.htmlto the basename.That is fine as a default, but we want to allow users to have an explicitly stated href in the content.yaml that will take precedence.
To fix this, we will need to fix the Jinja pages.html template too, which always creates the href by appending
.htmlto the basename.The easiest solution may be to iterate through the (currently named)
pagesdict and wherever thehrefkey is missing, insert basename +.html.That will also obviate the need for the dict get call for the homepage href inside the template render function.