Refactor package.json to rename the project to @riligar/knowledge, add files and engines fields, and include semantic-release dependencies. Update README.md to enhance installation instructions, add features section, and clarify the release process with automated versioning and changelog generation.

Author: ciro-maciel

.github/workflows/release.yml

@@ -0,0 +1,44 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - prod
+      - main
+
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v1
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install --frozen-lockfile
+
+      - name: Build binary
+        run: bun run build-bin
+
+      - name: Prepare npm package
+        run: bun run prepare-npm
+
+      - name: Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: bunx semantic-release 

.npmignore

@@ -0,0 +1,35 @@
+# Development files
+.git/
+.github/
+node_modules/
+.DS_Store
+*.log
+
+# Documentation and examples
+docs/
+README.md
+CNAME
+install.sh
+
+# Development configuration
+.gitignore
+bun.lock
+tsconfig.json
+knowledge.config.ts
+knowledge.config.example.json
+
+# Build artifacts that shouldn't be published
+dist/
+
+# Include the npm-specific README
+!README.npm.md
+
+# Only include essential files for the npm package
+# The following will be included:
+# - package.json
+# - bin/
+# - src/
+# - index.ts
+# - LICENSE
+# - themes/
+# - README.npm.md 

.releaserc.json

@@ -0,0 +1,39 @@
+{
+    "branches": [
+        "main",
+        "prod"
+    ],
+    "plugins": [
+        "@semantic-release/commit-analyzer",
+        "@semantic-release/release-notes-generator",
+        "@semantic-release/changelog",
+        [
+            "@semantic-release/npm",
+            {
+                "npmPublish": true,
+                "tarballDir": "dist"
+            }
+        ],
+        [
+            "@semantic-release/github",
+            {
+                "assets": [
+                    {
+                        "path": "dist/*.tgz",
+                        "label": "Package tarball"
+                    }
+                ]
+            }
+        ],
+        [
+            "@semantic-release/git",
+            {
+                "assets": [
+                    "CHANGELOG.md",
+                    "package.json"
+                ],
+                "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+            }
+        ]
+    ]
+}

CONTRIBUTING.md

@@ -0,0 +1,83 @@
+# Contributing to Knowledge
+
+Thank you for your interest in contributing to Knowledge! This document provides guidelines for contributing to the project.
+
+## Commit Convention
+
+This project uses [Conventional Commits](https://www.conventionalcommits.org/) to automate versioning and changelog generation. Please follow this format for your commit messages:
+
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Types
+
+- **feat**: A new feature (triggers a minor version bump)
+- **fix**: A bug fix (triggers a patch version bump)
+- **docs**: Documentation only changes
+- **style**: Changes that do not affect the meaning of the code
+- **refactor**: A code change that neither fixes a bug nor adds a feature
+- **perf**: A code change that improves performance
+- **test**: Adding missing tests or correcting existing tests
+- **chore**: Changes to the build process or auxiliary tools
+
+### Breaking Changes
+
+For breaking changes, add `BREAKING CHANGE:` in the footer or add `!` after the type:
+
+```
+feat!: remove deprecated API endpoint
+
+BREAKING CHANGE: The /old-api endpoint has been removed. Use /new-api instead.
+```
+
+### Examples
+
+```bash
+feat: add search functionality to documentation
+fix: resolve markdown parsing issue with code blocks
+docs: update installation instructions
+chore: update dependencies
+```
+
+## Development Workflow
+
+1. Fork the repository
+2. Create a feature branch: `git checkout -b feat/your-feature`
+3. Make your changes following the commit convention
+4. Push to your fork: `git push origin feat/your-feature`
+5. Create a Pull Request
+
+## Release Process
+
+Releases are automated using semantic-release:
+
+- **Patch releases** (1.0.1): Bug fixes
+- **Minor releases** (1.1.0): New features
+- **Major releases** (2.0.0): Breaking changes
+
+The release process is triggered automatically when commits are pushed to the `prod` branch.
+
+## Local Development
+
+```bash
+# Install dependencies
+bun install
+
+# Start development server
+bun run dev
+
+# Build the project
+bun run build
+
+# Test the CLI
+bun run knowledge --help
+```
+
+## Questions?
+
+Feel free to open an issue if you have any questions about contributing! 

README.md

@@ -8,61 +8,89 @@
 
 **Knowledge** is a modern static documentation generator that transforms Markdown files into professional documentation sites. It's the perfect tool for anyone who wants to create beautiful and functional documentation without complications.
 
-## 📦 Quick Installation
+## 🚀 Features
 
-### Global Installation (Recommended)
+- **Markdown-First**: Write documentation in familiar Markdown syntax
+- **Static Site Generation**: Fast, secure, and SEO-friendly output
+- **Modern Themes**: Beautiful, responsive themes out of the box
+- **Search Integration**: Built-in search functionality
+- **CLI Tool**: Simple command-line interface for easy management
+- **Live Development**: Hot-reload during development
 
-```bash
-# Using Bun (fastest)
-bun install -g knowledge
+## 📦 Installation
 
-# Using npm
-npm install -g knowledge
+### NPM (Recommended)
 
-# Using the install script
-curl -fsSL https://raw.githubusercontent.com/riligar/knowledge/main/install.sh | bash
+```bash
+npm install -g @riligar/knowledge
 ```
 
-### Quick Start
+### Direct Download
 
 ```bash
-# Create a new project
-mkdir my-docs && cd my-docs
+curl -fsSL https://raw.githubusercontent.com/riligar/knowledge/main/install.sh | sh
+```
 
-# Initialize Knowledge project
-knowledge init
+## 🎯 Quick Start
 
-# Install dependencies
-bun install  # or npm install
+1. **Initialize a new project**:
+   ```bash
+   knowledge init my-docs
+   cd my-docs
+   ```
 
-# Start development server
-knowledge dev
+2. **Start development server**:
+   ```bash
+   knowledge dev
+   ```
 
-# Build for production
-knowledge build
+3. **Build for production**:
+   ```bash
+   knowledge build
+   ```
 
-# Serve built site
-knowledge serve
+## 📖 Documentation
+
+Visit our [official documentation](https://myknowledge.click) for detailed guides and examples.
+
+## 🤝 Contributing
+
+We welcome contributions! Please see our [Contributing Guide](CONTRIBUTING.md) for details.
+
+### Commit Convention
+
+This project uses [Conventional Commits](https://www.conventionalcommits.org/) for automated versioning and changelog generation. Please format your commits as:
+
+```
+feat: add new feature
+fix: resolve bug
+docs: update documentation
 ```
 
-## ⚡ Why use Knowledge?
+## 🔄 Release Process
+
+Releases are fully automated using semantic-release:
+
+- **Automatic versioning** based on commit messages
+- **Changelog generation** from conventional commits  
+- **NPM publishing** on every release
+- **GitHub releases** with detailed notes
 
-### ✅ **Extreme Simplicity**
-- Write in plain Markdown
-- Configure once, use always
-- Generate professional sites automatically
+Simply push to the `prod` branch and let the automation handle the rest!
 
-### ✅ **Professional Features**
-- 🔍 **Instant search** across all content
-- 📱 **Responsive design** (mobile + desktop)
-- 🌙 **Automatic dark mode**
-- 🎨 **Syntax highlighting** for code
-- 🧭 **Automatic navigation** based on folders
+## 📄 License
+
+This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.
+
+## 🌟 Support
+
+- 📧 Email: maciel.ciro@icloud.com
+- 🐛 Issues: [GitHub Issues](https://github.com/riligar/knowledge/issues)
+- 💬 Discussions: [GitHub Discussions](https://github.com/riligar/knowledge/discussions)
+
+---
 
-### ✅ **Productivity**
-- 🚀 **Fast build** with Bun.js (seconds)
-- 📦 **Simple deploy** to any hosting
-- 🔧 **Zero configuration** required
+Made with ❤️ by [Riligar](https://riligar.click)
 
 ## 🚀 How to Use (3 Steps)