| 29 Jun 2023 |
 fricklerhandwerk | Here's another piece for the survey regarding contributor workflow: https://floxdev.com/blog/nixpkgs-contribution | 22:37:45 |
| 30 Jun 2023 |
 sterni | why can’t nobody at flox proofread such articles (if they are even wise to publish in that context)? Couple of inaccuracies and multiple things that are wrong presented as facts. | 07:36:05 |
|  jakob joined the room. | 08:33:28 |
|  ruby changed their profile picture. | 14:02:47 |
 Sandro 🐧 | FYI https://github.com/NixOS/nixpkgs/pull/240754 | 16:15:47 |
| sterni | pennae: maybe every md file for the manual could have an unique prefix assigned to it (e.g. haskell- for haskell.section.md). The md toolchain would then prefix every reference in the markdown file with that unless it is already prefixed. That would ensure unique anchors as long as the prefixes are unique.
Problem is of course that anchors would be changed, maybe we'd need to generously whitelist existing ones.
| 16:16:14 |
| sterni | * pennae: maybe every md file for the manual could have an unique prefix assigned to it (e.g. haskell- for haskell.section.md). The md toolchain would then prefix every reference in the markdown file with that unless it is already prefixed. That would ensure unique anchors as long as the prefixes are unique.
Problem is of course that anchors would be changed, maybe we'd need to generously whitelist existing ones. Still seems better than uuids.
Personally I'd also just be fine with a linter that checks for link uniqueness
| 16:16:37 |
 pennae | that's an option too, though we'd have to include the path of the file from the doc root instead of just the file name itself (and that can get pretty long) | 16:42:55 |
| pennae | nrd already checks for uniqueness and throws an error on duplicates, but that's a pretty bad experience. and the anchors that are likely to be problematic are exactly the ones that don't convey meaning | 16:43:37 |
| sterni | pennae: just have a list | 16:55:11 |
| sterni | well then just have meaningful anchors :) | 16:55:47 |
| pennae | In reply to @sternenseemann:systemli.org
well then just have meaningful anchors :) tell docs authors that D: | 16:58:10 |
| pennae | like. te python chapter has a section with the id faq | 16:58:52 |
| pennae | * like. the python chapter has a section with the id faq | 16:59:05 |
| pennae | that has been the in-html id for at least a very long time, possibly forever | 16:59:23 |
| sterni | I think checking for such things in the manual build is the best solution | 17:02:52 |
| sterni | it may always fail, after all | 17:02:59 |
| pennae | we do check, and it has failed in the past | 17:04:26 |
| pennae | at least now it can tell you where shit broke instead of having relaxng slap you with entirely incorrect error locations and messages that aren't worth the photons they're imprinted on | 17:05:41 |
| 1 Jul 2023 |
| pennae | nixdoc changes for nixpkgs markdowning are merged 🥳 | 12:42:41 |
| pennae | going to update the nixpkgs-side pr in a bit so we can hopefully get that done within the next week | 12:43:05 |
| pennae | https://github.com/NixOS/nixpkgs/pull/239636 preliminarily final pr for getting rid of docbook. that really should be it for the entirety of the nixpkgs repo, unless we missed something that's buried deep under the ice | 14:13:11 |
| pennae | home stretch! 🎉 | 18:59:06 |
| 3 Jul 2023 |
 @zmitchell:matrix.org | https://discourse.nixos.org/t/this-month-in-nix-docs-3-may-june-2023/29958 | 16:56:29 |
| @zmitchell:matrix.org | Feel free to post a comment if I got something wrong | 16:57:06 |
| pennae | damn, has it been two months again 😨 | 17:00:18 |
| @zmitchell:matrix.org | I too forgot that time marches forward regardless of my protests | 17:01:37 |
