Morten Piibeleht

I wonder if it is related to #1676?

If dropping in another CSS file would be sufficient, we could add some API where each plugin provides extra HTML assets. Currently we loop over the `.assets` field of the...

Yes, I also think this 4-level approach is a really good way to think about technical documentation, and I think it would be worth advertising in the docs (and same...

> I could do it. Although the first PR is a very minor fix. So it can wait (unless you want to keep PRs for issues strictly separated). Generally we...

Re #1612 PR: why are you looping over the builder pipeline when trying to check for assets? Wouldn't looping over the `plugins` field of `Document` would make more sense?

> Like those functions? Ah, yes. I think I was looking at an old commit the other day. But hmm. A couple thoughts: * For full flexibility, I think it...

@LazyScholar: apologies, I was not active here for a while. I still think a feature like this would be good. Do you think you would have time to revisit this...

Thank you @LazyScholar! And sorry for the delay here. I am actually having a little bit of trouble reviewing this, since I don't have a clear vision of how exactly...

Sorry for not looking into this earlier. I just tried out the latest commit and it looks like I can't reproduce it locally. But it looks like your GitHub Pages...

This would need some way to communicate the preference across multiple domains, which, I believe, is not possible with [Web Storage](https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API) which we currently use.