@mgks/docmd 0.1.0

package/docs/configuration.md

@@ -0,0 +1,166 @@
+---
+title: "Configuration"
+description: "Detailed explanation of all options available in the docmd config.js file, including logo, theming, plugins, and more."
+---
+
+# Configuration (`config.js`)
+
+`docmd` uses a `config.js` file in the root of your documentation project to control various aspects of your site. This file should export a JavaScript object containing your configuration options.
+
+## Example `config.js` Structure:
+
+```javascript
+// config.js
+module.exports = {
+  siteTitle: 'My Awesome Project Docs',
+  logo: {
+    light: '/assets/images/logo-light.svg', // Path to logo for light mode
+    dark: '/assets/images/logo-dark.svg',   // Path to logo for dark mode
+    alt: 'My Project Logo',                 // Alt text for the logo
+    // href: '/',                           // Optional: link for the logo, defaults to site root
+    // height: '30px',                      // Optional: specify height via CSS is often better
+  },
+  srcDir: 'docs',
+  outputDir: 'site',
+
+  theme: {
+    name: 'default',        // Name of the built-in theme to use (e.g., 'default', 'classic')
+    defaultMode: 'light',   // 'light' or 'dark'
+    enableModeToggle: true, // Show UI button to toggle light/dark modes
+    customCss: [            // Array of paths to your custom CSS files
+      // '/css/override-styles.css', // Paths are relative to the outputDir root
+    ],
+    // options: { /* Future: theme-specific options */ }
+  },
+
+  customJs: [               // Array of paths to your custom JS files
+    // '/js/extra-functionality.js', // Loaded at the end of the body
+  ],
+
+  plugins: [
+    // Example: Enable built-in SEO enhancements
+    // ['seo', {
+    //   defaultDescription: 'A fantastic site about interesting things.',
+    //   openGraph: { defaultImage: '/assets/images/og-social-default.png' },
+    //   twitter: { cardType: 'summary_large_image', siteUsername: '@MyProject' }
+    // }],
+
+    // Example: Enable Google Analytics (Universal Analytics)
+    // ['analytics-google-ua', { trackingId: 'UA-XXXXXXXXX-Y' }],
+
+    // Example: Enable Google Analytics 4
+    // ['analytics-google-v4', { measurementId: 'G-XXXXXXXXXX' }],
+  ],
+
+  navigation: [
+    { title: 'Home', path: '/', icon: 'home' }, // Icon names correspond to SVGs
+    {
+      title: 'Guides',
+      icon: 'book-open',
+      children: [
+        { title: 'Installation', path: '/guides/installation', icon: 'download' },
+        { title: 'Project GitHub', path: 'https://github.com/mgks/docmd', icon: 'github', external: true }
+      ],
+    },
+  ],
+  footer: '© ' + new Date().getFullYear() + ' My Project. Made with [docmd](https://github.com/mgks/docmd).',
+  favicon: '/assets/favicon.ico', // Path relative to outputDir root
+};
+```
+
+## Top-Level Options
+
+### `siteTitle`
+*   **Type:** `String`
+*   **Required:** Yes
+*   **Description:** The main title for your documentation site. Used as a fallback if no logo is provided, in the HTML `<title>` tag, and potentially by plugins (e.g., SEO).
+*   **Example:** `siteTitle: 'My Product Documentation'`
+
+### `logo`
+*   **Type:** `Object`
+*   **Optional**
+*   **Description:** Configures a logo to be displayed in the site header/sidebar, typically replacing or complementing the `siteTitle` text.
+*   **Properties:**
+    *   `light` (String, Required if using logo): Path to the logo image file for light mode. Path should be relative to the `outputDir` root (e.g., `/assets/images/logo-light.svg`).
+    *   `dark` (String, Required if using logo): Path to the logo image file for dark mode.
+    *   `alt` (String, Required if using logo): Alternative text for the logo image (for accessibility).
+    *   `href` (String, Optional): The URL the logo should link to. Defaults to the site root (`/`).
+    *   `height` (String, Optional): Suggested height for the logo (e.g., `'30px'`, `'2rem'`). It's often better to control size via CSS for more flexibility.
+*   **Note:** Ensure your logo image files are copied to the specified paths within your `outputDir` during the build. Usually, this means placing them in an assets folder that `docmd` copies.
+
+### `srcDir`
+*   **Type:** `String`
+*   **Default:** `'docs'`
+*   **Description:** Directory containing your Markdown source files.
+
+### `outputDir`
+*   **Type:** `String`
+*   **Default:** `'site'`
+*   **Description:** Directory where the static site will be generated.
+
+## `theme` (Object)
+
+Configures the visual theme of your site.
+
+### `theme.name`
+*   **Type:** `String`
+*   **Default:** `'default'`
+*   **Description:** Specifies which built-in `docmd` theme to use. Future versions may offer multiple themes like `'classic'`, `'minimalist-pro'`. Each theme would correspond to a CSS file (e.g., `theme-default.css`).
+*   **See Also:** [Available Themes](/theming/available-themes/)
+
+### `theme.defaultMode`
+*   **Type:** `String`
+*   **Default:** `'light'`
+*   **Values:** `'light'` or `'dark'`
+*   **Description:** Sets the default color mode (light or dark) for the site.
+
+### `theme.enableModeToggle`
+*   **Type:** `Boolean`
+*   **Default:** `true` (assuming it's now a core feature)
+*   **Description:** If `true`, a UI toggle button will be displayed allowing users to switch between light and dark modes. Their preference is typically saved in `localStorage`.
+
+### `theme.customCss`
+*   **Type:** `Array` of `String`
+*   **Default:** `[]` (empty array)
+*   **Description:** An array of paths to your custom CSS files. These files will be linked in the `<head>` of every page *after* the main theme CSS, allowing you to override or extend styles.
+*   **Paths:** Should be relative to the `outputDir` root (e.g., `'/css/my-styles.css'`). You are responsible for ensuring these files exist at the specified location in your final `site/` output (e.g., by placing them in an assets folder that `docmd` copies, or in your project's static assets if your `srcDir` is part of a larger project).
+*   **Example:** `customCss: ['/assets/css/custom-branding.css']`
+
+### `theme.options` (Future Placeholder)
+*   **Type:** `Object`
+*   **Description:** A placeholder for theme-specific configuration options if a theme (`theme.name`) exposes its own settings (e.g., primary color, font choices for a more advanced theme).
+
+## `customJs` (Array of String)
+*   **Type:** `Array` of `String`
+*   **Default:** `[]`
+*   **Description:** An array of paths to your custom JavaScript files. These files will be included as `<script>` tags just before the closing `</body>` tag on every page.
+*   **Paths:** Should be relative to the `outputDir` root (e.g., `'/js/my-analytics-alternative.js'`).
+*   **Example:** `customJs: ['/assets/js/interactive-component.js']`
+
+## `plugins` (Array)
+*   **Type:** `Array`
+*   **Default:** `[]`
+*   **Description:** An array to configure and enable plugins. `docmd` will ship with some core "local" plugins (like SEO and Analytics) that you can enable here. Future versions might support third-party plugins.
+*   **Format:** Each item in the array is typically another array: `['plugin-name', { pluginOptions }]` or a direct `require()` for local project plugins (advanced usage).
+*   **Built-in Plugin Examples:**
+    *   `['seo', { defaultDescription: '...', openGraph: { ... }, ... }]`
+    *   `['analytics-google-ua', { trackingId: 'UA-...' }]`
+    *   `['analytics-google-v4', { measurementId: 'G-...' }]`
+*   **See Also:** [Plugins](/plugins/)
+
+## `navigation` (Array of Objects)
+*   **Description:** Defines the sidebar navigation. (Content mostly same as before, but add the `icon` property explanation).
+*   **Navigation Item Properties:**
+    *   `title` (String, Required)
+    *   `path` (String, Required for direct links)
+    *   `children` (Array, Optional)
+    *   `icon` (String, Optional): The name of an SVG icon to display next to the navigation item. `docmd` will look for an SVG file named `icon-name.svg` in its bundled assets (e.g., `home` for `home.svg`). Ensure the chosen icon name corresponds to an available SVG. See [Theming > Icons](/theming/icons/) for more details.
+    *   `external` (Boolean, Optional): If set to `true`, the `path` is treated as an absolute external URL and the link will open in a new tab (`target="_blank"`). Defaults to `false`.
+
+## `footer` (String, Optional)
+*   **Description:** Custom footer text (Markdown supported).
+
+## `favicon` (String, Optional)
+*   **Description:** Path to your favicon file, relative to `outputDir` root.
+
+This file needs significant detail for each new option, explaining its purpose, type, default value, and how to use it with examples.

package/docs/contributing.md

@@ -0,0 +1,86 @@
+---
+title: "Contributing to docmd"
+description: "Learn how you can contribute to the development and improvement of docmd."
+---
+
+# Contributing to docmd
+
+Thank you for your interest in contributing to `docmd`! We welcome contributions from the community to help make `docmd` even better. Whether it's reporting a bug, suggesting a feature, improving documentation, or writing code, your help is appreciated.
+
+## How to Contribute
+
+There are many ways to contribute to `docmd`:
+
+*   **Reporting Bugs:** If you find a bug, please open an issue on our [GitHub Issues page](https://github.com/mgks/docmd/issues). Provide as much detail as possible, including steps to reproduce, expected behavior, and actual behavior.
+*   **Suggesting Features:** Have ideas for improvements? Open an issue and describe what you'd like to see.
+*   **Improving Documentation:** The documentation you're reading now (this site itself!) is built with `docmd` and lives in the `docs/` directory of the repository.
+*   **Writing Code:** If you're interested in fixing bugs or implementing new features, read on for development setup instructions.
+
+## Development Setup
+
+To set up `docmd` for local development:
+
+1. **Fork the Repository:**
+   Click the "Fork" button on the [docmd GitHub page](https://github.com/mgks/docmd) to create your own copy.
+
+2. **Clone Your Fork:**
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/docmd.git
+   cd docmd
+   ```
+
+3. **Install Dependencies:**
+   ```bash
+   npm install
+   ```
+
+### Development Workflow
+
+`docmd` uses Node.js and npm.
+
+1. **Make Your Changes:**
+   * Fix bugs or add features in the `/src` directory.
+   * Add or update tests in the `/tests` directory (if applicable).
+   * Update or add documentation in the `/docs` directory to reflect your changes.
+
+2. **Link for Local Testing:**
+   To use your development version of `docmd` as a global command-line tool on your system:
+   ```bash
+   npm link
+   ```
+   This allows you to run `docmd` from any directory and test your changes.
+
+3. **Test Your Changes:**
+   * Run automated tests with `npm test` (if available).
+   * Test your changes by running `docmd build` or `docmd dev` (which will use `docmd` itself to build its own documentation located in `docs/`).
+
+4. **Code Style:**
+   * Follow the existing code style and formatting.
+   * Consider running `npm run lint` to check for style issues (if set up).
+
+## Pull Request Process
+
+Once you're satisfied with your changes:
+
+1. **Commit Your Changes:**
+   ```bash
+   git add .
+   git commit -m "Brief description of your changes"
+   ```
+
+2. **Push to Your Fork:**
+   ```bash
+   git push origin main  # or the branch you created
+   ```
+
+3. **Submit a Pull Request:**
+   Go to your fork on GitHub and open a pull request to the `main` branch of the original `mgks/docmd` repository. Provide a clear description of your changes.
+
+4. **Code Review:**
+   Maintainers will review your PR and may suggest changes or improvements. Please be responsive to feedback.
+
+## Code of Conduct
+
+Please be respectful and considerate when interacting with others in the project. We aim to foster an inclusive and welcoming community.
+
+Thank you for helping make `docmd` a great tool for documentation!

package/docs/deployment.md

@@ -0,0 +1,129 @@
+---
+title: "Deployment"
+description: "Learn how to deploy your docmd-generated static site to various hosting platforms, including GitHub Pages."
+---
+
+# Deploying Your docmd Site
+
+Once you've built your documentation site using `docmd build`, the entire static site is generated into the `site/` directory (or your configured `outputDir`). This `site/` directory contains all the HTML, CSS, JavaScript, and assets needed, making it deployable to any static hosting service.
+
+## Building for Production
+
+Before deployment, ensure you build your site in production mode:
+
+```bash
+docmd build
+```
+
+This generates optimized HTML, CSS, and assets ready for production use. In production, `docmd` may:
+- Minify CSS and JavaScript assets (future feature)
+- Optimize HTML output
+
+## Deployment Options
+
+Since `docmd` generates a standard static site, you can use any static hosting service. Here are some popular options:
+
+### GitHub Pages
+
+GitHub Pages is a popular and free way to host static sites directly from your GitHub repository. `docmd` sites are perfectly suited for this.
+
+#### Option 1: Deploy from a Branch
+
+1. **Push your source files and built site to GitHub.**
+2. **Go to your repository settings.**
+3. **Navigate to the "Pages" section.**
+4. **Under "Source", select the branch and directory where your built site is located.**
+
+The simplest approach is to choose one of:
+
+*   **Built site in the `docs/` folder on the main branch:**
+    *   Configure `docmd`'s `outputDir` to be `docs` in your `config.js` (e.g., `outputDir: 'docs'`).
+    *   Select "Deploy from a branch" → "main" → "/docs"
+    
+If you set `outputDir: 'docs'`, your `config.js` for `docmd` itself (when building its own docs) would look like:
+
+```javascript
+// config.js for docmd's own docs, deploying from /docs on main
+module.exports = {
+  siteTitle: 'docmd Docs',
+  srcDir: 'documentation', // Assuming actual source MD files are NOT in the output 'docs'
+  outputDir: 'docs',
+  // ... other config ...
+};
+```
+
+#### Option 2: GitHub Actions (Recommended)
+
+The most robust and automated way to deploy to GitHub Pages is using a GitHub Actions workflow. This workflow will run `docmd build` and then deploy the resulting `site/` directory.
+
+Create a file at `.github/workflows/deploy-docs.yml` with the following content:
+
+```yaml
+name: Deploy docmd docs to Pages
+
+on:
+  # Run on pushes to main branch
+  push:
+    branches: ["main"]
+  # Allows manual workflow trigger from Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: '20' # Or the Node.js version docmd supports/requires
+          cache: 'npm'
+      - name: Install docmd (globally or from devDependencies)
+        # If docmd is a dev dependency of the project being documented:
+        # run: npm ci && npm run build:docs # Assuming 'build:docs' script runs 'docmd build'
+        # If installing docmd globally for this action:
+        run: npm install -g docmd # Or your scoped package name e.g. @mgks/docmd
+      - name: Build site with docmd
+        run: docmd build # Assumes config.js is in the root and correctly points to srcDir/outputDir
+      - name: Setup Pages
+        uses: actions/configure-pages@v3
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v2
+        with:
+          # This should be your outputDir path
+          path: './site' # or './docs' if you set outputDir: 'docs'
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v2
+```
+
+Then:
+1.  **Enable GitHub Pages in your repository settings**, selecting "GitHub Actions" as the source.
+2.  **Push the workflow file to your repository**.
+3.  On the next push to `main` (or if you manually trigger the workflow), the Action will run, build your `docmd` site, and deploy it. The URL will be something like `https://YOUR_USERNAME.github.io/YOUR_REPOSITORY/`.
+
+### Other Hosting Options
+
+* **Netlify, Vercel, Cloudflare Pages** - Upload or connect your Git repository and set the build command to your npm script that runs `docmd build`.
+* **Any Web Server** - Simply upload the contents of the `site/` directory to any web server that can serve static files.
+
+By following these guidelines, you can easily get your `docmd`-powered documentation online and accessible to your users.

package/docs/getting-started/basic-usage.md

@@ -0,0 +1,88 @@
+---
+title: "Basic Usage"
+description: "Learn the basic commands to initialize, build, and preview your docmd site."
+---
+
+# Basic Usage
+
+Once `docmd` is [installed](/getting-started/installation/), using it involves a few simple commands to manage your documentation project.
+
+## 1. Initialize Your Project (`docmd init`)
+
+Navigate to the directory where you want to create your documentation project. If the directory doesn't exist, create it first.
+
+```bash
+mkdir my-awesome-docs
+cd my-awesome-docs
+```
+
+Then, run the `init` command:
+
+```bash
+docmd init
+```
+
+This command sets up the basic structure for your `docmd` project:
+
+*   `docs/`: An empty directory where your Markdown source files will live.
+    *   `docs/index.md`: A sample Markdown file to get you started.
+*   `config.js`: A configuration file for your site, pre-filled with sensible defaults.
+
+You'll typically edit `config.js` to set your site title and define the navigation structure, and then start adding your `.md` files to the `docs/` directory.
+
+## 2. Add and Structure Content
+
+Create your Markdown (`.md`) files inside the `docs/` directory. You can organize them into subdirectories as needed. For example:
+
+```
+my-awesome-docs/
+├── docs/
+│   ├── index.md
+│   └── api/
+│       ├── introduction.md
+│       └── endpoints.md
+│   └── guides/
+│       ├── setup.md
+│       └── advanced.md
+└── config.js
+```
+
+Each Markdown file should start with YAML frontmatter to define metadata like the page title. See [Writing Content > Frontmatter](/writing-content/frontmatter/) for details.
+
+## 3. Preview Your Site (`docmd dev`)
+
+While you're writing content or configuring your site, you'll want to see a live preview. The `dev` command starts a local development server with live reloading.
+
+In your project's root directory (e.g., `my-awesome-docs/`), run:
+
+```bash
+docmd dev
+```
+
+This will:
+1.  Perform an initial build of your site.
+2.  Start a web server, typically at `http://localhost:3000`.
+3.  Watch your `docs/` directory and `config.js` for changes.
+4.  Automatically rebuild the site and refresh your browser when changes are detected.
+
+Open `http://localhost:3000` in your web browser to see your site. Any changes you save to your Markdown files or `config.js` will be reflected live in the browser.
+
+To stop the development server, press `Ctrl+C` in your terminal.
+
+## 4. Build Your Static Site (`docmd build`)
+
+When you're ready to deploy your documentation or create a production version, use the `build` command:
+
+```bash
+docmd build
+```
+
+This command:
+1.  Reads your `config.js`.
+2.  Processes all `.md` files in your `docs/` directory.
+3.  Generates the complete static HTML, CSS, and JavaScript assets.
+4.  Outputs the entire site into a `site/` directory (by default, configurable in `config.js`).
+
+The contents of the `site/` directory are all you need to deploy your documentation. You can upload this folder to any static web hosting provider. See [Deployment](/deployment/) for more information.
+
+This covers the fundamental workflow of using `docmd`. Next, you'll want to learn more about [Writing Content](/writing-content/) and [Configuration](/configuration/).

package/docs/getting-started/index.md

@@ -0,0 +1,21 @@
+---
+title: "Getting Started with docmd"
+description: "An overview of how to get up and running with docmd for your documentation needs."
+---
+
+# Getting Started Overview
+
+Welcome to `docmd`! This section will guide you through installing `docmd`, initializing your first documentation project, and understanding the basic commands to build and preview your site.
+
+Whether you're documenting a new open-source project, an internal tool, or just want a simple way to publish Markdown content as a website, `docmd` aims to make the process straightforward and enjoyable.
+
+## What You'll Learn:
+
+*   **[Installation](./installation.md):** How to install `docmd` on your system using npm.
+*   **[Basic Usage](./basic-usage.md):**
+    *   Initializing a new `docmd` project with `docmd init`.
+    *   Adding and structuring your Markdown content.
+    *   Building your static site with `docmd build`.
+    *   Previewing your site with live reloading using `docmd dev`.
+
+Ready to begin? Let's start with [Installation](./installation.md).

package/docs/getting-started/installation.md

@@ -0,0 +1,75 @@
+---
+title: "Installation"
+description: "Learn how to install docmd on your system globally or as a project dependency."
+---
+
+# Installation
+
+You can install `docmd` using npm (Node Package Manager), which comes with Node.js. If you don't have Node.js and npm installed, please visit [nodejs.org](https://nodejs.org/) to download and install them first (Node.js version 20.x or higher is recommended for `docmd`).
+
+## Global Installation (Recommended for CLI Use)
+
+For using `docmd` as a command-line tool across multiple projects, global installation is the most convenient method.
+
+Open your terminal or command prompt and run:
+
+```bash
+npm install -g @mgks/docmd
+```
+
+This command downloads `docmd` and makes the `docmd` executable available in your system's PATH.
+
+### Verify Installation
+After installation, you can verify that `docmd` is installed correctly by running:
+```bash
+docmd --version
+```
+This should print the installed version of `docmd`. You can also see available commands with:
+```bash
+docmd --help
+```
+
+## Local Installation (Per Project)
+
+Alternatively, you might prefer to install `docmd` as a development dependency for a specific project. This is useful if you want to lock down a specific version of `docmd` for that project or use it within npm scripts.
+
+Navigate to your project's root directory in the terminal and run:
+```bash
+npm install --save-dev @mgks/docmd
+```
+*(Or `npm install --save-dev @username/docmd` for a scoped package.)*
+
+When installed locally, `docmd` is not directly available as a global command. You can run it using:
+
+*   **`npx` (Recommended):** `npx` is a tool that comes with npm and allows you to execute package binaries.
+    ```bash
+    npx docmd init
+    npx docmd build
+    ```
+*   **NPM Scripts:** Add scripts to your project's `package.json`:
+    ```json
+    // package.json
+    {
+      "scripts": {
+        "docs:init": "docmd init",
+        "docs:dev": "docmd dev",
+        "docs:build": "docmd build"
+      }
+    }
+    ```
+    Then, you can run them like:
+    ```bash
+    npm run docs:dev
+    npm run docs:build
+    ```
+
+## Troubleshooting
+
+*   **Permission Errors (EACCES):** If you encounter permission errors during global installation on macOS or Linux, you might need to run the command with `sudo`:
+    ```bash
+    sudo npm install -g @mgks/docmd
+    ```
+    However, a better long-term solution is often to [configure npm to use a directory you own](https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally).
+*   **Command Not Found:** If `docmd` is not found after global installation, ensure that the npm global binaries directory is in your system's PATH.
+
+With `docmd` installed, you're ready to move on to [Basic Usage](/getting-started/basic-usage/) to create and manage your documentation site.

package/docs/index.md

@@ -0,0 +1,56 @@
+---
+title: "Minimalist Markdown Docs Generator"
+description: "Generate beautiful, lightweight static documentation sites directly from your Markdown files with docmd. Zero clutter, just content."
+---
+
+# docmd
+
+**Generate beautiful, lightweight static documentation sites directly from your Markdown files. Zero clutter, just content.**
+
+`docmd` is a Node.js-based command-line tool that transforms a directory of Markdown files (`.md`) into a clean, fast, and themeable static website. It prioritizes simplicity for the author, leveraging standard Markdown and intuitive configuration, while producing elegant and functional documentation sites.
+
+::: callout tip
+This very documentation site is built using `docmd`!
+:::
+
+## Core Philosophy
+
+*   **Markdown First:** Your content lives in standard `.md` files with simple YAML frontmatter.
+*   **Minimal Configuration:** Sensible defaults with straightforward overrides via `config.js`.
+*   **Lightweight Build:** Fast generation process using Node.js, no complex framework dependencies for the build itself.
+*   **Beautiful Defaults:** Clean, responsive design with light/dark themes and syntax highlighting out-of-the-box.
+*   **Static Output:** Deploy the generated `site/` folder anywhere (GitHub Pages, Netlify, Vercel, etc.).
+
+## Key Features
+
+*   📝 **Standard Markdown & Frontmatter:** Write content naturally, define page metadata (title, description) easily.
+*   🎨 **Themeable:** Built-in light/dark modes, customizable via CSS variables. Uses `highlight.js` for code blocks.
+*   🧩 **Custom Containers:** Add richer components like callouts, cards, and steps using simple `::: name :::` syntax.
+*   ⚙️ **Config-Driven Navigation:** Define your site structure and sidebar navigation in `config.js`. Supports nested items.
+*   🚀 **Fast Static Build:** Node.js script quickly processes files into optimized HTML & CSS.
+*   💻 **Simple CLI:** Easy-to-use commands (`docmd build`, `docmd init`, `docmd dev`) with clear feedback.
+*   🌐 **Deploy Anywhere:** Generates a standard static `site/` directory.
+
+## Get Started Quickly
+
+1.  **Install `docmd`:**
+    ```bash
+    npm install -g @mgks/docmd
+    ```
+2.  **Initialize Your Project:**
+    ```bash
+    cd my-project-docs
+    docmd init
+    ```
+3.  **Write Your Content:**
+    Create `.md` files in the `docs/` directory.
+4.  **Preview Live:**
+    ```bash
+    docmd dev
+    ```
+5.  **Build for Production:**
+    ```bash
+    docmd build
+    ```
+
+Dive into the [Getting Started](/getting-started/installation/) guide for more details, or explore the sidebar to learn about specific features.