Learning Path
The recommended order for learning NestForge without getting lost in reference material too early.
If you are new to NestForge, follow the docs in this order:
- Installation
- VS Code Extension if you want guided scaffolding and editor workflows
- Quick Start
- Feature Modules
- DTOs, Services, and Routes
- Build Your First Feature
- Database Setup if the app needs persistence or store infrastructure
- one workflow that matches your runtime:
Testing,GraphQL,gRPC,WebSockets,Microservices,Auth/OpenAPI,Scheduling, orCaching - one workflow that matches your data backend:
SQL,Mongo, orRedis - examples
- concepts and reference pages later
Why this order works
Section titled “Why this order works”New users usually get lost when they read the framework in reference order. NestForge is easier to understand when you first learn:
- how a feature is structured
- how the module wires it into the app
- how a transport is bootstrapped
- how to test the result
After that, the concept and reference pages become much more useful.
Suggested tracks
Section titled “Suggested tracks”HTTP-first application
Section titled “HTTP-first application”Read these in order:
- Quick Start
- Build Your First Feature
- Database Setup
- SQL Database Workflow
- OpenAPI from Scratch
- Testing Workflow
- Auth and OpenAPI Workflow
GraphQL-first application
Section titled “GraphQL-first application”Read these in order:
Document-oriented application
Section titled “Document-oriented application”Read these in order:
Cache-heavy application
Section titled “Cache-heavy application”Read these in order:
gRPC-first application
Section titled “gRPC-first application”Read these in order:
Event-driven or socket-first application
Section titled “Event-driven or socket-first application”Read these in order:
When to read the reference pages
Section titled “When to read the reference pages”Read the reference pages after you already have a working mental model. They are best for:
- checking syntax
- understanding available APIs
- comparing options
- debugging specific framework behavior
They are not the best first stop for onboarding.