Documentation is outdated

[slavamuravey]

After transferring learn section to the current repository documentation looks like outdated.
For example, these PRs are lost:
nodejs/nodejs.org#8623
nodejs/nodejs.org#8611

I recreated my PR nodejs/nodejs.org#8611 -> #23

@sebastiendan Please, take into account your PR nodejs/nodejs.org#8623. It is not presented in the current repository.

@avivkeller Please, check another documentation sections.

[avivkeller]

@avivkeller Please, check another documentation sections.

Hey, as @bjohansebas mentioned, please be a bit kinder with how you phrase things. We’re all putting in a lot of work here and that tone doesn’t help, especially when you echo it multiple times.

These files were added before those changes landed (see avivkeller/learn@d0f7b59), so given the repository move, new tooling, and everything we’ve shipped over the past few days... if a couple of PRs didn’t fully make the cut, that’s completely fine and can be addressed in a follow-up.

[akashbirajdar04]

hi i like to work on this documentation issue can you assing it to me

[mizoz]

Hi! I'd love to contribute. Could you assign this issue to me? Happy to get started right away.

[bmuenzenmeyer]

we dont assign issues in the project so feel free to contribute as you can

[rscharfer]

I believe the only thing left to do that has been explicitly mentioned above is getting the nodejs/nodejs.org#8623 changes into the current repo.
@avivkeller Does that sound right?

If so, can we close this issue after that is done?

(I'm just trying to refine this a bit. : ) )

[ovflowd]

I believe the only thing left to do that has been explicitly mentioned above is getting the nodejs/nodejs.org#8623 changes into the current repo. @avivkeller Does that sound right?

If so, can we close this issue after that is done?

(I'm just trying to refine this a bit. : ) )

bump @avivkeller 🙏

[avivkeller]

Yes, that's correct