feat: Add contributing, governance, and privacy documents

- Created CONTRIBUTING.md with guidelines for contributing to the project.
- Added GOVERNANCE.md outlining project structure and decision-making processes.
- Introduced LICENSE.md with the European Union Public License v. 1.2.
- Implemented PRIVACY.md detailing data collection and protection measures.
- Established SECURITY.md for reporting vulnerabilities and security measures.
- Added SUPPORT.md for user assistance and support policy.
- Created code style and commit style guidelines in docs/code-style.md and docs/commit-style.md.
- Added pull request template in docs/pull_request_template.md.
- Updated package.json and pnpm-lock.yaml to reflect changes in package naming conventions.

Author: devbyray

.github/CODEOWNERS

@@ -0,0 +1,5 @@
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in the repo.
+*       @devbyray

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/copilot-instructions.md

@@ -0,0 +1,9 @@
+Always use simple languages, be friendly, informal and avoid jargon. This will make your code easier to understand for everyone.
+
+Always use code according to the /docs/code-style.md guide. This will make your code easier to understand for everyone.
+
+The commit messages should be according to the /docs/commit-style.md guide. This will make your code easier to understand for everyone.
+
+Use @terminal when answering questions about Git.
+
+

.github/workflows/publish-packages.yml

@@ -34,7 +34,7 @@ jobs:
         with:
           node-version: '20'
           registry-url: 'https://npm.pkg.github.com'
-          scope: '@devbyrayray'
+          scope: '@devbyray'
           cache: 'pnpm'
 
       - name: Setup PNPM

.vscode/settings.json

@@ -0,0 +1,12 @@
+{
+    "github.copilot.chat.codeGeneration.instructions":[
+        {
+            "file": "docs/code-style.md",
+        }
+    ],
+    "github.copilot.chat.commitMessageGeneration.instructions": [
+        {
+            "file": "docs/commit-style.md"
+        }
+    ]
+}

ACCESSIBILITY.md

@@ -0,0 +1,49 @@
+# Accessibility Statement
+
+## Our Commitment
+
+We are committed to ensuring our project is accessible to everyone. We aim to comply with Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards.
+
+## Compliance Status
+
+Our project aims to be compliant with:
+
+- WCAG 2.1 Level AA
+- Section 508 requirements
+- ADA requirements
+
+## Features
+
+Accessibility features in our project include:
+
+- Keyboard navigation support
+- Screen reader compatibility
+- Sufficient color contrast
+- Text resizing without loss of functionality
+- Alternative text for images
+
+## Known Issues
+
+We are currently working to address these known accessibility issues:
+
+- [List any known issues]
+
+## Testing
+
+We regularly test our application for accessibility using:
+
+- Automated testing tools
+- Manual testing
+- Screen reader testing
+- Keyboard navigation testing
+
+## Feedback
+
+We welcome your feedback on the accessibility of this project. Please report accessibility barriers using one of these methods:
+
+- Submit an issue on our GitHub repository
+- Email us at [[email protected]](mailto:[email protected])
+
+## This Statement
+
+This statement was last updated on [DATE].

CODE_OF_CONDUCT.md

@@ -0,0 +1,50 @@
+# 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, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+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 include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+## Reporting Violations
+
+If you experience or witness unacceptable behavior, please report it by contacting
+the project team at [INSERT EMAIL ADDRESS]. All reports will be handled with
+discretion.
+
+## Enforcement
+
+Violations of the Code of Conduct may result in temporary or permanent exclusion
+from project participation, as determined by project maintainers.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# Contributing to This Project
+
+Thank you for your interest in contributing to our project! This document provides guidelines and instructions for contributing.
+
+## Code of Conduct
+
+Please read our [Code of Conduct](./CODE_OF_CONDUCT.md) before contributing.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+- Check if the bug has already been reported in the Issues section
+- Use the bug report template when creating a new issue
+- Provide detailed steps to reproduce the bug
+- Include screenshots if applicable
+
+### Suggesting Features
+
+- Check if the feature has already been suggested
+- Use the feature request template
+- Explain why the feature would be useful
+
+### Pull Requests
+
+1. Fork the repository
+2. Create a new branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Commit with clear messages (`git commit -m 'Add some amazing feature'`)
+5. Push to your branch (`git push origin feature/amazing-feature`)
+6. Open a Pull Request
+
+## Development Process
+
+- All development should happen in feature branches
+- Pull requests require at least one review before merging
+- All tests must pass before a PR can be merged
+
+## Style Guidelines
+
+- Follow the existing code style
+- Write clear comments and documentation
+- Keep commit messages concise and descriptive
+
+Thank you for contributing!

GOVERNANCE.md

@@ -0,0 +1,68 @@
+# Project Governance
+
+## Project Structure
+
+This project is maintained by a team of volunteers and follows a community-driven governance model.
+
+## Roles and Responsibilities
+
+### Project Maintainers
+
+- Review and merge pull requests
+- Release new versions
+- Establish project direction
+- Manage community interactions
+
+### Contributors
+
+- Submit pull requests
+- Report bugs and suggest features
+- Participate in discussions
+- Help with documentation and testing
+
+### Users
+
+- Provide feedback
+- Report bugs
+- Suggest features
+- Spread the word about the project
+
+## Decision Making Process
+
+1. **Proposals**: Anyone can propose changes via issues or discussions
+2. **Feedback**: Community feedback is gathered
+3. **Consensus**: We aim for consensus among maintainers
+4. **Implementation**: Once approved, changes are implemented
+
+## Becoming a Maintainer
+
+Contributors who show consistent, high-quality participation may be invited to become maintainers. The process includes:
+
+1. Nomination by an existing maintainer
+2. Review of contribution history
+3. Consensus among existing maintainers
+4. Formal invitation
+
+## Communication Channels
+
+- GitHub Issues and Discussions
+- Community Chat (e.g., Discord, Slack)
+- Regular community calls
+- Mailing list
+
+## Conflict Resolution
+
+When conflicts arise, we follow this process:
+
+1. Open discussion on the relevant platform
+2. Moderated debate with all stakeholders
+3. Attempt to reach consensus
+4. If consensus cannot be reached, maintainers make the final decision
+
+## Changes to Governance
+
+This governance document may evolve over time. Significant changes will be:
+
+1. Proposed via pull request
+2. Open for community feedback
+3. Implemented only after maintainer consensus