Sync main with user ranklist branch

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,10 @@
+---
+name: Documentation
+about: Documentation related
+title: "[DOC]"
+labels: documentation
+assignees: karastoyanov
+
+---
+
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,6 +1,6 @@
 ---
 name: Feature request
-about: Suggest an idea for this project
+about: Suggest an idea or enhancement
 title: "[ENHANCEMENT]"
 labels: enhancement
 assignees: karastoyanov

.github/ISSUE_TEMPLATE/new-quest-submit.md

@@ -0,0 +1,23 @@
+---
+name: New Quest Submit
+about: Got an idea for a quest?
+title: "[QUEST]"
+labels: quest
+assignees: karastoyanov
+
+---
+
+**Quest Title:**
+_Unique title for your quest_
+
+**Quest Difficulty:**
+_Choose between Novice Quests, Adventurous Challenges or Epic Campaings_
+
+**Quest Language:**
+_Python, Java, C# or JavaScript_
+
+**Quest Description:**
+_Briend description of the quest. What problem should be solved?_
+
+**Other:**
+_Any other related details_

.gitignore

@@ -1,7 +1,12 @@
 # Ignore VSCode settings
 .vscode/
+
+# Ignore Obsidian configs
+.obsidian/
+
 # Ignore venv dir
 /venv/
+/skill_forge/
 
 # Ignore docs folder
 /docs/
@@ -35,4 +40,5 @@ manage.py
 basic_email.py
 
 # Ignore DOC.md
-DOC.md
+DOC.md
+/old-build/

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# 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.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement 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 any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+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.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+karastoqnov.alexandar@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,111 @@
+
+# ➡️ Skill Forge Contributing Guidelines
+
+## 📝 Prerequisites:
+* Docker & Docker Compose
+* Piston API
+* It is recommended to use VSCode with Remote SSH
+
+## 1️⃣ Fork the repository
+
+## 2️⃣ Checkout to `dev-stack` branch.
+* Inside the branch you will find the `docker-compose.yaml` file. 
+* Change the `.env_variables` to `.env`
+* Run `docker compose up -d` in order to build and deploy all the necessary services: PostgreSQL, MongoDB, PistonAPI and the Skill Forge app 
+
+⌛ The build process will take some tame so grab a cup of coffee ☕
+After the services are built and deployed run `docker ps` to check all the containers.
+
+⚠️ In order to execute code snippets from Skill Forge you will have to install the required runtimes for each programming language supported: 
+```
+Java=15.0.2
+Python=3.12.0
+Csharp=6.12.0
+JavaScript=20.11.1
+```
+
+You might need Postman to send the POST requests in order to install the runtime environments. Refer to the [Piston API](https://github.com/engineer-man/piston) docs 
+
+❗You can re-build your local dev version each time when you did some changes in order to verify in the application can be build and deployed succsesfulyl. 
+
+## 3️⃣ Create your own branch with the proper name. Branch naming convention:
+
+**New Feature Development:**
+Includes new user stories or whole new feature introduction, e.g.:
+```
+• feature/user-google-authentication
+• feature/homepage-uui-cards
+• feature/add-search-functionality
+• feature/add-profile-page
+```
+**Bug Fixes:**
+Priority 1 and 2 bug fixes, not critical, e.g.:
+```
+• bugfix/logs-database-issue
+• bugfix/resolve-signup-error
+• bugfix/api-response-fix
+• bugfix/database-connection-error
+```
+**Hot-fixes:**
+Priority 0 bug fixes, production critical, e.g.:
+```
+• hotfix/critical-security-patch
+• hotfix/fix-broken-build
+• hotfix/urgent-ui-fix
+• hotfix/authentication-issue
+```
+
+**Miscellaneous:**
+```
+• chore/update-dependencies
+• chore/code-cleanup
+• test/add-unit-tests
+• refactor/remove-legacy-code
+• refactor/new-database-integration
+• refactor/ui-reword
+```
+
+### 4️⃣ After you are done with you changes open an Pull-Request and submit you commits. 
+
+To ensure a smooth and efficient code review process, please follow these guidelines when creating a pull request (PR):
+
+**Descriptive Title**
+* Provide a concise and clear title that summarizes the purpose of the PR. Avoid generic titles like “Fixes” or “Changes”—be specific.
+* ✅  Add user authentication with JWT
+*  ❌  Fixed stuff
+
+**Detailed Description**
+* **What was changed:** Provide a summary of the changes made in the PR.
+* **Why it was changed:** Explain the problem you’re solving or the new feature you’re adding.
+* **How it was changed:** Outline the approach taken, and any relevant design decisions.
+* **Dependencies:** List any other PRs, issue, libraries, or configurations this PR depends on.
+* **Additional context or screenshots:** If relevant, include screenshots for UI changes or logs of issues solved.
+
+**Break Down Large PRs**
+* Keep your pull requests small and focused. If the change is large, consider splitting it into smaller, incremental PRs. This makes reviews quicker and less error-prone.
+
+**Link to Relevant Issues**
+* If the PR fixes a bug or implements a feature request, reference the issue number using the appropriate keywords so it can be closed automatically after merging.
+
+**Follow Coding Standards**
+* Ensure your code follows the project’s coding conventions, such as:
+* Code style (e.g., naming conventions, formatting)
+* Consistent use of comments and documentation
+* Tests for new or updated functionality
+
+**Document Changes**
+* Update any relevant documentation, such as API endpoints, configuration files, or README.md, as part of the PR.
+* If this change requires environment-specific setup (e.g., new environment variables), clearly explain this in the description.
+
+**Keep PRs Up-to-date**
+* If your PR remains open for an extended period, rebase it with the latest changes from the main or development branch. Resolve any merge conflicts early to prevent delays in the review process.
+
+**Request Review**
+* Assign appropriate reviewers ([@karastoyanov](https://github.com/karastoyanov)).
+* Tag them in the description or use the platform’s review request feature.
+* If a specific area of code needs attention, mention it to the reviewer(s).
+
+**Be Open to Feedback**
+* Be responsive to reviewer comments.
+* If feedback requires changes, update the PR promptly and re-request reviews.
+* For larger discussions or significant design changes, consider discussing them in a separate issue or meeting.