miniblog.

I'm writing some docs in markdown, and I'm really glad I can use arbitrary HTML when I need to. It's so handy when you hit the limits of markdown (e.g. tables, named anchors, custom styling). It's dangerous when you have untrusted input, but I'm beginning to appreciate it.

A common UI antipattern is to make the structure directly reflect the implementation. If you have 4 database tables, you build 4 screens. This may not reflect how users want to get things done. Does this happen outside of software? I suspect it does, but I can't find examples.

I've added some new keybindings to deadgrep.el, so I split the shortcut tables into two categories: https://github.com/Wilfred/deadgrep#keybindings I've done this purely by intuition. Are there good rules or heuristics for deciding when more hierarchy is needed in information, I wonder?