nix.dev
nix.dev copied to clipboard
remove glossary and influences
the glossary is empty, and influences are irrelevant for the objective of learning Nix
Why do you think we should remove glossary? It's useful to be able to reference it here for the most basic terms that a beginner might encounter for the first time.
For influences, it's a sign of a health community to show that others are building work on top of what we're doing.
Why do you think we should remove glossary?
Because it only contains TODOs.
You said you would prefer not to present skeletons, and I agree in part: have a scaffold and give it some contents to get the feeling for the whole thing. Having two terms in the Glossary is probably fine, but they should at least be defined.
(Having a [visual] outline would also be good if some parts are filled - right now the textual one does the same thing.)
Another point is that I think the glossary should be part of the manual(s), as those are (supposed to be) the reference. A non-manual Glossary should at best contain the more softly defined jargon from the ecosystem. And even then we should choose where to maintain a single source of truth - here or the Wiki?
For influences, it's a sign of a health community to show that others are building work on top of what we're doing.
Yes, agreed. Question is whether that should be curated here, and my intuition is we should sharpen the focus on beginner and problem solving and guides, and move these softer issues to the Wiki.
One side effect is reducing the length of the main navigation side bar to depict that very clear focus. Just trying to ease overall navigation within the ecosystem.
@NixOS/marketing-team This information should be maintained by marketing.
This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/2023-07-17-documentation-team-meeting-notes-64/30653/1