doc: point manual contributing guides to devmode's README (#411326)

There's quite a bit of pingpong redirection with Nixpkgs and NixOS
manual utilities. Since devmode was lacking a README, the descriptive
text is moved there and it's referenced by both manuals.

authored by Alejandro Sánchez Medina and committed by GitHub 60264c48 8c35c2b4

+13 -6
+1 -5
doc/README.md
··· 56 57 #### `devmode` 58 59 - The shell in the manual source directory makes available a command, `devmode`. 60 - It is a daemon, that: 61 - 1. watches the manual's source for changes and when they occur — rebuilds 62 - 2. HTTP serves the manual, injecting a script that triggers reload on changes 63 - 3. opens the manual in the default browser 64 65 ### Testing redirects 66
··· 56 57 #### `devmode` 58 59 + Use [`devmode`](../pkgs/by-name/de/devmode/README.md) for a live preview when editing the manual. 60 61 ### Testing redirects 62
+3 -1
nixos/doc/manual/contributing-to-this-manual.chapter.md
··· 37 /**/.direnv 38 ``` 39 40 - You might want to also use [`devmode`](https://github.com/NixOS/nixpkgs/blob/master/doc/README.md#devmode) while editing the manual. 41 42 ## Testing redirects {#sec-contributing-redirects} 43
··· 37 /**/.direnv 38 ``` 39 40 + ### `devmode` {#sec-contributing-devmode} 41 + 42 + Use [`devmode`](https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/de/devmode/README.md) for a live preview when editing the manual. 43 44 ## Testing redirects {#sec-contributing-redirects} 45
+3
nixos/doc/manual/redirects.json
··· 95 "sec-contributing-development-env": [ 96 "index.html#sec-contributing-development-env" 97 ], 98 "sec-mattermost": [ 99 "index.html#sec-mattermost" 100 ],
··· 95 "sec-contributing-development-env": [ 96 "index.html#sec-contributing-development-env" 97 ], 98 + "sec-contributing-devmode": [ 99 + "index.html#sec-contributing-devmode" 100 + ], 101 "sec-mattermost": [ 102 "index.html#sec-mattermost" 103 ],
+6
pkgs/by-name/de/devmode/README.md
···
··· 1 + # `devmode` 2 + 3 + `devmode` is a daemon, that: 4 + 1. watches the manual's source for changes and when they occur — rebuilds 5 + 2. HTTP serves the manual, injecting a script that triggers reload on changes 6 + 3. opens the manual in the default browser