Add comprehensive professional documentation to README.md with architecture diagrams, installation guides, and extensive troubleshooting

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,36 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'Bug: [short description]'
+labels: bug
+---
+
+## Description
+
+<!-- A clear and concise description of what the bug is. -->
+
+## Steps to Reproduce
+1. 
+2. 
+3. 
+
+## Expected Behavior
+
+<!-- A clear and concise description of what you expected to happen. -->
+
+## Actual Behavior
+
+<!-- A clear and concise description of what actually happened. -->
+
+## Environment Details
+- OS: 
+- Browser: 
+- Version: 
+
+## Screenshots
+
+<!-- If applicable, add screenshots to help explain your problem. -->
+
+## Additional Context
+
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature Request
+description: Suggest a new idea for this project
+title: "
+labels: feature request
+---
+
+## Feature Description
+
+A clear and concise description of what the feature is and why it is needed.
+
+## Problem Statement
+
+What is the problem that this feature would solve? Why is it important?
+
+## Proposed Solution
+
+A clear and concise description of what you want to happen.
+
+## Alternatives Considered
+
+What are other solutions you considered? Why did you choose this solution?
+
+## Additional Context
+
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+## Description
+
+<!-- Please include a summary of the change and which issue is fixed. Also include relevant motivation and context. -->
+
+
+## Type of Change
+
+- [ ] Bugfix
+- [ ] New Feature
+- [ ] Documentation Update
+- [ ] Other (Please specify)
+
+
+## Testing Checklist
+
+- [ ] I have tested the changes locally
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] I have updated the documentation accordingly
+
+
+## Related Issues
+
+<!-- Please reference any related issues here. -->
+
+
+## Screenshots
+
+<!-- If applicable, add screenshots to help explain your changes. -->

CHANGELOG.md

@@ -0,0 +1,40 @@
+# Changelog
+
+## [1.0.0] - 2025-10-18
+
+### Added
+- GUI version
+- CLI version with Rich library
+- Batch processing
+- Language selection
+- Auto-detect
+- Dry run mode
+- Real-time progress tracking
+- Cross-platform support
+
+### Technical Details
+- Python 3.7+ support
+- MKVToolNix integration
+- Threading support
+
+### Dependencies
+- Rich library
+- Tkinter
+
+### Documentation Updates
+- Improved documentation for better understanding
+
+### Supported Platforms
+- Windows
+- macOS
+- Linux
+
+### Planned Future Enhancements
+- Multi-threading support
+- Presets for common configurations
+- Standalone executables
+- Support for additional formats
+- Web interface for easier access
+- Detailed logging features
+- Track selection capabilities
+- Codec conversion functionality

CODE_OF_CONDUCT.md

@@ -0,0 +1,32 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to instances of unacceptable behavior.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Enforcement Guidelines
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [your-email@example.com]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
+
+## Attribution
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing Guidelines
+
+Thank you for considering contributing to our project! We welcome contributions from everyone. Here are some guidelines to help you get started:
+
+## Reporting Bugs
+If you encounter a bug, please open an issue in the repository and provide as much detail as possible, including steps to reproduce the bug.
+
+## Suggesting Features
+We love new ideas! If you have a feature suggestion, please open an issue and describe your idea.
+
+## Code Style Guidelines
+We follow [PEP 8](https://www.python.org/dev/peps/pep-0008/) for Python code. Please ensure your code adheres to these guidelines.
+
+## Pull Request Process
+1. Fork the repository.
+2. Create a new branch for your changes.
+3. Make your changes and commit them.
+4. Open a pull request and describe your changes.
+
+## Development Setup Instructions
+1. Clone the repository.
+2. Install dependencies using `pip install -r requirements.txt`.
+3. Run tests using `pytest`.
+
+## Testing Guidelines
+Please ensure that you add tests for any new features or bug fixes.
+
+## Commit Message Conventions
+Use clear and descriptive commit messages. Follow the format: `Type: Subject` where Type can be feat, fix, docs, style, refactor, perf, test.
+
+## Code of Conduct
+Please adhere to our [Code of Conduct](CODE_OF_CONDUCT.md) in all interactions.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 mlbkumar9
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+- The above copyright notice and this permission notice shall be included in all
+  copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.