4 ms·
I've been working on things to help onboard people. If you wanted something to help onboard you with NixOS, what would you want to see?
by xena 5y ago
I've been working on things to help onboard people. If you wanted something to help onboard you with NixOS, what would you want to see?
- deleted 5y ago[deleted]
- viraptor 5y agoDifferent person, but trying to recall my initial painful experience: "Use case -> how to achieve it", more than "functionality -> how to use it". Nixpills seems to flirt with both concepts, but also is a bit... showing off? Just plain "I've got this app, how do I package it", "how do I overlay it", "why are there 5 ways of doing overlays that people use differently", "what is the actual expected signature of various flake elements", "what packaging helpers are available and how do I find them", ... would be amazing. I have issues with nix docs trying to be clever. For example https://nixos.wiki/wiki/Overlays https://nixos.wiki/wiki/Overlays - "Careful, we're using a different self and super here!" - ok, then name them something more descriptive!
- infogulch 5y agoMaybe nix needs to organize docs around the users intention: https://documentation.divio.com/ https://documentation.divio.com/ The big idea is that it separates types of documentation by its usefulness to a particular user that is approaching the docs with a clear goal. Here the goals are loosely organized along two 'axes': working-studying and theoretical-practical. Personally I think the model is missing a user-developer axis (especially for a developer tool like nix), but overall it's a great lens to view any documentation project through.