Transfer `avivkeller/learn` into the organization

[avivkeller]

See: https://github.com/avivkeller/learn
See: https://aviv.sh/learn (Note: This is set-up to run at learn.nodejs.org, and, as such, the sidebar does not work, since it's used at aviv.sh/learn)

Closes nodejs/nodejs.org#8612
Closes? nodejs/learn#38

cc @nodejs/nodejs-website

[avivkeller]

cc @nodejs/TSC so they are aware of our desired changes

[ovflowd]

Instead of transfering the repo, I'd rather prefer if we create a new one and set-it up here so that our team can actually review the code. i.e., would love to know what https://github.com/avivkeller/learn/blob/main/scripts/generate-config.mjs does

[avivkeller]

IMO transferring is better, since we already have a working preview, fully set up. We can discuss the merit of individual files before or after transfer.

To answer that question, it takes the data from navigation.json and creates the NavBar + SideBar sections.

[ovflowd]

IMO transferring is better, since we already have a working preview, fully set up. We can discuss the merit of individual files before or after transfer.

That kinda sounds like "hey I have this big chunk of code no one reviewed and that will replace nodejs.org/learn and I simply want it merged here..." [...]

Usually transfers are done for existing codebases that are being moved into Node.js core, not new spin up repositories (frehsly ones), we should create learn.nodejs.org within the Node.js org

[avivkeller]

@ovflowd ✨ compromise? ✨ If this gets no objections after the needed 72 hours, we create the new repository in this organization, and I'll open two PRs.

1. Move all the learn content
2. Everything else

That way, we are still making a new repo, allowing for review, but not repeating work already done?

[ovflowd]

To be clear, I'm fine if in the end we move, I just wish that next time we actually start the repository in-house, there was no need for you to make the whole thing in your personal account. We want more people contributing on this, reviewing the code and understanding it. If it's just you mass-working on PRs it creates a bus-factor and we become blind to how our systems work.

I always appreciate how fast and promptly you are with things, but we're not in a rush for any of them 🙏

[ovflowd]

In the end I'm fine with whatever, be it moving the repo, creating a new one or whatnot.

[avivkeller]

72 hours have passed, repository created @ https://github.com/nodejs/learn.

[ovflowd]

72 hours have passed, repository created @ https://github.com/nodejs/learn.

Should we call it learn or learn.nodejs.org? To visually indicate this is a website

[avivkeller]

Personally, I don't think so, I think learn is a good name, as this content might not be on a subdomain, it could be a path, etc, it's also accessible on GitHub. However, I don't feel too strongly.