Merge pull request #667 from aXenDeveloper/integrate_vitnode_with_docs

docs: Integrate vitnode with docs

Author: aXenDeveloper

.github/docs/tests_plan.md

@@ -2,7 +2,7 @@
 
 ## 1. Introduction
 
-This document outlines the testing strategy for the VitNode framework. The goal is to ensure the reliability, functionality, and performance of the core framework (`packages/vitnode`), the web application (`apps/web`), and associated plugins. We will utilize Vitest for unit and integration testing and Playwright for end-to-end testing.
+This document outlines the testing strategy for the VitNode framework. The goal is to ensure the reliability, functionality, and performance of the core framework (`packages/vitnode`), the web application (`apps/docs`), and associated plugins. We will utilize Vitest for unit and integration testing and Playwright for end-to-end testing.
 
 ## 2. Goals
 
@@ -24,13 +24,13 @@ This document outlines the testing strategy for the VitNode framework. The goal
 ### 4.1. Unit Tests (Vitest)
 
 **Scope:** Test individual functions, components, and utilities in isolation.
-**Location:** Primarily within `packages/vitnode` and utility directories in `apps/web`.
+**Location:** Primarily within `packages/vitnode` and utility directories in `apps/docs`.
 
 **Areas to Cover:**
 
 - **Core Utilities:** Functions in `packages/vitnode/src/lib`, helpers, etc.
 - **API Helpers:** Route building, validation logic using `@hono/zod-openapi`.
-- **UI Components:** Basic rendering tests, prop validation for components in `packages/vitnode/src/components` and `apps/web/src/components`.
+- **UI Components:** Basic rendering tests, prop validation for components in `packages/vitnode/src/components` and `apps/docs/src/components`.
 - **Configuration Loading:** Ensure `vitnode.config.ts` is loaded and parsed correctly.
 - **Internationalization (i18n):** Test translation loading and formatting utilities.
 
@@ -42,15 +42,15 @@ This document outlines the testing strategy for the VitNode framework. The goal
 **Areas to Cover:**
 
 - **API Endpoints:** Test request handling, validation, middleware execution, and response generation for Hono.js routes defined in `packages/vitnode/src/api`. Example: [`testRoute`](packages/vitnode/src/api/modules/users/routes/test.route.ts).
-- **Server Actions:** Test form submissions, data mutations, and interactions with the database within `apps/web`.
+- **Server Actions:** Test form submissions, data mutations, and interactions with the database within `apps/docs`.
 - **Database Interactions:** Verify Drizzle ORM queries, schema interactions, and data integrity (using a test database).
 - **Authentication Logic:** Test credential verification, session creation/validation (including durations), email verification, password reset, and SSO provider interactions (Google, GitHub, Facebook).
 - **Plugin Integration:** Test how core systems interact with plugin-provided extensions (routes, hooks, etc.).
 
 ### 4.3. End-to-End Tests (Playwright)
 
 **Scope:** Simulate real user scenarios by interacting with the application through a browser.
-**Location:** A dedicated `e2e` or `tests` directory at the root or within `apps/web`.
+**Location:** A dedicated `e2e` or `tests` directory at the root or within `apps/docs`.
 
 **Areas to Cover:**
 

.vscode/settings.json

@@ -1,5 +1,5 @@
 {
-  "cSpell.words": ["sonner", "vitnode"],
+  "cSpell.words": ["fumadocs", "sonner", "vitnode"],
   "github.copilot.chat.commitMessageGeneration.instructions": [
     {
       "text": "Follow the Conventional Commits format strictly for commit messages. Use the structure below:\n\n```\n<type>[optional scope]: <gitmoji> <description>\n```\n\nGuidelines:\n\n1. **Type and Scope**: Choose an appropriate type (e.g., `feat`, `fix`, `refactor`, `docs`) and optional scope to describe the affected module or feature.\n\n2. **Gitmoji**: Include a relevant `gitmoji` that best represents the nature of the change.\n\n3. **Description**: Write a concise, informative description in the header; use backticks if referencing code or specific terms.\n\nCommit messages should be clear, informative, and professional, aiding readability and project tracking."

apps/web/.prettierrc.mjs apps/docs/.prettierrc.mjsapps/web/.prettierrc.mjs renamed to apps/docs/.prettierrc.mjs

@@ -3,6 +3,10 @@ title: Dropdown Menu
 description: A dropdown menu component for building interactive menus in your application.
 ---
 
+## Preview
+
+<Preview name="dropdown-menu" />
+
 ## Usage
 
 ```ts

apps/web/components.json apps/docs/components.jsonapps/web/components.json renamed to apps/docs/components.json

@@ -0,0 +1,8 @@
+import eslintVitNode from '@vitnode/eslint-config/eslint';
+
+export default [
+  ...eslintVitNode,
+  {
+    ignores: ['.source'],
+  },
+];

apps/docs/content/docs/ui/dropdown-menu.mdx

@@ -0,0 +1,10 @@
+/// <reference types="next-intl" />
+
+import type core from './src/locales/@vitnode/core/en.json';
+import type blog from './src/locales/@vitnode/blog/en.json';
+
+declare module 'next-intl' {
+  interface AppConfig {
+    Messages: typeof core & typeof blog;
+  }
+}