Wiki.nixos.org is now live

Announcements
62

Thread has gotten pretty long so dont know if this was already mentioned. There are few module docs in Nixpkgs targeting specific modules, often written by maintainers themselves because docstrings aren’t enough.

E.g.

Can we possibly auto-genrate wiki pages for them and linking back to nixpkgs? So source of truth remains at the source code, but still benefits from SEO and discoverability of wiki.

Unsure on how much effort would be for translation. Might want to limit to unstable/stable branches to reduce page churn. Also want to limit write access to auto generated pages to not lose user changes to wiki on next page gen.

Just something to think about. I don’t know anything about mediawiki, but will happily work on it if people think its a good idea.

2 Likes
63

I agree this would be cool to have, this is along what I was proposing in:

Technically, speaking, it seems like this plugin allows the wiki to embed external content with something as simple as

{{#embed:github.com/org/repo/blob/master/hi.md}}

It seems to even work to include a code file.

We can maybe use this in the wiki to avoid code duplication while allowing users to edit the page?

This can even work for other documentation providing we can “compile” it first to markdown.

64

Those are part of the NixOS manual. We just need to carry out the plan to split the manual into multiple pages for SEO.

6 Likes
65

(EDIT: sorry, I misread your message and thought you were a maintainer of the old wiki) I definitely don’t want to take any hostile actions against the old wiki (that I both used and tried to improve)… but I still don’t understand why it would be bad to suggest users to check the new wiki with a link like @MikulasVanousek added (maybe with a lack of coordination, possibly explaining why someone removed the links), as it leaves the original content unchanged. The current status (official vs yours that is better referenced by search engines) will inevitably lead to a useless fork of the documentation, which will result in users reading outdated documentation. I guess you can agree, Nix does not need something like that. So, to maintain an healthy spirit, could you please consider adding a link suggesting users to additionally read the official Wiki?

1 Like
66

We do not control the old wiki and their owner has been unwilling to cooperate on this, how do you suggest to do this?

67

Oh, my bad, I read @JulienMalka 's message to quickly, I thought he was a maintainer of the old wiki, and I thought he reverted the changes of @MikulasVanousek. In my opinion, @MikulasVanousek’s code was the best strategy to solve this issue (and it does not harm the old wiki’s content at all)… but seems like someone reverted this changed, no idea who then…

68

The owner of the wiki reverted this change.

1 Like
69

That’s really sad and, IMHO, quite selfish. Not sure what to do then, except from regularly adding this warning manually, and trying to get the official wiki better referenced.

70

On a different topic, I see the wiki as a great opportunity to translate the documentation (for now, NixOs’s documentation is very english-orientated). But so far I can’t see a way to add a translation on Wiki’s page. Could the maintainer enable this option?

1 Like
71
6 Likes
72

I just tried to sign up for the Wiki using my Github account but it requests permission to act on my behalf.

Why?

73

It’s a limitation of GitHub. We don’t request any permissions from your account: GitHub - NixOS/nixos-wiki-infra: This project contains the setup of https://wiki.nixos.org

1 Like
74

Just thought I should mention this userscript that redirects you to the new wiki when accessing the old wiki. It’s linked to by the official wiki’s FAQ if anyone’s interested.

2 Likes
75

You can also do this with the Redirector extension as I did. Here’s my Redirector.json which you can import:

{
    "createdBy": "Redirector v3.5.3",
    "createdAt": "2024-07-11T16:10:24.762Z",
    "redirects": [
        {
            "description": "Redirect old wiki to new one",
            "exampleUrl": "https://nixos.wiki/wiki/some-word-that-matches-wildcard",
            "exampleResult": "https://wiki.nixos.org/wiki/some-word-that-matches-wildcard",
            "error": null,
            "includePattern": "https://nixos.wiki/wiki/*",
            "excludePattern": "",
            "patternDesc": "Anything after nixos.wiki/wiki redirects to the same page on wiki.nixos.org",
            "redirectUrl": "https://wiki.nixos.org/wiki/$1",
            "patternType": "W",
            "processMatches": "noProcessing",
            "disabled": false,
            "grouped": false,
            "appliesTo": [
                "main_frame"
            ]
        }
    ]
}
4 Likes
77

would be nice to have a single account for all *.nixos.org (for the not-Github users) - ie share Discourse account and wiki account with nixos.org as identity provider?

78

Good idea. Do you want to help setting it up?

1 Like
79

I have some basic experience with kanidm, but I am not a devops person in real live (I don’t even have a Github account) - with mentoring I may be able to help out

1 Like
80

Unfortunately kanidm doesn’t have any social login options like GitHub. Maybe keycloak? Though of course we could just keep the GitHub login on Discourse with kanidm on the side.