diff --git a/.prettierrc.json b/.prettierrc.json index c9f33af..7b587f5 100644 --- a/.prettierrc.json +++ b/.prettierrc.json @@ -15,6 +15,8 @@ "files": "**/*.md", "options": { "embeddedLanguageFormatting": "off", + "printWidth": 120, + "proseWrap": "always", "tabWidth": 2 } } diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 527005d..acff96a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -33,8 +33,8 @@ All PHP code must follow these standards: - All tests use **PHPUnit 12+**. - Target **100% code coverage** for new code. -- Run the quality/test scripts defined in the target repository's `composer.json` before submitting a pull request - (for example, `test`, `static`, `ecs`, `rector`, or `check-dependencies`): +- Run the quality/test scripts defined in the target repository's `composer.json` before submitting a pull request (for + example, `test`, `static`, `ecs`, `rector`, or `check-dependencies`): ```bash composer run diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md index 7ba42ca..73fa931 100644 --- a/PULL_REQUEST_TEMPLATE.md +++ b/PULL_REQUEST_TEMPLATE.md @@ -20,8 +20,8 @@ List the checks performed and their results. Explain any relevant checks not run ## Compatibility -Describe any behavior, configuration, dependency, or migration impact. -Write "None" when there is no compatibility impact. +Describe any behavior, configuration, dependency, or migration impact. Write "None" when there is no compatibility +impact. ## Related issues diff --git a/SECURITY.md b/SECURITY.md index 485e1a4..654d505 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -10,17 +10,22 @@ Use GitHub's private vulnerability reporting in the affected repository: 2. Go to the **Security** tab. 3. Click **Report a vulnerability** and describe the issue, how to reproduce it, its impact and any suggested fix. -See [Privately reporting a security vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability). +See +[Privately reporting a security vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability). -If the **Report a vulnerability** button is not available in a repository, open a public issue that only asks for a private contact. Do not include vulnerability details in it. +If the **Report a vulnerability** button is not available in a repository, open a public issue that only asks for a +private contact. Do not include vulnerability details in it. ## Supported Versions -Security fixes are applied to the latest stable release of each package unless the repository documents a different support policy. Older and development versions receive no security updates, although reports about them are welcome. +Security fixes are applied to the latest stable release of each package unless the repository documents a different +support policy. Older and development versions receive no security updates, although reports about them are welcome. ## Response -This project is maintained on a best-effort basis. Reports are reviewed as maintainer availability permits; receipt is acknowledged and updates are given through the private report. No acknowledgment, assessment or remediation deadline is guaranteed. Please do not include vulnerability details in public issues or discussions. +This project is maintained on a best-effort basis. Reports are reviewed as maintainer availability permits; receipt is +acknowledged and updates are given through the private report. No acknowledgment, assessment or remediation deadline is +guaranteed. Please do not include vulnerability details in public issues or discussions. ## Scope diff --git a/profile/README.md b/profile/README.md index 5c686eb..7568fc3 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,4 +1,4 @@ - +

@@ -6,35 +6,20 @@ PHP Forge

- + -PHP tools for frontend assets, project scaffolding, and shared code-quality -configuration. +PHP tools for frontend assets, project scaffolding, and shared code-quality configuration. -Bring these workflows into Composer-based projects, with each tool documented -in its own repository. Read each repository's installation and compatibility -notes before choosing a version. +Bring these workflows into Composer-based projects, with each tool documented in its own repository. Read each +repository's installation and compatibility notes before choosing a version. ## Documentation and contribution Start with each repository's README, or explore the [independent documentation portal](https://yii2-framework.github.io/docs/). -Read the -[contribution guide](https://github.com/php-forge/.github/blob/main/CONTRIBUTING.md) -before proposing a change. For security concerns, follow the -[security policy](https://github.com/php-forge/.github/blob/main/SECURITY.md). - -## Related projects - -Explore [ui-awesome](https://github.com/ui-awesome), -[yii2-extensions](https://github.com/yii2-extensions), -[yii2-framework](https://github.com/yii2-framework), and -[yii3](https://github.com/yii3). - -These are independent project collections. They and the documentation portal -are not official Yii resources. For upstream Yii, visit -[yiisoft](https://github.com/yiisoft). +Read the [contribution guide](https://github.com/php-forge/.github/blob/main/CONTRIBUTING.md) before proposing a change. +For security concerns, follow the [security policy](https://github.com/php-forge/.github/blob/main/SECURITY.md). ## Support this work diff --git a/profile/assets/PROVENANCE.md b/profile/assets/PROVENANCE.md deleted file mode 100644 index 22551b7..0000000 --- a/profile/assets/PROVENANCE.md +++ /dev/null @@ -1,23 +0,0 @@ - - -# PHP Forge cover provenance - -Prepared on 2026-11-03. `php-forge-cover-light.png` and `php-forge-cover-dark.png` are opaque PNG profile covers, each 1280 × 360 pixels. They contain the PHP Forge name and an artisan hammer resting on an anvil. The light and dark versions use the same composition with different backgrounds and text colors; neither has an orange rule. - -## Artwork and typography - -The hammer and anvil are generated supporting artwork, not an official emblem or a photograph of a real workshop. The selected Mjölnir-inspired scene was generated with the built-in image-generation tool. A subsequent image-model edit isolated the hammer and anvil on transparency and completed the cropped anvil. The edit is not an exact pixel cutout; details may differ from the initial scene. The transparent edited artwork used in the covers has SHA-256 `e43e16b0b1deb51ee97bb93855a17364a49ddb21398fda7c904a9c5d7380c086`. - -The organization name was added separately in Nimbus Sans Bold. No font binary is included in these assets. The artwork does not establish an affiliation with any fictional franchise or the creator of a particular depiction of Mjölnir. - -## Asset hashes - -- `php-forge-cover-light.png`: `5c06e086d02702425a7f2bb84d017b802c6cf665c04406414752d2a9d6bf0c6c` (152,676 bytes). -- `php-forge-cover-dark.png`: `049752e9ce20ff81f1aa7215d04599a5c59d4e6e6c3d15c5115f820372af9b66` (147,370 bytes). - -The earlier `php-forge-cover.png` is preserved as a separate draft and is not one of the two theme covers. Its SHA-256 is `30c9028c83e8f3d26c77ef07495b37f836904abbf29ab0927aa7d057d86196fa` (13,498 bytes). - -The selected cover is unlinked and serves as the profile H1. Its alternative -text carries the organization name; native profile text carries the scope and -links. The covers do not configure an organization avatar or a repository -social preview.