docs planning

[codyopel]

This issue is placeholder for things that need documentation. Any documentation for code that does not live in this repo (e.g. software packaged in this repo) does not belong here, this includes usage instructions for service and software.

• Nix language
  • syntax
  • style guide
  • best practices
  • recursion
• lib
  • functions
  • best practices
• stdenv
  • mkDerivation
    • phases
    • setupHook
    • how Nix variables are passed as environment variables
    • src/srcs
    • buildInputs etc...
    • name
    • patches
    • meta
    • checks
    • hardening
  • target/hostSystem
  • libc
  • cc
  • shell
  • bootstrap
    • how to build bootstrap
    • bootstraping new architectures/systems from scratch
    • additional information
  • overriding phases
  • best practices
  • licences and license options
  • coding practices specific to stdenv
  • setup.sh
    • nesting
    • future plans
  • stateful
• fetchurl & fetchzip
• pkgs
  • all-packages.nix
  • all-pkgs migration (mostly complete, just need a notice until finished)
  • overrides
  • package acceptance policies
  • overlays
  • buildPythonPackage
  • buildGoPackage
  • buildPerlPackage
• services
  • future cleanup/rewrite
• system
  • future rewrite