What are the next steps?

[pi0]

Hi all 👋

Since we announced new organization we already have 37+ people showing interest to help on improving Nitro as a better community, this was far beyond what I was expecting THANK YOU. ❤️

As you might probably know, we are close to Nitro 2.10 (which is a big rewrite in 2.x) and Nitro 3.0 + h3 2.0 releases which are also really big ones and they also affect how we use Nitro.

In the meantime, Nitro (as an ecosystem), also deserves to be better:

• Nitro docs are incomplete and fragmented.
• We don't have a dedicated channel for (end) user support.
  • unjs/nitro#issues is for tracking bugs/features, not a support channel and there are lots of invalid tickets in there.
  • unjs/nitro#discussions is not engaged well enough.
  • We have scattered discussions and questions in several discord and framework channels such as Nuxt Discord and Nuxt issues not tracked in Nitro channels.
• Users often need to go through several repositories in unjs org to find about usage docs and report their problems.
• While we have a connection channel with some deployment providers and frameworks, their teams do not have a presence in the Nitro org itself.

I hope that the Nitro docs and community become the frontline and first step for every user's needs.

• We need to unify all documentation as usages to the main docs and improve examples
• We need to triage (question) issues and help to move them forward by answering, making minimal reproduction, making more isolated reports to downstream repositories, etc.
• We need to be more responsive to the questions nitro discussions and possibly collect community feedback from various sources into the central place of discussions.
• We need to open up a public Discord server for more engagement

How to get started?

I believe the first step should be knowledge sharing within the team. This way we can read and answer the issues and find solutions together with a shared vision. If I could explain anything better, please don't hesitate to just open a new discussion, every small detail would make our team work better.

I would highly recommend that you all read nitro docs, and get familiar with the underlying unjs ecosystem tools. You can read nitro source also to find out how things internally work, and perhaps try to view Nitro DX from the user's perspective (without using any wrapper framework).

Please read nitro core principles they are really really really important about how we approach solutions in Nitro.

Thanks to the @codiini idea (#6), we have initiated awesome repository (private to community team). It is still under progress before ready but ideas welcome there as we are collecting various resources.

I have also created a discord server we can use to chat closer and later use for better internal coordination.

/cc @nitrojsdev/community