1.3

Author: bugfish\bugfishtm

.gitattributes

@@ -0,0 +1,26 @@
+# This is just an internal File to setup the repository
+
+# Set default behaviour, in case users don't have core.autocrlf set.
+* text=auto
+
+# Explicitly declare text files we want to always be normalized and converted 
+# to native line endings on checkout.
+*.php text eol=lf
+*.sql text eol=lf
+*.htm text eol=lf
+*.html text eol=lf
+*.js text eol=lf
+*.css text eol=lf
+*.lang text eol=lf
+*.txt text eol=lf
+*.md text eol=lf
+*.bat text eol=lf
+*.sh   text eol=lf
+*.bash text eol=lf
+
+# Denote all files that are truly binary and should not be modified.
+*.ico binary
+*.png binary
+*.jpg binary
+*.odt binary
+*.odf binary

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,17 @@
+# 🤝 Code of Conduct  
+
+We’re on a mission to create groundbreaking solutions, pushing the boundaries of technology. By being here, you’re an integral part of that journey. 
+
+**Positive Guidelines:**
+- Be kind, empathetic, and respectful in all interactions.
+- Engage thoughtfully, offering constructive, solution-oriented feedback.
+- Foster an environment of collaboration, support, and mutual respect.
+
+**Unacceptable Behavior:**
+- Harassment, hate speech, or offensive language.
+- Personal attacks, discrimination, or any form of bullying.
+- Sharing private or sensitive information without explicit consent.
+
+Let’s collaborate, inspire one another, and build something extraordinary together!
+
+🐟 Bugfish

.github/CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# 🌱 Contributing
+
+I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.
+
+## How to Contribute
+
+1. Fork the repository to create your own copy.
+2. Create a new branch for your work (e.g., `feature/my-feature`).
+3. Make your changes and ensure they work as expected.
+4. Run tests to confirm everything is functioning correctly.
+5. Commit your changes with a clear, concise message.
+6. Push your branch to your forked repository.
+7. Submit a pull request with a detailed description of your changes.
+8. Reference any related issues or discussions in your pull request.
+
+## Coding Style
+
+- Keep your code clean and well-organized.
+- Add comments to explain complex logic or functions.
+- Use meaningful and consistent variable and function names.
+- Break down code into smaller, reusable functions and components.
+- Follow proper indentation and formatting practices.
+- Avoid code duplication by reusing existing functions or modules.
+- Ensure your code is easily readable and maintainable by others.
+
+## Issues
+
+If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.
+
+🐟 Bugfish

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+custom: https://paypal.me/bugfish
+patreon: bugfish

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,30 @@
+---
+name: Bug Report
+about: Report a problem with the project.
+title: "[BUG] Short description of the issue"
+labels: bug
+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. Do '....'
+3. 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.
+
+## Environment:
+ - OS: [e.g. Windows, macOS, Linux]
+ - Version [e.g. Software Version, Browser Version]
+
+## Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,17 @@
+---
+name: Feature Request
+about: Suggest a new feature or improvement for this project.
+title: "[FEATURE] Short description of the feature"
+labels: enhancement
+assignees: ''
+
+---
+
+## 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/ISSUE_TEMPLATE/QUESTION.md

@@ -0,0 +1,20 @@
+---
+name: Question  
+about: Ask a question about the project.  
+title: "[QUESTION] Short description of your question"  
+labels: question  
+assignees: ''  
+---
+
+## Question  
+A clear and concise question about the project.  
+
+## Context  
+Provide any relevant details, such as what you're trying to achieve, any challenges you're facing, or related documentation/code references.  
+
+## What Have You Tried?  
+List any steps you've taken to find an answer, such as searching the documentation, checking previous issues, or testing solutions.  
+
+## Additional Information  
+If applicable, include screenshots, code snippets, or links that might help clarify your question.  
+

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+# contact_links:
+#   - name: Visit
+#     url: https://www.bugfish.eu
+#     about: Please ask and answer questions there.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+## Description
+[Provide a brief description of the changes in this pull request]
+
+## Related Issue
+[Reference any related issue(s) here using the syntax: Fixes #123 or Relates to #456]
+
+## Proposed Changes
+- [Change 1]
+- [Change 2]
+- [Change 3]
+
+## Additional Information
+[Any additional information or context that would be helpful for reviewers]
+
+## Checklist
+- [ ] I have tested these changes locally
+- [ ] I have updated the documentation accordingly
+- [ ] My code follows the project's coding standards
+
+## Screenshots (if applicable)
+[Add screenshots here to demonstrate visual changes]

.gitignore

@@ -0,0 +1,10 @@
+# This is just an internal File to ignore Files during git operations
+
+# Block a File
+# folder/file.php
+# Block a Folder
+# folder/
+
+# Ignore all htaccess & htpasswd Files
+# **/.htaccess*
+# **/.htpasswd*

CHANGELOG.md

@@ -0,0 +1,5 @@
+# 📑 Changelog
+
+Refer to the `_changelogs` folder for detailed insights into the changes made across different versions. The changelogs are available in **HTML format** within this folder, providing a structured record of updates, modifications, and improvements over time. Additionally, **GitHub Releases** follow the same structure and also include these changelogs for easy reference.
+
+🐟 Bugfish 

CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# 🌱 Contributing
+
+I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.
+
+## How to Contribute
+
+1. Fork the repository to create your own copy.
+2. Create a new branch for your work (e.g., `feature/my-feature`).
+3. Make your changes and ensure they work as expected.
+4. Run tests to confirm everything is functioning correctly.
+5. Commit your changes with a clear, concise message.
+6. Push your branch to your forked repository.
+7. Submit a pull request with a detailed description of your changes.
+8. Reference any related issues or discussions in your pull request.
+
+## Coding Style
+
+- Keep your code clean and well-organized.
+- Add comments to explain complex logic or functions.
+- Use meaningful and consistent variable and function names.
+- Break down code into smaller, reusable functions and components.
+- Follow proper indentation and formatting practices.
+- Avoid code duplication by reusing existing functions or modules.
+- Ensure your code is easily readable and maintainable by others.
+
+## Issues
+
+If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.
+
+🐟 Bugfish