G.Ambatte

It's possible that we could inject a step right before the rendered Markdown gets pushed into the BrewRenderer display element which builds a list of all element IDs in the...

This is an us problem, we render the Markdown one page at a time; I did suspect it would be unique if we rendered the whole thing at once.

PR #3089 renders the whole document at once, so if/when it goes live, heading IDs will be unique throughout the entire brew and persist in the HTML, even when on...

It looks like these changes have caused quite a lot of tests to break. I'll try to look into it in the next few days.

I've pushed an initial pass at a new view type - List  When all groups are collapsed, it reverts to the original styling, so it's still WIP right now.

This is all just styling right now, so the brew groups are unchanged.

> I can also help with the css if you’d like, too— I could create a branch off yours or just contribute it via comment to this branch. I don’t...

> This PR is pretty much forgotten, isn't it? Not forgotten, just simmering in the background. This PR is part of the reason I added a BrewItem icon for brews...

`return {this.updateFilter('tag', tag);}}>{matches[2]};`

I'm getting 406 responses when attempting to get a local image file, which appears to be from the content-negotiation middleware, That said, disabling said middleware does NOT result in the...