Recent versions of Hugo have changed the default Markdown parser from
blackfriday to goldmark. The plainIDAnchors setting for blackfriday
told it to use GitHub-style IDs for anchor links. goldmark does this
by default, so there should be no change in behaviour by removing this
obsolete setting.
Recent versions of Hugo have changed the default Markdown parser from
blackfriday to goldmark. The hrefTargetBlank setting for blackfriday
told it to make all external links open in a new window/tab. goldmark
has no equivalent to this setting, so this functionality has been
lost, but there's no point keeping this setting around when it isn't
doing anything.
.navbar-links is designed to always be aligned to the right.
Currently, this is achieved by putting it as the second element inside
a flex container with justify-content: space-between, which pushes it
over to the right. But that doesn't work when it's the only item in a
flex container, because the flex items still start at the left. To
resolve that case, we can set margin-left: auto. This has no effect
in the multiple-element case, but solves the problem when
.navbar-links is an only child.
This option is unhelpfully called "unsafe". The reason for this (and
for it not being on by default), is that Hugo's BDFL is worried that
with "content contributed from millions of people on the interweb (via
PRs and similar), it's pretty easy to envision that that editor will
let some unsafe content slip through and deployed". I don't think
that's really relevant to us.
Allowing HTML markup means we can use semantic HTML like the <address>
element, for which there is no Markdown syntax.
[1]: https://github.com/gohugoio/hugo/issues/6581#issuecomment-562102816
This is a work-in-progress state of affairs, namely it changes the way
that RPC core components (aimed at qaul developers) and SDK
components (aimed at application developers) are identified. This
commit also breaks user storage (search for `todo!()`) which means
that this state needs to be fixed before being usable again.