I know this is a joke, and I get it, but: Generally, the NixOS feature discovery/troubleshooting/documentation workflow should not involve Google. It should s

I know this is a joke, and I get it, but: Generally, the NixOS feature discovery/troubleshooting/documentation workflow should not involve Google. It should start with a NixOS Options Search on search.nixos.org, where for most software projects the search will also end when you turn up a one-liner (or close to it) that enables your desired service or sets your desired configuration. Then if you need to know more, check the NixOS manual and maybe the Nixpkgs manual. If those things don't (quickly!) answer your question, then it's time to start Googling, checking the wiki, grepping through the Nixpkgs codebase, asking on Discourse or Matrix or IRC, etc. Just wanted to note that here even though you were joking because that search order is a super simple way to make using NixOS a lot more enjoyable and less painful. Most NixOS users settle on a flow similar to that over time, but if you use that search order from the start, it'll help keep things fun. :)