PteroCA-Org · ksroga · Mar 2, 2026 · Feb 17, 2026 · Feb 17, 2026 · Feb 17, 2026
diff --git a/.github/ISSUE_TEMPLATE/custom.md b/.github/ISSUE_TEMPLATE/custom.md
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,19 @@
+## Description
+<!-- What does this PR do? Reference related issues: Closes #123 -->
+
+## Type of change
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Refactoring / code improvement
+- [ ] Documentation update
+- [ ] Translation update
+
+## Checklist
+- [ ] CI pipeline passes (PHPStan, migrations, translations check)
+- [ ] Branch targets `main`
+- [ ] Code follows PSR-12 (PHP) / project conventions
+- [ ] If adding/editing translations: all language files in `src/Core/Resources/translations/` were updated
+- [ ] If introducing behavior changes: CHANGELOG entry added
+
+## Testing
+<!-- How was this change tested? (manual steps, screenshots, etc.) -->
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,42 @@
 # Changelog
 
+## [0.6.4] - 2026-03-02
+
+### Added
+- Added price preview widget in the product pricing tab showing formatted prices for each billing period.
+- Added email notification sent to the user when an admin creates a server on their behalf.
+- Added filesystem permission precheck before plugin upload to verify write access and show clear error messages.
+- Added filesystem permission precheck before theme upload to verify write access and show clear error messages.
+- Added Marketplace integration in the admin panel - browse, search, and install plugins directly from marketplace.pteroca.com.
+- Added support for required user-provided server variables during the server purchase flow.
+- Added product egg variable validation rules support - rules defined in egg configuration are now enforced on user input.
+- Added server health status badge in the admin server CRUD list view.
+- Added configurable "Manage in Pterodactyl" button on the user server management page (can be enabled/disabled in settings).
+- Added configurable price format settings - customizable decimal and thousands separators for price display.
+- Added configurable datetime format settings - date format, timezone, and timezone visibility can be set per installation.
+- Added configurable minimum top-up amount setting for wallet balance.
+- Added custom head scripts setting - arbitrary scripts can be injected into the `<head>` of the landing page and panel.
+- Added code editor field type for settings with syntax highlighting support.
+- Added short description field to products for use in SEO metadata and store listing previews.
+
+### Changed
+- Improved admin server CRUD list view - Pterodactyl server identifier is now shown in a shortened form on the index page.
+- Updated contribution documentation - improved CONTRIBUTING.md, PR template, issue templates, and code of conduct.
+- Updated help link in product CRUD controllers.
+- Added Mailhog to the development Docker environment for local email testing.
+
+### Fixed
+- Fixed server state in the servers list showing as unknown when the status check cannot be performed.
+- Fixed doubled server ID appearing in the server name after migration from Pterodactyl.
+- Fixed invalid YAML escaping in the Italian translation file.
+- Fixed theme export functionality that was producing invalid archives.
+- Fixed plugin migration not wrapping schema changes in a database transaction.
+- Fixed saving the default theme context in theme settings.
+- Fixed EasyAdmin CRUD controllers not calling the parent `configureFields` method, causing plugin-registered fields to be dropped.
+- Fixed node selection not respecting Pterodactyl maintenance mode - nodes in maintenance are now skipped during automatic selection and rejected when chosen manually.
+
+---
+
 ## [0.6.3] - 2026-02-03
 
 ### Added

diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -56,6 +56,9 @@ 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.
 
+This includes our GitHub repository, Discord server (discord.gg/Gz5phhuZym),
+and any other official community spaces.
+
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
 # Contributing to PteroCA
 
-Thank you for your interest in contributing to **PteroCA**! We welcome contributions from everyone. Here’s how you can help:
+Thank you for your interest in contributing to **PteroCA**! We welcome contributions from everyone. Here's how you can help:
 
 ## How to Contribute
 
@@ -23,57 +23,124 @@ We love new ideas! If you have a feature request, follow these steps:
 ### Submitting Pull Requests
 
 1. **Fork the repository**: Create your own fork of the repository by clicking the "Fork" button in the top right of our [GitHub repository](https://github.com/pteroca-com/panel).
-2. **Create a new branch**: Use a descriptive name for your branch. For example: `feature/add-payment-integration` or `bugfix/fix-user-auth`.
+2. **Create a new branch**: Use a descriptive name for your branch. See [Branch Naming](#branch-naming) below.
 3. **Make changes**: Add your code, following our coding standards:
     - Follow PSR-12 for PHP.
     - Write clear, concise code with comments where necessary.
     - Write tests for your code whenever possible.
-4. **Commit your changes**: Write meaningful and descriptive commit messages.
+4. **Commit your changes**: Write meaningful and descriptive commit messages. See [Commit Messages](#commit-messages) below.
 5. **Push to your fork**: Push the changes from your local repository to your fork on GitHub.
-6. **Submit a pull request**: From your forked repository, click the “New Pull Request” button. Ensure that your pull request is well-documented and references any issues it resolves.
+6. **Submit a pull request**: From your forked repository, click the "New Pull Request" button. Make sure your PR targets the `main` branch.
 
-### Code Review and Feedback
+## Branch Naming
 
-- **Be patient**: Our maintainers will review your pull request as soon as possible. We may ask you to make additional changes.
-- **Tests**: Ensure your pull request passes all tests before submission. Use PHPUnit for testing the PHP code.
-- **Constructive Feedback**: If your pull request is rejected, don’t be discouraged. We will provide constructive feedback to help you improve.
+Use the following naming conventions for your branches:
 
-## Community Guidelines
+- `feature/<name>` — new functionality (e.g. `feature/add-payment-integration`)
+- `bugfix/<name>` — bug fixes (e.g. `bugfix/fix-user-auth`)
+- `hotfix/<name>` — urgent fixes for production issues
+- `task-<id>-<name>` — tasks tracked in the issue tracker (e.g. `task-42-improve-logging`)
 
-- **Be respectful**: We value a welcoming, respectful, and inclusive community. Disrespectful or inappropriate behavior will not be tolerated.
-- **Collaboration**: Help fellow contributors by reviewing pull requests and participating in discussions.
-- **Support**: For usage or configuration questions, please refer to our [Documentation](https://pteroca.gitbook.io) and the [Discord Support Server](https://discord.gg/Gz5phhuZym).
+## Commit Messages
+
+Write clear, descriptive commit messages in English. Focus on what the change does and why:
+
+**Good examples:**
+- `Add user balance notification on low funds`
+- `Fix server suspension not triggered on expired subscription`
+- `Refactor payment gateway to support multiple providers`
+
+Avoid vague messages like `fix`, `update`, or `WIP`.
+
+## Pull Request Process
+
+1. **Target `main`** — all PRs should target the `main` branch.
+2. **CI pipeline must pass** — the GitHub Actions CI pipeline runs automatically on every PR. A PR with a failing pipeline will not be reviewed. See [CI Pipeline](#ci-pipeline) for details.
+3. **Code review** — a maintainer will review your pull request. Be patient; we will provide feedback as soon as possible.
+4. **Address all comments** — all review comments must be addressed before the PR can be merged.
+5. **Resolve all threads** — all discussion threads must be marked as resolved before merge.
+6. **Merge** — once approved and all checks pass, a maintainer will merge the PR.
+
+## CI Pipeline
+
+Every pull request to `main` or `develop` automatically triggers the GitHub Actions CI pipeline (`symfony.yml`). The pipeline must pass before a PR will be reviewed or merged.
+
+The pipeline checks:
+
+- **PHPStan** (static analysis, level 1) — ensures no type errors or undefined references
+- **Doctrine Migrations** — all migrations must execute without errors
+- **Translation completeness** — no translation keys may be missing from any language file
+
+### Running checks locally
+
+Before pushing, you can run the checks inside the Docker development container:
+
+```bash
+# Static analysis
+docker exec -it pteroca_web_dev vendor/bin/phpstan analyse
+
+# Database migrations
+docker exec -it pteroca_web_dev bin/console doctrine:migrations:migrate --no-interaction
+
+# Translation check (replace messages.pl.yaml with any non-English file)
+docker exec -it pteroca_web_dev bin/console app:show-missing-translations \
+  src/Core/Resources/translations/messages.en.yaml \
+  src/Core/Resources/translations/messages.pl.yaml
+```
+
+> **Note:** A PR with a failing CI pipeline will not be reviewed. Fix all issues before requesting a review.
 
 ## Setting Up Your Development Environment
 
+PteroCA uses Docker for local development. Make sure you have [Docker](https://docs.docker.com/get-docker/) and [Docker Compose](https://docs.docker.com/compose/install/) installed.
+
 1. **Clone the repository**:
     ```bash
     git clone https://github.com/pteroca-com/panel.git
     cd panel
     ```
 
-2. **Install dependencies**:
-    Make sure you have [Composer](https://getcomposer.org/) installed. Run:
+2. **Configure environment**:
     ```bash
-    composer install
+    cp .env.SAMPLE .env
+    # Edit .env with your local settings
     ```
 
-3. **Set up the environment**:
-    Create a `.env.local` file from `.env.example` and configure your database and environment variables:
+3. **Start the containers**:
     ```bash
-    cp .env.example .env.local
+    docker-compose up -d
     ```
 
 4. **Run migrations**:
     ```bash
-    php bin/console doctrine:migrations:migrate
+    docker exec -it pteroca_web_dev bin/console doctrine:migrations:migrate
     ```
 
 5. **Start developing!**
 
+> All Symfony and Composer commands must be executed inside the `pteroca_web_dev` container:
+> ```bash
+> docker exec -it pteroca_web_dev bin/console [symfony-command]
+> docker exec -it pteroca_web_dev composer [composer-command]
+> ```
+
+For more details, see our [Documentation](https://docs.pteroca.com).
 
 ## Helping with Translations
-We want PteroCA to be accessible to users all over the world. If you're interested in helping translate PteroCA into more languages, you can contribute via our [Crowdin page](https://crowdin.com/project/pteroca). No coding skills are required—just your language expertise!
+
+We want PteroCA to be accessible to users all over the world. If you're interested in helping translate PteroCA into more languages, you can contribute directly via a pull request.
+
+**Important rules for translations:**
+
+- When **adding new translation keys or editing existing ones**, update all language files located in `src/Core/Resources/translations/`.
+- The English file (`messages.en.yaml`) is the reference — make sure the key exists there first, then add the translated value to each other language file.
+- The CI pipeline checks for missing translation keys — your PR will fail if any language file is incomplete.
+
+## Community Guidelines
+
+- **Be respectful**: We value a welcoming, respectful, and inclusive community. Disrespectful or inappropriate behavior will not be tolerated.
+- **Collaboration**: Help fellow contributors by reviewing pull requests and participating in discussions.
+- **Support**: For usage or configuration questions, please refer to our [Documentation](https://docs.pteroca.com) and the [Discord Support Server](https://discord.gg/Gz5phhuZym).
 
 ## License
 

diff --git a/README.md b/README.md
@@ -286,6 +286,8 @@ We welcome contributions from developers of all skill levels!
 
 [Read the Contributing Guide →](CONTRIBUTING.md)
 
+> **Before submitting a PR:** Make sure the CI pipeline passes (PHPStan, migrations, translations) and that your branch is up to date with `main`. All review threads must be resolved before merge.
+
 ---
 
 ## 📄 License

diff --git a/composer.json b/composer.json
@@ -1,7 +1,7 @@
 {
     "name": "pteroca/panel",
     "description": "PteroCA.com is a free, open-source client area and management panel designed specifically for Pterodactyl server users and hosting providers. The platform simplifies and automates server management with a user-friendly interface and robust billing features.",
-    "version": "0.6.3",
+    "version": "0.6.4",
     "type": "project",
     "license": "MIT",
     "minimum-stability": "stable",
@@ -33,6 +33,7 @@
         "symfony/dotenv": "^7.0",
         "symfony/flex": "^2",
         "symfony/framework-bundle": "^7.0",
+        "symfony/html-sanitizer": "^7.0",
         "symfony/http-client": "^7.0",
         "symfony/http-foundation": "^7.0",
         "symfony/mailer": "^7.0",
-Original file line number
+Diff line change
@@ Expand Up @@
     [Read the Contributing Guide →](CONTRIBUTING.md)
+    > **Before submitting a PR:** Make sure the CI pipeline passes (PHPStan, migrations, translations) and that your branch is up to date with `main`. All review threads must be resolved before merge.
     ---
     ## 📄 License
@@ Expand Down @@