@venizia/ignis-docs 0.0.8 → 0.2.0

package/content/guides/reference/glossary.md

@@ -1,6 +1,6 @@
 # Glossary for Beginners
 
-Quick reference for key terms in Ignis documentation.
+Quick reference for key terms in IGNIS documentation.
 
 
 ## Core Framework Terms
@@ -37,9 +37,16 @@ const TodoRoutes = {
 
 @controller({ path: '/todos' })
 export class TodoController extends BaseRestController {
+  constructor(
+    @inject({ key: 'repositories.TodoRepository' })
+    private repository: TodoRepository,
+  ) {
+    super({ scope: TodoController.name });
+  }
+
   @get({ configs: TodoRoutes.GET_ALL })
   async getAll(c: TRouteContext) {
-    const todos = await this.repository.find({});
+    const todos = await this.repository.find({ filter: {} });
     return c.json(todos, HTTP.ResultCodes.RS_2.Ok);
   }
 }
@@ -64,7 +71,7 @@ Annotations starting with `@` that add behavior to classes/methods.
 | `@repository` | Marks class as repository |
 | `@datasource` | Marks class as datasource |
 | `@inject` | Requests dependency from container |
-| `@get`, `@post`, `@patch`, `@delete` | HTTP route handlers |
+| `@get`, `@post`, `@put`, `@patch`, `@del` | HTTP route handlers |
 
 ### Dependency Injection (DI)
 Classes receive dependencies from an external container instead of creating them internally. Benefits: testable, flexible, maintainable.
@@ -111,7 +118,7 @@ class TodoRepository extends DefaultCRUDRepository<typeof Todo.schema> {}
 
 | Term | Description |
 |------|-------------|
-| **ORM** | Tool to work with databases using code instead of raw SQL. Ignis uses Drizzle ORM. |
+| **ORM** | Tool to work with databases using code instead of raw SQL. IGNIS uses Drizzle ORM. |
 | **Drizzle ORM** | Type-safe ORM library. [Docs](https://orm.drizzle.team/) |
 | **Schema** | Table structure definition using Drizzle syntax |
 | **Migration** | Script that creates/modifies tables. Version control for database structure. |
@@ -129,7 +136,7 @@ export const todoTable = pgTable('Todo', {
 // Relations
 export const userRelations = createRelations({
   source: userTable,
-  relations: [{ type: 'hasMany', model: () => Post, foreignKey: 'authorId' }],
+  relations: [{ name: 'posts', type: 'many', schema: postTable, metadata: {} }],
 });
 
 // Query with relations
@@ -181,15 +188,15 @@ await repository.find({
 | Method | URL | Action |
 |--------|-----|--------|
 | GET | `/todos` | List all |
-| GET | `/todos/:id` | Get one |
+| GET | `/todos/{id}` | Get one |
 | POST | `/todos` | Create |
-| PATCH | `/todos/:id` | Update |
-| DELETE | `/todos/:id` | Delete |
+| PATCH | `/todos/{id}` | Update |
+| DELETE | `/todos/{id}` | Delete |
 
 ```typescript
 const TodoRoutes = {
   GET_ALL: { method: HTTP.Methods.GET, path: '/', responses: jsonResponse({ schema: z.array(z.any()) }) },
-  GET_BY_ID: { method: HTTP.Methods.GET, path: '/:id', request: { params: z.object({ id: z.string() }) }, responses: jsonResponse({ schema: z.any() }) },
+  GET_BY_ID: { method: HTTP.Methods.GET, path: '/{id}', request: { params: z.object({ id: z.string() }) }, responses: jsonResponse({ schema: z.any() }) },
   CREATE: { method: HTTP.Methods.POST, path: '/', request: { body: jsonContent({ schema: z.any() }) }, responses: jsonResponse({ schema: z.any() }) },
 } as const;
 
@@ -215,14 +222,14 @@ class TodoController extends BaseRestController {
 | Term | Description |
 |------|-------------|
 | **Endpoint** | URL path that API responds to (e.g., `GET /todos`) |
-| **Route Parameter** | Variable in URL marked with `:` (e.g., `:id`) |
+| **Route Parameter** | Variable in URL wrapped in braces (e.g., `{id}` in OpenAPI route configs) |
 | **Request Body** | JSON data sent with POST/PATCH requests |
-| **OpenAPI/Swagger** | Auto-generated API docs at `/doc/explorer` (default path via SwaggerComponent) |
+| **OpenAPI/Swagger** | Auto-generated API docs at `/doc/explorer` (default path via ApiReferenceComponent) |
 
 
 ## Environment & Configuration
 
-Environment variables store configuration outside code (in `.env` files). Ignis uses `APP_ENV_` prefix to avoid system conflicts.
+Environment variables store configuration outside code (in `.env` files). IGNIS uses `APP_ENV_` prefix to avoid system conflicts.
 
 ```bash
 # .env file

package/content/guides/reference/mcp-docs-server.md

@@ -1,6 +1,6 @@
-# Getting Started with Ignis Docs MCP Server
+# Getting Started with IGNIS Docs MCP Server
 
-> **What is this?** An MCP (Model Context Protocol) server that lets AI assistants access Ignis framework documentation in real-time. Your AI gets the latest docs instead of outdated training data.
+> **What is this?** An MCP (Model Context Protocol) server that lets AI assistants access IGNIS framework documentation in real-time. Your AI gets the latest docs instead of outdated training data.
 
 ## What You'll Need
 
@@ -210,14 +210,14 @@ Restart your Claude Code session (close terminal and reopen), then test:
 
 ```bash
 # In your Claude Code session, ask:
-Can you search the Ignis docs for "dependency injection"?
+Can you search the IGNIS docs for "dependency injection"?
 ```
 
 **Expected behavior:**
 
 - Claude Code should use the `searchDocs` tool
 - You'll see a message like: `[Using tool: searchDocs]`
-- Results from Ignis documentation appear
+- Results from IGNIS documentation appear
 
 **If it doesn't work:**
 
@@ -231,16 +231,16 @@ Once working, try these queries:
 
 ```
 # Search documentation
-"How do I create a controller in Ignis?"
+"How do I create a controller in IGNIS?"
 
 # Get specific guide
 "Show me the complete Building a CRUD API guide"
 
 # Browse topics
-"What helpers are available in Ignis?"
+"What helpers are available in IGNIS?"
 
 # Get code examples
-"Show me an example of dependency injection in Ignis"
+"Show me an example of dependency injection in IGNIS"
 ```
 
 ## VS Code Setup
@@ -275,7 +275,7 @@ The configuration location depends on which extension you're using:
 
 ### Add MCP Server Configuration
 
-Open the config file for your extension and add the Ignis docs server:
+Open the config file for your extension and add the IGNIS docs server:
 
 **If you installed globally:**
 
@@ -324,7 +324,7 @@ Reload the window: `Cmd/Ctrl + Shift + P` → "Developer: Reload Window"
 Open your AI assistant in VS Code and ask:
 
 ```
-Can you search the Ignis docs for "dependency injection"?
+Can you search the IGNIS docs for "dependency injection"?
 ```
 
 The assistant should use the MCP tools to access and return documentation.
@@ -439,9 +439,9 @@ Once configured, you can ask your AI assistant:
 ### Example 1: Search Documentation
 
 ```
-You: "How do I set up dependency injection in Ignis?"
+You: "How do I set up dependency injection in IGNIS?"
 AI: [Uses searchDocs tool, finds relevant pages]
-AI: "Based on the Ignis documentation..."
+AI: "Based on the IGNIS documentation..."
 ```
 
 ### Example 2: Get Specific Guide
@@ -463,9 +463,9 @@ AI: "The Helpers category contains: Redis, Logger, Queue..."
 
 ## Local Development Setup
 
-For contributors or those developing Ignis itself:
+For contributors or those developing IGNIS itself:
 
-### 1. Clone the Ignis repository
+### 1. Clone the IGNIS repository
 
 ```bash
 git clone https://github.com/venizia-ai/ignis.git
@@ -481,7 +481,11 @@ bun install
 ### 3. Run the MCP server in dev mode
 
 ```bash
-bun run docs:mcp:dev
+# From the repo root
+bun run mcp:dev
+
+# Or from docs/wiki
+cd docs/wiki && bun run mcp:dev
 ```
 
 ### 4. Configure your AI tool
@@ -495,7 +499,7 @@ Use absolute paths in your config:
   "mcpServers": {
     "ignis-docs-dev": {
       "command": "bun",
-      "args": ["run", "/absolute/path/to/ignis/packages/docs/mcp-server/index.ts"]
+      "args": ["run", "/absolute/path/to/ignis/docs/wiki/mcp-server/index.ts"]
     }
   }
 }
@@ -508,7 +512,7 @@ Use absolute paths in your config:
   "mcpServers": {
     "ignis-docs-dev": {
       "command": "bun",
-      "args": ["run", "C:\\absolute\\path\\to\\ignis\\packages\\docs\\mcp-server\\index.ts"]
+      "args": ["run", "C:\\absolute\\path\\to\\ignis\\docs\\wiki\\mcp-server\\index.ts"]
     }
   }
 }
@@ -539,7 +543,7 @@ cat ~/.config/claude-code/config.json | python -m json.tool
 **Test 3: AI tool recognizes MCP server**
 
 - Restart your AI tool COMPLETELY (quit and reopen)
-- Ask: `Can you search the Ignis docs for "controller"?`
+- Ask: `Can you search the IGNIS docs for "controller"?`
 - Look for: `[Using tool: searchDocs]`
 
 
@@ -755,7 +759,7 @@ If this works, the issue is specific to `@venizia/ignis-docs`.
 
 ## What's Next?
 
-- **Learn the Tools:** Read the [Deep Dive Guide](/extensions/src-details/mcp-server) to understand all 5 available tools
+- **Learn the Tools:** Read the [Deep Dive Guide](/extensions/src-details/mcp-server) to understand all 10 available tools
 - **Advanced Usage:** Explore how to chain tools for complex documentation queries
 - **Contribute:** Help improve the docs or add new features
 

package/content/guides/tutorials/building-a-crud-api.md

@@ -1,6 +1,6 @@
 # Building a CRUD API: A Step-by-Step Tutorial
 
-Build a complete, database-backed REST API for managing todos. This guide covers Models, DataSources, Repositories, and Controllers - the core building blocks of Ignis applications.
+Build a complete, database-backed REST API for managing todos. This guide covers Models, DataSources, Repositories, and Controllers - the core building blocks of IGNIS applications.
 
 **Time to Complete:** ~45 minutes
 
@@ -21,16 +21,16 @@ Build a complete, database-backed REST API for managing todos. This guide covers
 **Endpoints:**
 - `POST /todos` - Create todo
 - `GET /todos` - List all todos
-- `GET /todos/:id` - Get single todo
-- `PATCH /todos/:id` - Update todo
-- `DELETE /todos/:id` - Delete todo
+- `GET /todos/{id}` - Get single todo
+- `PATCH /todos/{id}` - Update todo
+- `DELETE /todos/{id}` - Delete todo
 
 ### Architecture Flow
 
 Here's how a request flows through your application:
 
 ```
-HTTP Request (GET /api/todos/:id)
+HTTP Request (GET /api/todos/{id})
             │
             ▼
    ┌─────────────────┐
@@ -66,9 +66,9 @@ HTTP Request (GET /api/todos/:id)
 | **Model** | Defines what the data looks like |
 
 **Benefits of this separation:**
-- **Testable** — Mock repository in tests
-- **Maintainable** — Clear responsibility for each layer
-- **Flexible** — Change database without touching business logic
+- **Testable** - Mock repository in tests
+- **Maintainable** - Clear responsibility for each layer
+- **Flexible** - Change database without touching business logic
 
 ## Step 1: Install Database Dependencies
 
@@ -90,10 +90,10 @@ Create `src/models/todo.model.ts`:
 // src/models/todo.model.ts
 import {
   BaseEntity,
-  createRelations,
   generateIdColumnDefs,
   generateTzColumnDefs,
   model,
+  TRelationConfig,
   TTableObject,
 } from '@venizia/ignis';
 import { boolean, pgTable, text } from 'drizzle-orm/pg-core';
@@ -108,21 +108,16 @@ export const todoTable = pgTable('Todo', {
   isCompleted: boolean('is_completed').default(false),
 });
 
-// 2. Define relations (empty for now, but required)
-export const todoRelations = createRelations({
-  source: todoTable,
-  relations: [],
-});
-
-// 3. Define the TypeScript type for a Todo object
+// 2. Define the TypeScript type for a Todo object
 export type TTodoSchema = typeof todoTable;
 export type TTodo = TTableObject<TTodoSchema>;
 
-// 4. Create the Entity class, decorated with @model
+// 3. Create the Entity class, decorated with @model
 @model({ type: 'entity' })
 export class Todo extends BaseEntity<typeof Todo.schema> {
   static override schema = todoTable;
-  static override relations = () => todoRelations.definitions;
+  // 4. Define relations (empty array for now, but the resolver is still required)
+  static override relations = (): TRelationConfig[] => [];
   static override TABLE_NAME = 'Todo';
 }
 ```
@@ -149,7 +144,7 @@ const password = process.env.APP_ENV_DB_PASSWORD;
 const password = Bun.env.APP_ENV_DB_PASSWORD;
 ```
 
-Ignis uses `APP_ENV_` prefix to prevent conflicts with system variables.
+IGNIS uses `APP_ENV_` prefix to prevent conflicts with system variables.
 
 ### Create `.env` File
 
@@ -184,7 +179,7 @@ import {
   datasource,
   ValueOrPromise,
 } from '@venizia/ignis';
-import { drizzle } from 'drizzle-orm/node-postgres';
+import { NodePostgresDriver } from '@venizia/ignis/postgres/node-postgres';
 import { Pool } from 'pg';
 
 interface IDSConfigs {
@@ -200,15 +195,14 @@ interface IDSConfigs {
  *
  * How it works:
  * 1. @repository decorator binds model to datasource
- * 2. When configure() is called, getSchema() auto-discovers all bound models
- * 3. Drizzle is initialized with the auto-discovered schema
+ * 2. getSchema() auto-discovers all bound models when the driver/connector are wired
+ * 3. Naming NodePostgresDriver in @datasource is what wires the driver and Drizzle connector
  */
-@datasource({ driver: 'node-postgres' })
+@datasource({ driver: NodePostgresDriver })
 export class PostgresDataSource extends BaseDataSource<IDSConfigs> {
   constructor() {
     super({
       name: PostgresDataSource.name,
-      // Driver is read from @datasource decorator - no need to pass here!
       config: {
         host: process.env.APP_ENV_POSTGRES_HOST ?? 'localhost',
         port: +(process.env.APP_ENV_POSTGRES_PORT ?? 5432),
@@ -221,19 +215,18 @@ export class PostgresDataSource extends BaseDataSource<IDSConfigs> {
   }
 
   override configure(): ValueOrPromise<void> {
-    // getSchema() auto-discovers models from @repository bindings
-    const schema = this.getSchema();
-
-    // Log discovered schema for debugging
-    const schemaKeys = Object.keys(schema);
+    // getSchema() auto-discovers models from @repository bindings; log it for debugging
+    const schemaKeys = Object.keys(this.getSchema());
     this.logger.debug(
       '[configure] Auto-discovered schema | Schema + Relations (%s): %o',
       schemaKeys.length,
       schemaKeys,
     );
 
-    const client = new Pool(this.settings);
-    this.connector = drizzle({ client, schema });
+    // The client must land on this.client - a local would leave beginTransaction() with nothing
+    // to resolve a driver from, and it would throw `No driver and no client`. NodePostgresDriver
+    // named in @datasource above is what wires the driver and Drizzle connector from it.
+    this.client = new Pool(this.settings);
   }
 }
 ```
@@ -242,7 +235,7 @@ export class PostgresDataSource extends BaseDataSource<IDSConfigs> {
 - Schema is auto-discovered from `@repository` decorators - no manual registration needed
 - Uses `getSchema()` for lazy schema resolution (resolves when all models are loaded)
 - Uses environment variables for connection config
-- Implements `configure()` for connection setup and `getConnectionString()` for URL generation
+- `configure()` only assigns `this.client` - the base class wires the driver and connector from `@datasource({ driver })`; implements `getConnectionString()` for URL generation
 
 > **Deep Dive:** See [DataSources Reference](/references/base/datasources) for advanced configuration and multiple database support.
 
@@ -296,9 +289,9 @@ export class TodoRepository extends DefaultCRUDRepository<typeof Todo.schema> {
 Dependency Injection (DI) is a design pattern where objects receive their dependencies from outside rather than creating them internally. Instead of `new Repository()` inside a controller, you declare "I need a Repository" using `@inject`, and the framework provides it automatically.
 
 **Benefits:**
-- **Testable** — Replace real services with mocks in tests
-- **Flexible** — Swap implementations without changing code
-- **Maintainable** — Dependencies are explicit and centralized
+- **Testable** - Replace real services with mocks in tests
+- **Flexible** - Swap implementations without changing code
+- **Maintainable** - Dependencies are explicit and centralized
 
 [Learn more →](/guides/core-concepts/dependency-injection)
 :::
@@ -361,13 +354,13 @@ export * from './todo.controller';
 | Method | Path | Description |
 |--------|------|-------------|
 | GET | `/todos` | List all todos (find) |
-| GET | `/todos/:id` | Get todo by ID (findById) |
+| GET | `/todos/{id}` | Get todo by ID (findById) |
 | GET | `/todos/find-one` | Find one todo by filter (findOne) |
 | GET | `/todos/count` | Count todos (count) |
 | POST | `/todos` | Create todo (create) |
-| PATCH | `/todos/:id` | Update todo by ID (updateById) |
+| PATCH | `/todos/{id}` | Update todo by ID (updateById) |
 | PATCH | `/todos` | Update multiple todos by filter (updateBy) |
-| DELETE | `/todos/:id` | Delete todo by ID (deleteById) |
+| DELETE | `/todos/{id}` | Delete todo by ID (deleteById) |
 | DELETE | `/todos` | Delete multiple todos by filter (deleteBy) |
 
 > **Deep Dive:** See [ControllerFactory Reference](/references/base/controllers#controllerfactory) for customization options.
@@ -378,7 +371,7 @@ Update `src/application.ts` to register all components:
 
 ```typescript
 // src/application.ts
-import { BaseApplication, IApplicationConfigs, IApplicationInfo, SwaggerComponent, ValueOrPromise } from '@venizia/ignis';
+import { BaseApplication, IApplicationConfigs, IApplicationInfo, ApiReferenceComponent, ValueOrPromise } from '@venizia/ignis';
 import { HelloController } from './controllers/hello';
 import packageJson from '../package.json';
 
@@ -403,8 +396,8 @@ export class Application extends BaseApplication {
   setupMiddlewares(): ValueOrPromise<void> {}
 
   preConfigure(): ValueOrPromise<void> {
-    // 1. Register SwaggerComponent for API docs
-    this.component(SwaggerComponent);
+    // 1. Register ApiReferenceComponent for API docs
+    this.component(ApiReferenceComponent);
 
     // 2. Register datasource
     this.dataSource(PostgresDataSource);
@@ -481,7 +474,7 @@ Add these scripts to your `package.json`:
 
 ### Run the Migration
 
-For development, use `push` — it reads your schema and applies changes directly to the database:
+For development, use `push` - it reads your schema and applies changes directly to the database:
 
 ```bash
 bun run db:push
@@ -516,7 +509,7 @@ Test the API endpoints:
 # Create a todo
 curl -X POST http://localhost:3000/api/todos \
   -H "Content-Type: application/json" \
-  -d '{"title":"Learn Ignis","description":"Complete tutorial"}'
+  -d '{"title":"Learn IGNIS","description":"Complete tutorial"}'
 
 # Get all todos
 curl http://localhost:3000/api/todos
@@ -616,7 +609,7 @@ path: { base: '/api', isStrict: true },  // All routes start with /api
 # Make sure you include the header:
 curl -X POST http://localhost:3000/api/todos \
   -H "Content-Type: application/json" \  # ← This line!
-  -d '{"title":"Learn Ignis"}'
+  -d '{"title":"Learn IGNIS"}'
 ```
 
 

package/content/guides/tutorials/complete-installation.md

@@ -1,6 +1,6 @@
 # Complete Installation
 
-This guide walks you through creating a new web application with Ignis and setting up a professional development environment.
+This guide walks you through creating a new web application with IGNIS and setting up a professional development environment.
 
 **Time to Complete:** ~20 minutes
 
@@ -26,7 +26,7 @@ bun add hono @hono/zod-openapi @scalar/hono-api-reference @venizia/ignis @venizi
 - `hono` - High-performance web framework
 - `@hono/zod-openapi` - OpenAPI schema generation with Zod validation
 - `@scalar/hono-api-reference` - Interactive API documentation UI
-- `@venizia/ignis` - Core Ignis framework (application, controllers, repositories, DI)
+- `@venizia/ignis` - Core IGNIS framework (application, controllers, repositories, DI)
 - `@venizia/ignis-helpers` - Utilities (HTTP constants, logger, environment helpers)
 
 ### Development Dependencies
@@ -39,7 +39,7 @@ bun add -d typescript @types/bun @venizia/dev-configs eslint prettier tsc-alias
 - Centralized ESLint configuration
 - Centralized Prettier configuration
 - Shared TypeScript base configs
-- Consistent code style across all Ignis projects
+- Consistent code style across all IGNIS projects
 
 > **Note:** Database dependencies (drizzle-orm, pg, etc.) will be added later in the [CRUD Tutorial](./building-a-crud-api.md).
 
@@ -167,7 +167,7 @@ Each controller gets its own folder: `definitions.ts` for route configs and Zod
 Create `src/application.ts` - this is where you configure and register all your application resources:
 
 ```typescript
-import { BaseApplication, IApplicationConfigs, IApplicationInfo, SwaggerComponent, ValueOrPromise } from '@venizia/ignis';
+import { BaseApplication, IApplicationConfigs, IApplicationInfo, ApiReferenceComponent, ValueOrPromise } from '@venizia/ignis';
 import { HelloController } from './controllers';
 import packageJson from '../package.json';
 
@@ -188,7 +188,7 @@ export class Application extends BaseApplication {
     // return {
     //   name: 'my-app',
     //   version: '1.0.0',
-    //   description: 'My Ignis application',
+    //   description: 'My IGNIS application',
     // };
   }
 
@@ -212,8 +212,8 @@ export class Application extends BaseApplication {
 
   // Hook 3: Register your resources (THIS IS THE MOST IMPORTANT ONE)
   preConfigure(): ValueOrPromise<void> {
-    // Register SwaggerComponent for API documentation at /doc/explorer
-    this.component(SwaggerComponent);
+    // Register ApiReferenceComponent for API documentation at /doc/explorer
+    this.component(ApiReferenceComponent);
 
     // As your app grows, you'll add:
     // this.dataSource(PostgresDataSource);    // Database connection
@@ -234,9 +234,9 @@ export class Application extends BaseApplication {
 
 > [!NOTE] IApplicationInfo
 > **Required fields in `package.json`:**
-> - `name` — App name (shown in API docs title)
-> - `version` — App version (shown in API docs)
-> - `description` — App description (shown in API docs)
+> - `name` - App name (shown in API docs title)
+> - `version` - App version (shown in API docs)
+> - `description` - App description (shown in API docs)
 >
 > **No proper `package.json`?** Use static app info instead (see Option 2 in code above).
 >
@@ -262,7 +262,7 @@ export class Application extends BaseApplication {
 
 Each controller lives in its own folder with separate files for definitions, logic, and exports.
 
-Create `src/controllers/hello/definitions.ts` — route configs and schemas:
+Create `src/controllers/hello/definitions.ts` - route configs and schemas:
 
 ```typescript
 import { jsonContent } from '@venizia/ignis';
@@ -285,7 +285,7 @@ export const helloRouteConfigs = {
 } as const;
 ```
 
-Create `src/controllers/hello/hello.controller.ts` — the controller class:
+Create `src/controllers/hello/hello.controller.ts` - the controller class:
 
 ```typescript
 import { BaseRestController, controller, api } from '@venizia/ignis';
@@ -311,13 +311,13 @@ export class HelloController extends BaseRestController {
 }
 ```
 
-Create `src/controllers/hello/index.ts` — barrel export:
+Create `src/controllers/hello/index.ts` - barrel export:
 
 ```typescript
 export * from './hello.controller';
 ```
 
-Create `src/controllers/index.ts` — export all controllers:
+Create `src/controllers/index.ts` - export all controllers:
 
 ```typescript
 export * from './hello';
@@ -327,7 +327,7 @@ export * from './hello';
 
 | Pattern | Description |
 |---------|-------------|
-| `definitions.ts` | Route configs, Zod schemas, and constants — keeps controller file clean |
+| `definitions.ts` | Route configs, Zod schemas, and constants - keeps controller file clean |
 | `@controller` | Registers the class as a controller with a base path |
 | `@api` | Defines a route with `method` specified in configs |
 | `@get`, `@post`, etc. | Shorthand decorators that auto-set the HTTP method (recommended) |
@@ -425,11 +425,11 @@ Response:
 
 Open `http://localhost:3000/doc/explorer` to see interactive Swagger UI with your endpoints.
 
-Congratulations! You have successfully created and configured your first application with the `Ignis` framework.
+Congratulations! You have successfully created and configured your first application with the `IGNIS` framework.
 
 ## Continue Your Journey
 
-You now have a working Ignis application!
+You now have a working IGNIS application!
 
 **Next steps:**