add more authors and editors to tutorials and guides

Author: fricklerhandwerk

source/concepts/flakes.md

@@ -1,6 +1,10 @@
 (flakes-definition)=
 # Flakes
 
+```{contributors}
+:authors: kiara
+```
+
 ## What are flakes?
 
 Flakes offer an entrypoint file `flake.nix` aimed at sharing Nix code.

source/contributors.yaml

@@ -1,8 +1,26 @@
+djacu:
+  name: Daniel Baker
+domenkozar:
+  name: Domen Kožar
 fricklerhandwerk:
   name: Valentin Gagarin
+grahamc:
+  name: Graham Christensen
 infinisil:
   name: Silvan Mosberger
+kiara:
+  name: Kiara Grouwstra
+  github: KiaraGrouwstra
 mmesch:
   name: Matthias Meschede
 NobbZ:
   name: Norbert Melzer
+olafklingt:
+proofconstruction:
+  name: Alexander Groleau
+rapenne-s:
+  name: Solène Rapenne
+tfc:
+  name: Jacek Galowicz
+zmitchell:
+  name: Zach Mitchell

source/guides/best-practices.md

@@ -1,5 +1,10 @@
 # Best practices
 
+```{contributors}
+:authors: domenkozar
+:editors: fricklerhandwerk, infinisil
+```
+
 ## URLs
 
 The Nix language syntax supports bare URLs, so one could write `https://example.com` instead of `"https://example.com"`

source/guides/recipes/continuous-integration-github-actions.md

@@ -9,6 +9,10 @@ myst:
 
 # Continuous integration with GitHub Actions
 
+```{contributors}
+:authors: domenkozar
+```
+
 Set up [GitHub Actions](https://github.com/features/actions) as your continuous integration (CI) workflow for commits and pull requests.
 
 Nix lets CI build and cache developer environments for every project on every branch using binary caches.

source/guides/recipes/post-build-hook.md

@@ -1,6 +1,10 @@
 (post-build-hooks)=
 # Setting up post-build hooks
 
+```{contributors}
+:authors: grahamc
+```
+
 This guide shows how to use the Nix [`post-build-hook`](https://nix.dev/manual/nix/2.22/command-ref/conf-file#conf-post-build-hook) configuration option to automatically upload build results to an [S3-compatible binary cache](https://nix.dev/manual/nix/2.22/store/types/s3-binary-cache-store).
 
 ## Implementation caveats

source/tutorials/first-steps/ad-hoc-shell-environments.md

@@ -2,6 +2,11 @@
 
 # Ad hoc shell environments
 
+```{contributors}
+:authors: domenkozar
+:editors: fricklerhandwerk
+```
+
 In a Nix shell environment, you can immediately use any program packaged with Nix, without installing it permanently.
 
 You can also share the command invoking such a shell with others, and it will work on all Linux distributions, WSL, and macOS[^1].

source/tutorials/first-steps/declarative-shell.md

@@ -7,6 +7,10 @@ myst:
 (declarative-reproducible-envs)=
 # Declarative shell environments with `shell.nix`
 
+```{contributors}
+:authors: domenkozar, zmitchell
+:editors: fricklerhandwerk
+```
 ## Overview
 
 Declarative shell environments allow you to:

source/tutorials/first-steps/reproducible-scripts.md

@@ -2,6 +2,11 @@
 
 # Reproducible interpreted scripts
 
+```{contributors}
+:authors: rapenne-s
+:editors: fricklerhandwerk
+```
+
 In this tutorial, you will learn how to use Nix to create and run reproducible interpreted scripts, also known as [shebang] scripts.
 
 ## Requirements

source/tutorials/module-system/a-basic-module/index.md

@@ -1,5 +1,10 @@
 # A basic module
 
+```{contributors}
+:authors: djacu
+:editors: fricklerhandwerk
+```
+
 What is a module?
 
 * A module is a function that takes an attribute set and returns an attribute set.

source/tutorials/module-system/deep-dive.md

@@ -3,6 +3,11 @@
 
 Or: *Wrapping the world in modules*
 
+```{contributors}
+:authors: infinisil
+:editors: fricklerhandwerk, proofconstruction
+```
+
 In this tutorial you will follow an extensive demonstration of how to wrap an existing API with Nix modules.
 
 ## Overview