@mgks/docmd 0.3.1 → 0.3.3

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

@@ -1,89 +0,0 @@
----
-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.
-*   `docmd.config.js`: A configuration file for your site, pre-filled with sensible defaults.
-
-You'll typically edit config file 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/
-├── assets/
-├── docs/
-│   ├── index.md
-│   └── api/
-│       ├── introduction.md
-│       └── endpoints.md
-│   └── guides/
-│       ├── setup.md
-│       └── advanced.md
-└── docmd.config.js
-```
-
-Each Markdown file should start with YAML frontmatter to define metadata like the page title. See [Content > Frontmatter](/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 `docmd.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 file 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 `docmd.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 `docmd.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 [Content](/content/) and [Configuration](/configuration/).

package/docs/getting-started/index.md

@@ -1,21 +0,0 @@
----
-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](/getting-started/installation/):** How to install `docmd` on your system using npm.
-*   **[Basic Usage](/getting-started/basic-usage/):**
-    *   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](/getting-started/installation/).

package/docs/getting-started/installation.md

@@ -1,75 +0,0 @@
----
-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 22.x or higher is required 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

@@ -1,168 +0,0 @@
----
-title: "Documentation. Zero Clutter. Just Content."
-description: "A lightweight static documentation site generator that transforms Markdown into beautiful, responsive documentation websites."
-noStyle: true
-components:
-  meta: true
-  favicon: true
-  css: false
-  theme: false
-  themeMode: true
-  scripts: false
-  mainScripts: false
-  lightbox: false
-seo:
-  ldJson:
-    "@context": "https://schema.org"
-    "@type": "SoftwareApplication"
-    name: "docmd"
-    operatingSystem: "Any"
-    applicationCategory: "DeveloperApplication"
-    url: "https://docmd.mgks.dev"
-    description: "docmd is a Node.js-powered static site generator for Markdown documentation. It features custom containers, multiple themes, and zero client-side bloat."
-    creator:
-      "@type": "Person"
-      name: "Ghazi"
-      sameAs:
-        - "https://github.com/mgks"
-        - "https://mgks.dev"
-    codeRepository: "https://github.com/mgks/docmd"
-    releaseNotes: "See GitHub Releases for changelog"
-    programmingLanguage: "Node.js"
-    installUrl: "https://www.npmjs.com/package/@mgks/docmd"
-customHead: |
-  <link rel="stylesheet" href="/assets/css/welcome.css">
-  <script>
-    function toggleTheme() {
-      const currentTheme = document.documentElement.getAttribute('data-theme');
-      const newTheme = currentTheme === 'light' ? 'dark' : 'light';
-      document.documentElement.setAttribute('data-theme', newTheme);
-      localStorage.setItem('docmd-theme', newTheme);
-    }
-    
-    function copyToClipboard(text) {
-      navigator.clipboard.writeText(text).then(() => {
-        const button = event.target.closest('.copy-button');
-        const originalHTML = button.innerHTML;
-        button.innerHTML = '<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><polyline points="20,6 9,17 4,12"></polyline></svg>';
-        button.style.color = '#10b981';
-        setTimeout(() => {
-          button.innerHTML = originalHTML;
-          button.style.color = '';
-        }, 2000);
-      });
-    }
-  </script>
----
-
-<div class="header-top">
-  <button class="theme-toggle" onclick="toggleTheme()" aria-label="Toggle dark/light mode">
-    <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-sun-moon-icon lucide-sun-moon"><path d="M12 8a2.83 2.83 0 0 0 4 4 4 4 0 1 1-4-4"/><path d="M12 2v2"/><path d="M12 20v2"/><path d="m4.9 4.9 1.4 1.4"/><path d="m17.7 17.7 1.4 1.4"/><path d="M2 12h2"/><path d="M20 12h2"/><path d="m6.3 17.7-1.4 1.4"/><path d="m19.1 4.9-1.4 1.4"/></svg>
-  </button>
-</div>
-
-<div class="landing-container">
-  <div class="content-side">
-    <div class="logo">
-      <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-feather-icon lucide-feather"><path d="M12.67 19a2 2 0 0 0 1.416-.588l6.154-6.172a6 6 0 0 0-8.49-8.49L5.586 9.914A2 2 0 0 0 5 11.328V18a1 1 0 0 0 1 1z"/><path d="M16 8 2 22"/><path d="M17.5 15H9"/></svg>
-      <span class="logo-text">docmd</span>
-    </div>
-
-    <h1>Beautiful Documentation.<br />Zero Clutter. Just Content.</h1>
-
-    <p class="tagline">
-      Transform your Markdown files into elegant, responsive documentation sites with zero setup.
-    </p>
-    
-    <div class="features">
-      <div class="feature">
-        <div class="feature-icon">
-          <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-file-down-icon lucide-file-down"><path d="M15 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2V7Z"/><path d="M14 2v4a2 2 0 0 0 2 2h4"/><path d="M12 18v-6"/><path d="m9 15 3 3 3-3"/></svg>
-        </div>
-        <div class="feature-text">
-          <strong>Markdown Powered</strong>
-          Write in Markdown – get clean HTML
-        </div>
-      </div>
-
-      <div class="feature">
-        <div class="feature-icon">
-          <svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-monitor-smartphone-icon lucide-monitor-smartphone"><path d="M18 8V6a2 2 0 0 0-2-2H4a2 2 0 0 0-2 2v7a2 2 0 0 0 2 2h8"/><path d="M10 19v-3.96 3.15"/><path d="M7 19h5"/><rect width="6" height="10" x="16" y="12" rx="2"/></svg>
-        </div>
-        <div class="feature-text">
-          <strong>Responsive Design</strong>
-          Looks great on any device
-        </div>
-      </div>
-
-      <div class="feature">
-        <div class="feature-icon">
-          <svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-sun-icon lucide-sun"><circle cx="12" cy="12" r="4"/><path d="M12 2v2"/><path d="M12 20v2"/><path d="m4.93 4.93 1.41 1.41"/><path d="m17.66 17.66 1.41 1.41"/><path d="M2 12h2"/><path d="M20 12h2"/><path d="m6.34 17.66-1.41 1.41"/><path d="m19.07 4.93-1.41 1.41"/></svg>
-        </div>
-        <div class="feature-text">
-          <strong>Light & Dark Modes</strong>
-          Themes with auto dark mode
-        </div>
-      </div>
-
-      <div class="feature">
-        <div class="feature-icon">
-          <svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 20h9"></path><path d="M16.5 3.5a2.121 2.121 0 0 1 3 3L7 19l-4 1 1-4L16.5 3.5z"></path></svg>
-        </div>
-        <div class="feature-text">
-          <strong>Highly Customizable</strong>
-          Extend with plugins & containers
-        </div>
-      </div>
-    </div>
-
-    <div class="install-section">
-      <div class="install-code">
-        <pre><code>npm install @mgks/docmd</code></pre>
-        <button class="copy-button" onclick="copyToClipboard('npm install @mgks/docmd')" aria-label="Copy npm install command">
-          <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
-            <rect x="9" y="9" width="13" height="13" rx="2" ry="2"></rect>
-            <path d="M5 15H4a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2h9a2 2 0 0 1 2 2v1"></path>
-          </svg>
-        </button>
-      </div>
-    </div>
-
-    <div class="buttons">
-      <a href="/getting-started/" class="btn btn-primary">
-        <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-rocket-icon lucide-rocket"><path d="M4.5 16.5c-1.5 1.26-2 5-2 5s3.74-.5 5-2c.71-.84.7-2.13-.09-2.91a2.18 2.18 0 0 0-2.91-.09z"/><path d="m12 15-3-3a22 22 0 0 1 2-3.95A12.88 12.88 0 0 1 22 2c0 2.72-.78 7.5-6 11a22.35 22.35 0 0 1-4 2z"/><path d="M9 12H4s.55-3.03 2-4c1.62-1.08 5 0 5 0"/><path d="M12 15v5s3.03-.55 4-2c1.08-1.62 0-5 0-5"/></svg>
-        Get Started
-      </a>
-      <a href="https://github.com/mgks/docmd" target="_blank" rel="noopener" class="btn btn-secondary">
-        <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M15 22v-4a4.8 4.8 0 0 0-1-3.5c3 0 6-2 6-5.5.08-1.25-.27-2.48-1-3.5.28-1.15.28-2.35 0-3.5 0 0-1 0-3 1.5-2.64-.5-5.36-.5-8 0C6 2 5 2 5 2c-.3 1.15-.3 2.35 0 3.5A5.403 5.403 0 0 0 4 9c0 3.5 3 5.5 6 5.5-.39.49-.68 1.05-.85 1.65-.17.6-.22 1.23-.15 1.85v4"></path><path d="M9 18c-4.51 2-5-2-7-2"></path></svg>
-        GitHub
-      </a>
-    </div>
-
-    <div class="social-links">
-      <a href="https://github.com/sponsors/mgks" target="_blank" rel="noopener" class="social-link" title="Buy me a Coffee – GitHub Sponsors">
-        <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-heart-handshake-icon lucide-heart-handshake"><path d="M19 14c1.49-1.46 3-3.21 3-5.5A5.5 5.5 0 0 0 16.5 3c-1.76 0-3 .5-4.5 2-1.5-1.5-2.74-2-4.5-2A5.5 5.5 0 0 0 2 8.5c0 2.3 1.5 4.05 3 5.5l7 7Z"/><path d="M12 5 9.04 7.96a2.17 2.17 0 0 0 0 3.08c.82.82 2.13.85 3 .07l2.07-1.9a2.82 2.82 0 0 1 3.79 0l2.96 2.66"/><path d="m18 15-2-2"/><path d="m15 18-2-2"/></svg>
-      </a>
-      <a href="https://twitter.com/share?url=https://docmd.mgks.dev" target="_blank" rel="noopener" class="social-link">
-        <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 4s-.7 2.1-2 3.4c1.6 10-9.4 17.3-18 11.6 2.2.1 4.4-.6 6-2C3 15.5.5 9.6 3 5c2.2 2.6 5.6 4.1 9 4.5-.9-4.2 4-6.6 7-3.8 1.1 0 3-1.2 3-1.2z"></path></svg>
-      </a>
-    </div>
-  </div>
-  
-  <div class="preview-side">
-    <div class="preview-stack">
-      <div class="preview-image top">
-        <img src="/assets/images/preview-light-1.webp" alt="docmd documentation preview" class="light-img" loading="lazy">
-        <img src="/assets/images/preview-dark-1.webp" alt="docmd documentation preview" class="dark-img" loading="lazy">
-      </div>
-      <div class="preview-image middle">
-        <img src="/assets/images/preview-light-2.webp" alt="docmd documentation preview" class="light-img" loading="lazy">
-        <img src="/assets/images/preview-dark-2.webp" alt="docmd documentation preview" class="dark-img" loading="lazy">
-      </div>
-      <div class="preview-image bottom">
-        <img src="/assets/images/preview-light-3.webp" alt="docmd documentation preview" class="light-img" loading="lazy">
-        <img src="/assets/images/preview-dark-3.webp" alt="docmd documentation preview" class="dark-img" loading="lazy">
-      </div>
-    </div>
-  </div>
-</div>

package/docs/overview.md

@@ -1,63 +0,0 @@
----
-title: "Minimalist Markdown Docs Generator"
-description: "Generate beautiful, lightweight static documentation sites directly from your Markdown files with docmd. Zero clutter, just content."
----
-
-```
-   _                 _ 
- _| |___ ___ _____ _| |
-| . | . |  _|     | . |
-|___|___|___|_|_|_|___|
-
-```
-
-**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 `docmd.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.
-*   🔍 **Smart Search:** Built-in, offline-capable full-text search with fuzzy matching and highlighting. No API keys required.
-*   🎨 **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 `docmd.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.

package/docs/plugins/analytics.md

@@ -1,75 +0,0 @@
----
-title: "Analytics Integration"
-description: "Integrate web analytics services like Google Analytics into your docmd site to track visitor traffic."
----
-
-# Analytics Integration Plugin
-
-`docmd` allows you to easily integrate popular web analytics services into your documentation site using the built-in analytics plugin. This helps you understand your audience, track page views, and gather insights into how your documentation is being used.
-
-## Enabling Analytics Plugin
-
-You enable analytics by adding the analytics plugin and its configuration to the `plugins` object in your config file.
-
-**Example:**
-
-```javascript
-module.exports = {
-  // ...
-  plugins: {
-    // Analytics plugin configuration
-    analytics: {
-      // For Google Analytics 4 (GA4)
-      googleV4: {
-        measurementId: 'G-XXXXXXXXXX' // Your GA4 Measurement ID
-      },
-      
-      // For Google Universal Analytics (Legacy)
-      // googleUA: {
-      //   trackingId: 'UA-XXXXXXXXX-Y' // Your Universal Analytics Tracking ID
-      // }
-    },
-    
-    // ... other plugins
-  },
-  // ...
-};
-```
-
-Choose the analytics service and version you want to use by configuring the appropriate section.
-
-## Available Analytics Options
-
-### Google Analytics 4 (GA4)
-
-* **Configuration Key:** `googleV4`
-* **Description:** Integrates the latest version of Google Analytics, GA4. This is the recommended version for new Google Analytics setups.
-* **Options:**
-  * `measurementId` (String, Required): Your Google Analytics 4 Measurement ID, which typically looks like `G-XXXXXXXXXX`.
-* **Action:** Injects the standard Google Analytics 4 `gtag.js` tracking snippet into your pages.
-
-### Google Universal Analytics (Legacy)
-
-* **Configuration Key:** `googleUA`
-* **Description:** Integrates the older version of Google Analytics, known as Universal Analytics (UA). Note that Google has sunset Universal Analytics as of July 2023.
-* **Options:**
-  * `trackingId` (String, Required): Your Google Universal Analytics Tracking ID, which typically looks like `UA-XXXXXXXXX-Y`.
-* **Action:** Injects the standard Google Universal Analytics `analytics.js` tracking snippet into your pages.
-
-## Important Considerations
-
-* **Choose One Google Analytics Version:** If using Google Analytics, configure *either* `googleUA` *or* `googleV4`, but not both for the same property, to avoid incorrect data collection.
-* **Privacy and Consent:**
-  * Be mindful of user privacy when implementing analytics.
-  * Clearly disclose your use of analytics (and any cookies set by them) in your site's privacy policy or a cookie consent banner if required by regulations in your target regions (e.g., GDPR, CCPA).
-  * Consider features like IP anonymization if your analytics provider offers them and it's appropriate for your privacy stance.
-* **Testing:** After enabling the analytics plugin and deploying your site, verify that data is being collected correctly in your analytics provider's dashboard. Use browser developer tools (Network tab) to check if the tracking script is loading.
-
-## Future Analytics Support
-
-`docmd` may add support for other privacy-focused or popular analytics providers in the future, such as:
-* Plausible Analytics
-* Fathom Analytics
-* Simple Analytics
-
-Check the latest `docmd` documentation or GitHub repository for updates on supported analytics integrations.

package/docs/plugins/index.md

@@ -1,70 +0,0 @@
----
-title: "Using Plugins with docmd"
-description: "Extend docmd's functionality with built-in plugins."
----
-
-# Extending docmd with Plugins
-
-`docmd` supports a plugin system to add extra features and integrations to your documentation site without bloating the core tool. Plugins can modify the build process, inject content into pages, or add site-wide functionalities.
-
-## Enabling Plugins
-
-You enable and configure plugins in your config file within the `plugins` object. Each plugin is configured using its key with a corresponding configuration object.
-
-```javascript
-module.exports = {
-  // ... other config ...
-  plugins: {
-    // SEO Plugin
-    seo: {
-      defaultDescription: 'Your site-wide meta description',
-      openGraph: {
-        defaultImage: '/assets/images/og-preview.png',
-      },
-    },
-    // Analytics Plugin
-    analytics: {
-      googleV4: {
-        measurementId: 'G-XXXXXXXXXX'
-      }
-    },
-    // Sitemap Plugin
-    sitemap: {
-      defaultChangefreq: 'weekly',
-      defaultPriority: 0.8
-    }
-  },
-  // ...
-};
-```
-
-## Core Plugins
-
-`docmd` ships with several core plugins that you can easily enable:
-
-* **[SEO & Meta Tags](/plugins/seo/):** Automatically generates common SEO-related meta tags (description, Open Graph, Twitter Cards).
-* **[Analytics Integration](/plugins/analytics/):** Easily add tracking snippets for popular web analytics services like Google Analytics.
-* **[Sitemap](/plugins/sitemap/):** Generates a sitemap.xml file for search engines to better discover and index your content.
-
-Click on the links above or see the sidebar for detailed configuration of each core plugin.
-
-## How Plugins Work
-
-Plugins in `docmd` hook into various parts of the build process:
-
-* They can add meta tags and scripts to the page head
-* They can inject content or scripts at the beginning or end of the page body
-* They can generate additional files in the output directory
-* They can modify the HTML output of pages
-
-All plugins are designed to be configurable through your config file, giving you control over their behavior.
-
-## Future Plugin Development
-
-The plugin system is designed with future extensibility in mind. As `docmd` evolves, we plan to:
-
-* Add more built-in plugins for common documentation needs
-* Create an API for developers to build custom plugins
-* Enable community contribution of third-party plugins
-
-For now, focus on utilizing the available core plugins to enhance your site's functionality.