nimforum mirror - How to edit the wiki?

pietroppeter (orginal) [2022-11-02T11:46:10+01:00] view original

this has been brought up a couple of times in unrelated threads, so it is worth making its own thread. Hopefully someone that knows the details will answer.

https://forum.nim-lang.org/t/9223#62915

https://forum.nim-lang.org/t/9521#62555

some open questions:

to edit the wiki you need to be a contributor, correct?

what does it mean to be a contributor? having a merged PR is enough? how old should the PR be?

when was this enforced?

once we have the answers we could update the wiki

DeletedUser (orginal) [2022-11-02T11:59:46+01:00] view original

to edit the wiki you need to be a contributor, correct?

Sorry for the inconvenience. No, I simply disabled contributing to the wiki for a few times. Each time fishy cases like https://forum.nim-lang.org/t/9164 happened, I disable the wiki for some times. And after some time, I enable the Wiki. It has happened for at least four times.

what does it mean to be a contributor? having a merged PR is enough? how old should the PR be?

It is the opposite. There is no censor which can be done for wiki contribution. We can only revert the content, report them and ban them (only the owner of organization can ban people). The alternative method is disabling the wiki for some time.

I would rather the wiki can be transferred into a separate repo so that we can reject these fishy contribution.

juancarlospaco (orginal) [2022-11-02T12:02:50+01:00] view original

I think Wiki is disabled because of spam and phishing.

I tried making an antispam bot for Wikis, but the Github API is very limited for Wikis.

The problem is that it is not spam bots nowadays, but actually people posting spam, so captchas and the like wont work, how they make the economics of that work, I dunno.

dlesnoff (orginal) [2022-11-02T15:50:10+01:00] view original

@xflywind with the edit button activated, it is easier for me to copy the markdown files into a separate repo. If you intend to do it, no problem. I'll probably make a second version of each md file into nimibs after this, to check code output and code compilation, and check all the links manually. The longest will be to change all links to point them to the right repository.

Is it easier to make a private repository and then move to a nim-lang repo (at the risk to have to change all urls after), or wait for the creation of a nim-lang repo and add the makefiles through PRs ?

Yardanico (orginal) [2022-11-02T15:53:22+01:00] view original

You can just clone the wiki as a git repo: git clone git@github.com:nim-lang/nim.wiki.git

DeletedUser (orginal) [2022-11-02T16:40:31+01:00] view original

Is it easier to make a private repository and then move to a nim-lang repo (at the risk to have to change all urls after), or wait for the creation of a nim-lang repo and add the makefiles through PRs ?

I can create the repo, PRs are appreciated.

dlesnoff (orginal) [2022-11-02T18:04:28+01:00] view original

@xflywind I used @yardanico's command to fetch all the MD files and add them to your repo. I'll write a script that retrieve all nim markdown code blocks and split them into a nbCode:. If no change has been made since you opened back the edit button, no links should have been compromised. Otherwise, I'll try to make a script to list all external links (that do not link to the wiki or www.nim-lang.org).

DeletedUser (orginal) [2022-11-02T18:10:20+01:00] view original

Nice work!

dlesnoff (orginal) [2022-11-03T01:06:44+01:00] view original

I have generated 60 Nimibs from the wikis MDs .. image :: https://cdn.discordapp.com/attachments/371759389889003532/1037517675506712727/Firefox_Full_Of_Nimib.png

Yardanico (orginal) [2022-11-03T01:23:30+01:00] view original

Maybe a better idea for the wiki would be using nimibook?

pietroppeter (orginal) [2022-11-03T12:22:51+01:00] view original

Sorry for the inconvenience. No, I simply disabled contributing to the wiki for a few times.

ah ok, good to know. and thanks for the work protecting it from.

I would rather the wiki can be transferred into a separate repo

yep, this seems a solution that could work

I have generated 60 Nimibs from the wikis MDs

wow, nice work @dlesnoff !

Maybe a better idea for the wiki would be using nimibook?

agree, nimib for the moment has very limited functionality for building a site and nimibook is currently the only available option to have a nice toc.

I am working on a SSG for nimib, hopefully we will have (soon?) more options (for a blog or general purpose site).

dlesnoff (orginal) [2022-11-04T09:18:35+01:00] view original

Can we add a message on the wiki concerning the new repository ? We should also make the old wiki non-editable again, and advise to propose a Pull Request instead.

It would be nice if the wiki markdowns could be rendered from the Github repository. It would replace the edit button with the PR system of Github.

I will change to Nimibook and add the table of contents but you should be aware that Nimibook does not support all functionality Nimib provides. I tried to plot a graph with Plotly show_plotly but it was not working due to some distinction in the HTML header between Nimib and Nimibook.

dlesnoff (orginal) [2022-11-04T09:25:12+01:00] view original

Can we add a message on the wiki concerning the new repository ? We should also make the old wiki non-editable again, and advise to propose a Pull Request instead.

It would be nice if the wiki markdowns could be rendered from the Github repository. It would replace the edit button with the PR system of Github.

I will change to Nimibook and add the table of contents but you should be aware that Nimibook does not support all functionality Nimib provides. I tried to plot a graph with Plotly show_plotly but the macro nbShow (doc.partials) was not working due to some distinction in the HTML header generation made by Nimib and made by Nimibook.

dlesnoff (orginal) [2022-11-04T09:25:47+01:00] view original

Can we add a message on the wiki concerning the new repository ? We should also make the old wiki non-editable again, and advise to propose a Pull Request instead.

It would be nice if the wiki markdowns could be rendered from the Github repository. It would replace the edit button with the PR system of Github.

I will change to Nimibook and add the table of contents but you should be aware that Nimibook does not support all functionality Nimib provides. I tried to plot a graph with Plotly show_plotly but the macro nbShow (doc.partials) was not working due to some distinction in the HTML header generation made by Nimib and made by Nimibook.

dlesnoff (orginal) [2022-11-04T09:27:52+01:00] view original

Sorry for the triple post. I had a bug where the Reply button did not activate anything visible. I believed it did not sent my message. I can not delete these additionnal messages.

DeletedUser (orginal) [2022-11-04T09:29:22+01:00] view original

It is a known bug regarding Karax if you are using LanguageTool or Grammarly tools which change the vnode or something.

DeletedUser (orginal) [2022-11-04T09:31:28+01:00] view original

Can we add a message on the wiki concerning the new repository ? We should also make the old wiki non-editable again, and advise to propose a Pull Request instead.

Sure thing, when the new repository has a pipeline hosting the contents using GitHub pages or something.

pietroppeter (orginal) [2022-11-04T17:36:51+01:00] view original

I will change to Nimibook and add the table of contents but you should be aware that Nimibook does not support all functionality Nimib provides. I tried to plot a graph with Plotly show_plotly but the macro nbShow (doc.partials) was not working due to some distinction in the HTML header generation made by Nimib and made by Nimibook.

that is a bug and should be fixed, can you open an issue on nimibook with some details?

It would be nice if the wiki markdowns could be rendered from the Github repository. It would replace the edit button with the PR system of Github.

one thing that you can do yourself is activate github pages on your fork while you make your changes (to see them you have to merge in the branch you use for pages, either main or gh-pages, usually). then at some point you can do a PR to nim repo and github pages could be activated there as well. ideally it would also be nice to use a PR preview system like the one is setup in scinim/getting-started, nimib and nimibook but that takes a minimum of setup (and a netlify account...)

pietroppeter (orginal) [2022-11-04T18:00:11+01:00] view original

It is a known bug regarding Karax if you are using LanguageTool or Grammarly tools which change the vnode or something.

I guess you are referring to this issue: https://github.com/nim-lang/nimforum/issues/303

I create an issue also in karax so that people using karax are aware (and it is also the place where it should be fixed): https://github.com/karaxnim/karax/issues/232

Mirror of forum.nim-lang.org

9571 :: How to edit the wiki?