Nitro is expanding to a dedicated org

[pi0]

What is happening

Nitro, originally hosted under the unjs umbrella—which provides the supply chain of low-level tools powering Nuxt and many other frameworks, tools, and projects—has grown significantly.

After almost 4 years of Nitro development, it's time to evolve Nitro into a larger community and ecosystem.

By moving Nitro into a dedicated organization, we aim to create a user-friendly community and team made up of diverse backgrounds, talents, and mindsets. This will also help expand examples and improve documentation.

Like unjs, Nitro is committed to building an open server toolkit that works with everything™️.

I have written a draft of what we really value in making Nitro: nitro core principles

Would you like to join the team?

If you enjoy writing documentation and engaging with the community, we could really use your help!

If you are part of a framework or deployment provider team that wants to have a presence within this new community, we would love to have you on the team as well!

While we are still shaping the new organization and team, I would love to hear from you!

We are getting prepared for the Next steps

[yooneskh]

Hi Pouya,
It is truly great to see unjs grow so much. I have always been fortunate to use the tools you provided, if possible i would love to be able to help in whatever way I can.

[silvesterwali]

hi pio. if possible i want to join even it a small part that i can write

[o-az]

I'm here for this!

Whether as a spectator or as an active contributing team member is left for Nitro to decide. Either way I'm supremely bullish on this ❤️

[geromegrignon]

Hi, willing to help with documentation (and already engaging with the community with an upcoming talk in Poland: https://ng-poland.pl/speaker/2024/gerome-grignon).

[kkarimi]

Would love to help with docs or any way I can

[iiio2]

@pi0 , Very nice. I am always here to contribute in any portion. I would like to join in team.

[CibiAananth]

Would absolutely love to join the team and help 👍🏼

[justserdar]

Interested. I'm a full stack freelancer trying to locally expand all forms of Nuxt/Nitro into the local business/ market space. It's my personal mission to improve awareness beyond anything react/next.

I write articles on my blog called the Foundry , expect to see articles about Nuxt & Nitro auth, db's, websockets, tailwind, threejs and much more still to come.

Contribution wise, I wrote two auth adapters for Nuxt-Auth-Utils (discord & linkedin). In early Nuxt 3 rc days, I got a Sidebase Nuxt Auth article out that got over 10k reads and still counting.

I recently started writing my own Nuxt modules (can't wait for Nitro modules), I have Heyokjs, a Nuxt module x Three.js. Nuxt-Coolify a Nuxt module to wrap the self host Coolify API.

Soft launching GLTransform soon which is a Nuxt & Nitro driven 3D(-modeling) / Digital twin editing SaaS platform using again Threejs and Sockets for Collab Shared hybrid style working on 3D projects for f.e Augmented reality/beyond.

I'd happily contribute as part of a team.

The first project I created wth Nuxt v2 were 3 3D product configurators for M line (EU's biggest bed manufacturer), currently building a 3D product configurator for a client using Nuxt v3 (It's so much fun).

[ThimoDEV]

Hi!

I love to see how Nitro grew over the years. By now its my favorite backend and I want to help where I can.

I developed the Nuxt codemirror module, helped fixed bugs, docs and examples in the nuxt repo, Tresjs, nuxt image and some more.

I'd love to participate in any way possible

Kind regards

Thimo

[pabyome]

Hi Pio,
I would love to join the team and contribute in any capacity needed.

[gxres042]

It's great to see Nitro expanding soon.

Would love to do something for Nitro.

[johannschopplich]

Hi Pooya!
As I have done in the past, I would like to contribute to Nitro. I'd like to join the team especially to help improve the documentation. Since I use Nitro for almost all of my APIs (personal and professional), I want to give back what Nitro has enabled me to do.

[oscarcao]

Happy to put my hand up to help with the docs.

O.

[adamdehaven]

I’d be happy to help

[OsamaHaikal]

I would be happy to join and help

[BluesYoung-web]

Hello, I first came into contact with nitro through nuxt3. I am very honored to witness its growth. It has helped me make the team's docker image very small, and in some non-nuxt projects, it has also made it easier for me to write back-end interfaces. My current ability is indeed not that high. The only thing I can show off is that I previously submitted a pr to nuxt-devtools. But at least, if Chinese documents need to be translated later, I am very happy to help! 😃 ❤️

[typed-sigterm]

Chinese document +1

[gxres042]

@pi0 Should we do translations for Nitro's docs?

[justserdar]

Per extension we could also do Dutch translations, @ThimoDEV you wanna hop in too?

[ThimoDEV]

@justserdar Happy to help with translations!

[pi0]

I appreciate your willingness to help with translations and we certainly can use help ❤️

The first and most important mission we have is to improve the main documentation content and examples in English as it can get out of sync out of sync if we translate now.

[nermalcat69]

Glad to see nitro grow :) - if i feel like i can contribute i'll just do a pr

[typed-sigterm]

Would love to do something :)

BTW what about unjs/h3?

[pi0]

h3 (like many other tools) is a separate project in unjs. We mainly need to improve jsdocs for h3 so that they can be cross-rendered in nitro (and other places) as h3 utils are available for Nitro users via high-level API.

[yeskunall]

Hey Pooya, glad to see the continued growth of Nitro! If you need assistance with anything (especially docs!), feel free to ping me.

Thanks for working on this (and other) projects!

[hakshu25]

I enjoyed listening to the presentations at Vue Fes Japan 2024.
I would be happy to join and help.

[taskylizard]

Hi! Really awesome to see the progress all these years on Nitro, will be happy to help!

[jelmerdemaat]

I would like to help! I think I can contribute to documentation. How can I help?