Added a bunch of Docs and Issue templates and CODEOWNERS

Author: youngcoder45

.github/CODEOWNERS

@@ -0,0 +1,10 @@
+# Default owners for the whole repository
+* @TheCodeVerseHub/core
+
+# Area ownership (keep these lightweight and practical)
+/docs/ @TheCodeVerseHub/core
+/scripts/ @TheCodeVerseHub/core
+/configs/ @TheCodeVerseHub/core
+/iso/ @TheCodeVerseHub/core
+/pkgbuild/ @TheCodeVerseHub/core
+/src/ @TheCodeVerseHub/core

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,62 @@
+name: Bug report
+description: Report something that is broken or unexpected
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug.
+
+  - type: input
+    id: version
+    attributes:
+      label: ISO/version
+      description: If known (e.g. iso_version from the boot screen, or the build date)
+      placeholder: "2026.03.29 (example)"
+    validations:
+      required: false
+
+  - type: dropdown
+    id: environment
+    attributes:
+      label: Environment
+      options:
+        - VM
+        - Real hardware
+    validations:
+      required: true
+
+  - type: textarea
+    id: what_happened
+    attributes:
+      label: What happened?
+      description: A clear and concise description of the problem
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      placeholder: |
+        1. Boot ISO
+        2. Run cvh-install
+        3. ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+    validations:
+      required: false
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / output
+      description: Paste relevant output (journalctl, installer output, etc.)
+      render: shell
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,31 @@
+name: Feature request
+description: Suggest an idea or improvement
+labels: [enhancement]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping improve CVH Linux.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem / motivation
+      description: What problem does this solve?
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: What would you like to see implemented?
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+## Summary
+
+<!-- What does this PR do and why? -->
+
+## Changes
+
+-
+
+## Testing
+
+<!-- How did you test this? -->
+- [ ] Built ISO
+- [ ] Booted in VM
+- [ ] Ran installer (`cvh-install`)
+
+## Checklist
+
+- [ ] Scope is focused (no unrelated changes)
+- [ ] Docs updated (if needed)
+- [ ] Scripts/configs changed were tested

CONTRIBUTING.md

@@ -1,100 +1,45 @@
-# Contributing to CodeVerse Hub Projects
+# Contributing
 
-Thank you for your interest in contributing to CodeVerse Hub projects.  
-All repositories under the CodeVerse Hub organization are community-driven and open to contributions.
+Thanks for contributing to CodeVerse Linux (CVH Linux).
 
-This document explains how to get started and what is expected from contributors.
+## Setup (build environment)
 
----
+This project builds an ArchISO and is easiest to work on from an **Arch-based host**.
 
-## Who Can Contribute
+Required tools for ISO builds:
 
-- Beginners, intermediate, and advanced developers
-- Designers, writers, and documentation contributors
-- Anyone willing to collaborate respectfully
+- `archiso` (provides `mkarchiso`)
+- `squashfs-tools` (provides `mksquashfs`)
+- `libisoburn` (provides `xorriso`)
+- `grub` (provides `grub-mkrescue`)
 
-You do not need prior open-source experience.
+Install (Arch):
 
----
+- `sudo pacman -S archiso squashfs-tools libisoburn grub`
 
-## How to Start
+If you touch `src/` (Rust tools), install Rust via rustup.
 
-1. Choose a repository under the organization  
-   https://github.com/TheCodeVerseHub
-2. Read the repository README carefully
-3. Check existing issues
-4. Pick an issue or open a new one if needed
-5. Fork the repository
-6. Create a new branch for your work
-7. Make your changes
-8. Submit a pull request
+## Common tasks
 
----
+- Build packages: `./scripts/build-packages.sh`
+- Build ISO: `./scripts/build-iso.sh`
 
-## Development Workflow
+More detail: [docs/BUILD.md](docs/BUILD.md).
 
-- Fork the repository
-- Create a branch using a clear name  
-  Example: `fix-starboard-bug` or `add-hyprland-config`
-- Keep commits small and meaningful
-- Write clear commit messages
-- Test your changes before submitting
+## Testing changes
 
----
+Recommended: test in a VM first.
 
-## Pull Request Guidelines
+- Boot the ISO in QEMU/virt-manager
+- Smoke test:
+  - Boot to live environment
+  - Run `cvh-install` and complete an install on a disposable virtual disk
 
-- Clearly explain what your PR does
-- Link the related issue if applicable
-- Do not mix unrelated changes in one PR
-- Follow the existing code style
-- Be open to feedback and review comments
+VM walkthrough: [docs/TESTING.md](docs/TESTING.md).
 
-Low-quality or incomplete PRs may be closed.
+## Submitting a PR
 
----
-
-## Code Quality Expectations
-
-- Code should be readable and maintainable
-- Avoid unnecessary complexity
-- Follow project-specific style and structure
-- Document non-obvious logic
-- Do not commit generated files unless required
-
----
-
-## Issues and Discussions
-
-- Use issues for bugs, features, and tasks
-- Use discussions for questions and ideas
-- Search before opening a new issue
-
----
-
-## Behavior and Conduct
-
-- Be respectful and professional
-- No harassment, spam, or toxic behavior
-- Follow the Code of Conduct
-
-Violations may result in removal from the project.
-
----
-
-## Contributor Recognition
-
-Meaningful contributions will be:
-- Reviewed and merged when appropriate
-- Credited in the project
-- Eligible for the @Contributors role on the CodeVerse Hub Discord server
-
----
-
-## Questions
-
-If you are unsure about anything:
-- Ask in GitHub Discussions
-- Ask in the CodeVerse Hub Discord server
-
-We value collaboration and learning.
+1. Fork the repo and create a feature branch.
+2. Keep PRs focused (one logical change).
+3. Describe what changed and how it was tested.
+4. Submit a pull request using the PR template.