Community

Contribute to NestJS Ninja

This blog works better when it is close to real projects. If you have a problem you solved, a topic you want to understand, or a fix for an existing article, there is a simple path to contribute.

Share a project

Send a NestJS project, architecture decision, integration, or bug you solved. Practical examples are the best source for new articles.

Open project form

Suggest an article

Ask for a topic you want explained: tests, modules, queues, authentication, deployment, observability, or anything around backend architecture.

Open article form

Fix a post

Found a typo, broken link, outdated command, missing image, or confusing explanation? Start with a correction form and follow up with a small pull request if you already have the fix.

Open correction form

Contribute code

Improve the reader experience, automation, quality gate, cover generation, or markdown rendering. Open a focused proposal first, then send the tested pull request.

Open code form

What helps most

The most useful contributions are specific. Instead of only saying “write about testing”, share the type of app, the test problem, the dependency that made it hard, and what result you expected. That context makes the future article much more practical.