@venizia/ignis-docs 0.0.5 → 0.0.6-1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@venizia/ignis-docs",
-  "version": "0.0.5",
+  "version": "0.0.6-1",
   "description": "Documentation and MCP Server for Ignis Framework",
   "keywords": [
     "ignis",

package/wiki/best-practices/architectural-patterns.md

@@ -2,8 +2,6 @@
 
 Ignis promotes separation of concerns, dependency injection, and modularity for scalable, maintainable applications.
 
-> **Deep Dive:** See [Core Framework Reference](../references/src-details/core.md) for implementation details.
-
 ## 1. Layered Architecture
 
 Each layer has a single responsibility. Ignis supports **two architectural approaches**:

package/wiki/best-practices/architecture-decisions.md

@@ -141,7 +141,6 @@ export class HealthController extends BaseController {
 | **Service** | Single app | Medium | Internal |
 | **Inline** | Single controller | None | None |
 
----
 
 ## 3. Repository Method Design
 
@@ -203,7 +202,6 @@ export class OrderRepository extends BaseRepository<Order> {
 }
 ```
 
----
 
 ## 4. Error Handling Strategy
 
@@ -277,7 +275,6 @@ Controller (catches, formats for API response)
 Client (receives formatted error)
 ```
 
----
 
 ## 5. Scaling Decisions
 
@@ -334,7 +331,6 @@ class NotificationService {
 | Data | Shared database OK | Need data isolation |
 | Complexity | Keep simple | Worth the overhead |
 
----
 
 ## 6. Data Access Patterns
 
@@ -384,7 +380,6 @@ const nearby = await db.execute(sql`
 `);
 ```
 
----
 
 ## 7. Configuration Strategy
 
@@ -429,7 +424,6 @@ this.component(SwaggerComponent, {
 });
 ```
 
----
 
 ## 8. Testing Strategy
 
@@ -454,7 +448,6 @@ this.component(SwaggerComponent, {
   --------------
 ```
 
----
 
 ## Quick Reference
 
@@ -479,7 +472,6 @@ this.component(SwaggerComponent, {
 | Premature optimization | Start simple, optimize when needed |
 | Over-engineering | YAGNI - build what you need now |
 
----
 
 ## See Also
 

package/wiki/best-practices/code-style-standards/control-flow.md

@@ -241,5 +241,5 @@ import { QueryBuilder } from '../query';
 ## See Also
 
 - [Error Handling](../error-handling) - Comprehensive error patterns
-- [Logging Reference](../../references/helpers/logger) - Logger API
+- [Logging Reference](../../references/helpers/logger/) - Logger API
 - [Function Patterns](./function-patterns) - Method organization

package/wiki/best-practices/code-style-standards/index.md

@@ -107,4 +107,3 @@ import { QueryBuilder } from './query';
 
 - [Architectural Patterns](../architectural-patterns) - High-level design
 - [Common Pitfalls](../common-pitfalls) - Mistakes to avoid
-- [@venizia/dev-configs Reference](../../references/src-details/dev-configs) - Full tooling docs

package/wiki/best-practices/code-style-standards/tooling.md

@@ -119,8 +119,6 @@ Use the centralized TypeScript configs:
 | `strict` | `true` | Strict type checking |
 | `skipLibCheck` | `true` | Faster compilation |
 
-See [`@venizia/dev-configs` documentation](../../references/src-details/dev-configs) for full details.
-
 ## IDE Integration
 
 ### VS Code
@@ -152,4 +150,3 @@ See [`@venizia/dev-configs` documentation](../../references/src-details/dev-conf
 
 - [Naming Conventions](./naming-conventions) - File and class naming
 - [Type Safety](./type-safety) - TypeScript best practices
-- [@venizia/dev-configs Reference](../../references/src-details/dev-configs) - Full documentation

package/wiki/best-practices/contribution-workflow.md

@@ -17,8 +17,8 @@ feature/*, fix/*, docs/* (your work)
 ```
 
 **Important:**
-- ✅ Create PRs to `develop` branch
-- ❌ Do NOT create PRs to `main` branch
+- Create PRs to `develop` branch
+- Do NOT create PRs to `main` branch
 - `main` only accepts merges from `develop`
 - Releases are tagged in git (e.g., `v1.0.0`)
 
@@ -125,10 +125,10 @@ git checkout -b feature/your-feature-name
 ### Step 2: Make Changes
 
 **Checklist:**
-- ✅ Follow [Code Style Standards](./code-style-standards/)
-- ✅ Follow [Architectural Patterns](./architectural-patterns.md)
-- ✅ Add tests for new features/fixes
-- ✅ Update docs in `packages/docs/wiki` if needed
+- Follow [Code Style Standards](./code-style-standards/)
+- Follow [Architectural Patterns](./architectural-patterns.md)
+- Add tests for new features/fixes
+- Update docs in `packages/docs/wiki` if needed
 
 ### Step 3: Commit
 
@@ -183,11 +183,11 @@ git push origin feature/your-feature-name
 | **Breaking changes** | Clearly mark and explain |
 
 **PR Checklist:**
-- ✅ All tests pass
-- ✅ Code is linted and formatted
-- ✅ Documentation updated
-- ✅ Commit messages follow conventions
-- ✅ Branch is up-to-date with `main`
+- All tests pass
+- Code is linted and formatted
+- Documentation updated
+- Commit messages follow conventions
+- Branch is up-to-date with `main`
 
 ## 4. Review Process
 
@@ -205,4 +205,4 @@ git commit -m "fix: address review feedback"
 git push origin feature/your-feature-name
 ```
 
-**Thank you for contributing to Ignis! 🎉**
+**Thank you for contributing to Ignis!**

package/wiki/best-practices/index.md

@@ -5,49 +5,41 @@ Production-ready patterns, security guidelines, and optimization strategies for
 <div class="guide-cards">
 
 <a href="./architectural-patterns" class="guide-card highlight">
-<span class="guide-icon">🏗️</span>
 <h3>Architecture</h3>
 <p>Layered architecture, DI, components, lifecycle hooks</p>
 </a>
 
 <a href="./code-style-standards/" class="guide-card">
-<span class="guide-icon">📝</span>
 <h3>Code Standards</h3>
 <p>Naming, types, patterns, ESLint, Prettier</p>
 </a>
 
 <a href="./security-guidelines" class="guide-card highlight">
-<span class="guide-icon">🔒</span>
 <h3>Security</h3>
 <p>Auth, validation, secrets, CORS, rate limiting</p>
 </a>
 
 <a href="./data-modeling" class="guide-card">
-<span class="guide-icon">🗄️</span>
 <h3>Data Modeling</h3>
 <p>Schemas, enrichers, relations, migrations</p>
 </a>
 
 <a href="./testing-strategies" class="guide-card">
-<span class="guide-icon">🧪</span>
 <h3>Testing</h3>
 <p>Unit tests, integration tests, mocking</p>
 </a>
 
 <a href="./performance-optimization" class="guide-card">
-<span class="guide-icon">⚡</span>
 <h3>Performance</h3>
 <p>Query optimization, caching, pooling</p>
 </a>
 
 <a href="./error-handling" class="guide-card">
-<span class="guide-icon">🚨</span>
 <h3>Error Handling</h3>
 <p>Error patterns, logging, user-friendly messages</p>
 </a>
 
 <a href="./deployment-strategies" class="guide-card">
-<span class="guide-icon">🚀</span>
 <h3>Deployment</h3>
 <p>Docker, Kubernetes, cloud platforms, CI/CD</p>
 </a>
@@ -194,13 +186,11 @@ const data: any = await fetchData(); // Use proper types!
 |-------|-------------|
 | [Contribution Workflow](./contribution-workflow) | Git workflow, PR guidelines, code review |
 
-::: tip New to Ignis?
-Start with the [Getting Started Guide](/guides/) for tutorials, then return here for production-ready patterns.
-:::
+> [!TIP] New to Ignis?
+> Start with the [Getting Started Guide](/guides/) for tutorials, then return here for production-ready patterns.
 
-::: warning Production Deployment?
-Before deploying, review the [Security Guidelines](./security-guidelines) and [Deployment Strategies](./deployment-strategies) thoroughly.
-:::
+> [!WARNING] Production Deployment?
+> Before deploying, review the [Security Guidelines](./security-guidelines) and [Deployment Strategies](./deployment-strategies) thoroughly.
 
 ## See Also
 

package/wiki/best-practices/performance-optimization.md

@@ -32,7 +32,7 @@ Prevent blocking the event loop with Worker Threads:
 - Large file/data processing
 - Any synchronous task > 5ms
 
-> **Deep Dive:** See [Worker Thread Helper](../references/helpers/worker-thread.md) for implementation guide.
+> **Deep Dive:** See [Worker Thread Helper](../references/helpers/worker-thread/) for implementation guide.
 
 ## 3. Optimize Database Queries
 
@@ -127,7 +127,7 @@ Reduce database load with caching:
 
 | Cache Type | Use Case | Implementation |
 |-----------|----------|----------------|
-| **Redis** | Distributed cache, session storage | [Redis Helper](../references/helpers/redis.md) |
+| **Redis** | Distributed cache, session storage | [Redis Helper](../references/helpers/redis/) |
 | **In-Memory** | Single-process cache | `MemoryStorageHelper` |
 
 **Example:**
@@ -390,7 +390,7 @@ logger.log('info', MSG_ORDER_FILLED);
 - Use background flushing to avoid I/O blocking
 - HfLogger uses a lock-free ring buffer (64K entries, 16MB)
 
-> **Deep Dive:** See [Logger Helper](../references/helpers/logger.md) for complete HfLogger API.
+> **Deep Dive:** See [Logger Helper](../references/helpers/logger/) for complete HfLogger API.
 
 ## Performance Checklist
 

package/wiki/best-practices/security-guidelines.md

@@ -68,7 +68,7 @@ const SecureRoute = {
 };
 ```
 
-> **Deep Dive:** See [Authentication Component](../references/components/authentication.md) for full setup guide.
+> **Deep Dive:** See [Authentication Component](../references/components/authentication/) for full setup guide.
 
 **Access user in protected routes:**
 ```typescript
@@ -462,6 +462,6 @@ Before deploying to production, verify:
 
 ## See Also
 
-- [Authentication Component](../references/components/authentication) - JWT setup and configuration
+- [Authentication Component](../references/components/authentication/) - JWT setup and configuration
 - [Common Pitfalls](./common-pitfalls) - Security-related mistakes to avoid
 - [Deployment Strategies](./deployment-strategies) - Secure deployment practices

package/wiki/best-practices/troubleshooting-tips.md

@@ -118,7 +118,7 @@ cat .env | grep APP_ENV
 - Use `try-catch` blocks to catch and log errors
 - Check database queries with Drizzle's logging: `{ logger: true }`
 
-> **Deep Dive:** See [Logger Helper](../references/helpers/logger.md) for advanced logging configuration.
+> **Deep Dive:** See [Logger Helper](../references/helpers/logger/) for advanced logging configuration.
 
 ## 6. Request ID Tracking
 

package/wiki/guides/core-concepts/application/bootstrapping.md

@@ -66,10 +66,10 @@ export class Application extends BaseApplication {
 ```
 
 **Benefits:**
-- ✅ **Convention-based** - Follow naming patterns, framework does the rest
-- ✅ **Scalable** - Add 100 controllers without changing application code
-- ✅ **Clean** - No constructor bloat
-- ✅ **Team-friendly** - No merge conflicts on registration
+- **Convention-based** - Follow naming patterns, framework does the rest
+- **Scalable** - Add 100 controllers without changing application code
+- **Clean** - No constructor bloat
+- **Team-friendly** - No merge conflicts on registration
 
 ## How It Works
 
@@ -542,7 +542,7 @@ npx glob "your-pattern/**/*.controller.js"
 
 ## Best Practices
 
-### ✅ DO
+### DO
 
 - Follow naming conventions consistently
 - Use boot system for applications with > 5 artifacts per type
@@ -550,7 +550,7 @@ npx glob "your-pattern/**/*.controller.js"
 - Keep boot options in config file
 - Use debug logging during development
 
-### ❌ DON'T
+### DON'T
 
 - Mix manual and auto registration (choose one approach)
 - Use boot for tiny applications (< 5 total artifacts)
@@ -568,7 +568,6 @@ npx glob "your-pattern/**/*.controller.js"
 
 - **References:**
   - [Bootstrapping API](/references/base/bootstrapping) - Complete API reference
-  - [Boot Package](/references/src-details/boot) - Boot system internals
   - [Dependency Injection](/references/base/dependency-injection) - DI container
 
 - **Tutorials:**

package/wiki/guides/core-concepts/components-guide.md

@@ -501,7 +501,7 @@ export class MyComponent extends BaseComponent {
 
 - **References:**
   - [BaseComponent API](/references/base/components) - Complete API reference
-  - [Authentication Component](/references/components/authentication) - Real-world component example
+  - [Authentication Component](/references/components/authentication/) - Real-world component example
   - [Health Check Component](/references/components/health-check) - Simple component example
 
 - **Best Practices:**

package/wiki/guides/core-concepts/components.md

@@ -113,10 +113,10 @@ export class Application extends BaseApplication {
 
 - **References:**
   - [BaseComponent API](/references/base/components) - Complete API reference
-  - [Authentication Component](/references/components/authentication) - JWT authentication
+  - [Authentication Component](/references/components/authentication/) - JWT authentication
   - [Health Check Component](/references/components/health-check) - Health endpoints
   - [Swagger Component](/references/components/swagger) - API documentation
-  - [Socket.IO Component](/references/components/socket-io) - WebSocket support
+  - [Socket.IO Component](/references/components/socket-io/) - WebSocket support
 
 - **Best Practices:**
   - [Architectural Patterns](/best-practices/architectural-patterns) - Component design patterns

package/wiki/guides/core-concepts/dependency-injection.md

@@ -4,7 +4,7 @@ Dependency Injection (DI) enables loosely coupled, testable code by automaticall
 
 > **Deep Dive:** See [DI Reference](../../references/base/dependency-injection.md) for technical details on Container, Binding, and `@inject`.
 
-> **Standalone Package:** The core DI container is available as the standalone `@venizia/ignis-inversion` package for use outside the Ignis framework. See [Inversion Package Reference](../../references/src-details/inversion.md) for details.
+> **Standalone Package:** The core DI container is available as the standalone `@venizia/ignis-inversion` package for use outside the Ignis framework. See [Inversion Package Reference](/references/helpers/inversion/) for details.
 
 ## Core Concepts
 
@@ -244,9 +244,8 @@ describe('UserService', () => {
 | **Lifecycle** | Managed by framework | You control it |
 | **Use Case** | Main application | Testing, isolated modules, workers |
 
-::: tip
-The `Application` class extends `Container`, so all container methods (`bind`, `get`, `getSync`) are available on your application instance. Standalone containers are useful when you need isolation from the main application context.
-:::
+> [!TIP]
+> The `Application` class extends `Container`, so all container methods (`bind`, `get`, `getSync`) are available on your application instance. Standalone containers are useful when you need isolation from the main application context.
 
 ## See Also
 
@@ -258,7 +257,7 @@ The `Application` class extends `Container`, so all container methods (`bind`, `
 
 - **References:**
   - [Dependency Injection API](/references/base/dependency-injection) - Complete API reference
-  - [Inversion Helper](/references/helpers/inversion) - DI container utilities
+  - [Inversion Helper](/references/helpers/inversion/) - DI container utilities
   - [Glossary](/guides/reference/glossary#dependency-injection-di) - DI concepts explained
 
 - **Tutorials:**

package/wiki/guides/core-concepts/persistent/datasources.md

@@ -2,9 +2,8 @@
 
 A DataSource manages database connections and supports **schema auto-discovery** from repositories.
 
-::: info PostgreSQL First
-IGNIS currently focuses on **PostgreSQL** as the primary database. Support for other database systems (MySQL, SQLite, etc.) is planned for future releases.
-:::
+> [!NOTE] PostgreSQL First
+> IGNIS currently focuses on **PostgreSQL** as the primary database. Support for other database systems (MySQL, SQLite, etc.) is planned for future releases.
 
 ## Creating a DataSource
 
@@ -106,8 +105,8 @@ export class Application extends BaseApplication {
 | Driver | Package | Status |
 |--------|---------|--------|
 | `node-postgres` | `pg` | ✅ Supported |
-| `mysql2` | `mysql2` | 🔜 Planned |
-| `better-sqlite3` | `better-sqlite3` | 🔜 Planned |
+| `mysql2` | `mysql2` | Planned |
+| `better-sqlite3` | `better-sqlite3` | Planned |
 
 ## DataSource Template
 

package/wiki/guides/core-concepts/services.md

@@ -94,7 +94,7 @@ This layered architecture makes your application:
 - **References:**
   - [BaseService API](/references/base/services) - Complete API reference
   - [Providers](/references/base/providers) - Factory pattern for runtime instantiation
-  - [Logger Helper](/references/helpers/logger) - Logging in services
+  - [Logger Helper](/references/helpers/logger/) - Logging in services
 
 - **Best Practices:**
   - [Architectural Patterns](/best-practices/architectural-patterns) - Service layer design

package/wiki/guides/get-started/5-minute-quickstart.md

@@ -2,7 +2,7 @@
 
 Build your first Ignis API endpoint in 5 minutes. No database, no complex setup - just a working "Hello World" API.
 
-**⏱️ Time to Complete:** ~5 minutes
+**Time to Complete:** ~5 minutes
 
 > **Prerequisites:** [Bun installed](./setup) and basic TypeScript knowledge.
 
@@ -262,13 +262,12 @@ You might wonder why we set up TypeScript, ESLint, and Prettier configs in a "qu
 - **Team Ready** — New developers can onboard faster with familiar structure
 - **CI/CD Friendly** — Lint and format checks work out of the box
 
-::: tip
-All configs extend from `@venizia/dev-configs`, so you get updates automatically. Customize by overriding specific rules in your local config files.
-:::
+> [!TIP]
+> All configs extend from `@venizia/dev-configs`, so you get updates automatically. Customize by overriding specific rules in your local config files.
 
 ## Next Steps
 
-✅ **You have a working API!**
+**You have a working API!**
 
 **Want more?**
 

package/wiki/guides/get-started/philosophy.md

@@ -4,7 +4,6 @@ Ignis combines the structured, enterprise-grade development experience of **Loop
 
 <div class="philosophy-hero">
 <div class="hero-content">
-<span class="hero-icon">🔥</span>
 <div class="hero-text">
 <strong>Enterprise patterns. Hono performance. Modern simplicity.</strong>
 <span>The framework for developers who want structure without the weight.</span>
@@ -20,7 +19,6 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 
 <div class="landscape-card minimal">
 <div class="card-header">
-<span class="card-icon">⚡</span>
 <h3>Express, Hono, Fastify, Koa</h3>
 <span class="card-badge">Minimal</span>
 </div>
@@ -36,7 +34,6 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 
 <div class="landscape-card balanced">
 <div class="card-header">
-<span class="card-icon">🔥</span>
 <h3>Ignis, Ts.ED</h3>
 <span class="card-badge">Balanced</span>
 </div>
@@ -52,7 +49,6 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 
 <div class="landscape-card enterprise">
 <div class="card-header">
-<span class="card-icon">🏢</span>
 <h3>NestJS, LoopBack 4, AdonisJS</h3>
 <span class="card-badge">Enterprise</span>
 </div>
@@ -164,9 +160,9 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 <thead>
 <tr>
 <th>Aspect</th>
-<th><span class="header-icon">⚡</span> Minimal (Hono/Express)</th>
-<th><span class="header-icon">🏢</span> Enterprise (NestJS/LoopBack)</th>
-<th class="highlight-col"><span class="header-icon">🔥</span> Ignis</th>
+<th>Minimal (Hono/Express)</th>
+<th>Enterprise (NestJS/LoopBack)</th>
+<th class="highlight-col">Ignis</th>
 </tr>
 </thead>
 <tbody>
@@ -223,9 +219,9 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 <thead>
 <tr>
 <th>Feature</th>
-<th><span class="header-icon">⚡</span> Minimal</th>
-<th><span class="header-icon">🏢</span> Enterprise</th>
-<th class="highlight-col"><span class="header-icon">🔥</span> Ignis</th>
+<th>Minimal</th>
+<th>Enterprise</th>
+<th class="highlight-col">Ignis</th>
 </tr>
 </thead>
 <tbody>
@@ -276,9 +272,9 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 <thead>
 <tr>
 <th>Aspect</th>
-<th><span class="header-icon">⚡</span> Hono</th>
-<th><span class="header-icon">🏢</span> NestJS</th>
-<th class="highlight-col"><span class="header-icon">🔥</span> Ignis</th>
+<th>Hono</th>
+<th>NestJS</th>
+<th class="highlight-col">Ignis</th>
 </tr>
 </thead>
 <tbody>
@@ -339,7 +335,6 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 <div class="synthesis">
 
 <div class="synthesis-box source">
-<div class="synthesis-icon">🏗️</div>
 <h4>LoopBack 4</h4>
 <ul>
 <li>DI Container</li>
@@ -352,7 +347,6 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 <div class="synthesis-operator">+</div>
 
 <div class="synthesis-box source">
-<div class="synthesis-icon">⚡</div>
 <h4>Hono</h4>
 <ul>
 <li>Blazing Speed</li>
@@ -365,7 +359,6 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 <div class="synthesis-operator">=</div>
 
 <div class="synthesis-box result">
-<div class="synthesis-icon">🔥</div>
 <h4>Ignis</h4>
 <ul>
 <li>DI + Speed</li>
@@ -382,7 +375,7 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 <div class="excel-section">
 
 <div class="excel-card minimal">
-<h3>⚡ Minimal Frameworks</h3>
+<h3>Minimal Frameworks</h3>
 <p class="excel-subtitle">Hono, Express, Fastify</p>
 <div class="excel-pros">
 <h4>Strengths</h4>
@@ -407,7 +400,7 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 </div>
 
 <div class="excel-card ignis">
-<h3>🔥 Ignis</h3>
+<h3>Ignis</h3>
 <p class="excel-subtitle">The balanced choice</p>
 <div class="excel-pros">
 <h4>Strengths</h4>
@@ -432,7 +425,7 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 </div>
 
 <div class="excel-card enterprise">
-<h3>🏢 Enterprise Frameworks</h3>
+<h3>Enterprise Frameworks</h3>
 <p class="excel-subtitle">NestJS, LoopBack, AdonisJS</p>
 <div class="excel-pros">
 <h4>Strengths</h4>
@@ -536,25 +529,21 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 <div class="perfect-grid">
 
 <div class="perfect-card">
-<span class="perfect-icon">🛒</span>
 <h4>Production APIs</h4>
 <p>10-100+ endpoints with enterprise patterns. Controllers, services, repositories — all built-in and ready.</p>
 </div>
 
 <div class="perfect-card">
-<span class="perfect-icon">👥</span>
 <h4>Teams of Any Size</h4>
 <p>Solo developers to large teams. Consistent patterns, DI for testing, scales with your needs.</p>
 </div>
 
 <div class="perfect-card">
-<span class="perfect-icon">🚀</span>
 <h4>Performance-Critical Apps</h4>
 <p>Hono's speed with enterprise structure. ~140k req/s with full DI, validation, and OpenAPI.</p>
 </div>
 
 <div class="perfect-card">
-<span class="perfect-icon">⚡</span>
 <h4>Modern Bun Projects</h4>
 <p>ESM native, Bun optimized. Build to single executable file for easy deployment.</p>
 </div>
@@ -644,7 +633,6 @@ When building REST APIs with Node.js/Bun, developers choose from three categorie
 </div>
 
 <div class="cta-card">
-<span class="cta-icon">🔥</span>
 <p><strong>IGNIS</strong> is ideal for developers who want enterprise patterns with modern performance. Start building today with structure that scales.</p>
 </div>
 

package/wiki/guides/index.md

@@ -5,37 +5,31 @@ Welcome to Ignis — a TypeScript framework that combines enterprise architectur
 <div class="guide-cards">
 
 <a href="./get-started/setup" class="guide-card">
-<span class="guide-icon">🛠️</span>
 <h3>Setup</h3>
 <p>Install Bun, PostgreSQL, and configure your IDE</p>
 </a>
 
 <a href="./get-started/5-minute-quickstart" class="guide-card highlight">
-<span class="guide-icon">⚡</span>
 <h3>5-Min Quickstart</h3>
 <p>Your first endpoint in 5 minutes</p>
 </a>
 
 <a href="./tutorials/complete-installation" class="guide-card">
-<span class="guide-icon">📦</span>
 <h3>Full Installation</h3>
 <p>Production-ready project setup</p>
 </a>
 
 <a href="./tutorials/building-a-crud-api" class="guide-card">
-<span class="guide-icon">🗄️</span>
 <h3>Build a CRUD API</h3>
 <p>Complete Todo API with database</p>
 </a>
 
 <a href="./tutorials/testing" class="guide-card">
-<span class="guide-icon">🧪</span>
 <h3>Testing</h3>
 <p>Write tests for your application</p>
 </a>
 
 <a href="./get-started/philosophy" class="guide-card">
-<span class="guide-icon">💡</span>
 <h3>Philosophy</h3>
 <p>Why Ignis? Design decisions explained</p>
 </a>
@@ -84,6 +78,5 @@ Welcome to Ignis — a TypeScript framework that combines enterprise architectur
 
 </div>
 
-::: tip New to backend development?
-Check out our [Glossary](./reference/glossary) for explanations of key terms like Controllers, Repositories, and Dependency Injection.
-:::
+> [!TIP] New to backend development?
+> Check out our [Glossary](./reference/glossary) for explanations of key terms like Controllers, Repositories, and Dependency Injection.