i hope its okay to reply here as curious, but new person. I just read the notes and the PR for the how to guides and that you decided to not proceed with them. Would it be feasible to make a template instead of a how-to guide? This could provide some help to contributes without tying things down to much.
The reason is that we currently don’t have all that much experience with guides and don’t know exactly enough what to expect from contributors to write it down concisely. We’re currently focused on just doing things together and making any progress at all.
Thats why i thought a template would be easier. I dont think, you need to much in-depth knowledge to create a template, that could be beneficial.
If we already have some proper documentations or how to guides, that meet a certain standard, we could use them to boil down a generalized structure for the template.
if this is just at the bottom of the proprieties, i fully understand. just wanted to ask.
That sounds like a helpful thing to do once we have more experience. An in-between step I’ve considered is the team picks a current how-to guide on nix.dev and recommends mimicking its structure.
Total aside but here are some of my personal reflections on why I closed the PR.
A few years ago, I helped maintain the Rust track for exercism.org. As an OSS team we spent a lot of time and energy upfront trying to build a learning path in abstract. While I personally benefited from that approach, it seemed to slow down progress on the track’s development.
With nix.dev guides, I’m hoping to take a concrete approach. Take a topic, write a guide. Repeat n times. Then, hopefully generalise those observations into useful advice.
great idea tarrens!