Skip to content

[WIP] Why use PHP #1172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft

[WIP] Why use PHP #1172

wants to merge 5 commits into from

Conversation

saundefined
Copy link
Member

@saundefined saundefined commented Dec 3, 2024

Copy link
Contributor

github-actions bot commented Dec 3, 2024

🚀 Regression report for commit 837e36b is at https://web-php-regression-report-pr-1172.preview.thephp.foundation

Copy link
Contributor

github-actions bot commented Dec 3, 2024

🚀 Preview for commit 837e36b can be found at https://web-php-pr-1172.preview.thephp.foundation

@lwlwilliam
Copy link
Contributor

I feel this is very suitable as the homepage of the official website. At present, the release log on the homepage only needs to display the title of the latest article in highlighted font. In addition, there should be an archive entrance in the navigation bar, which will look much more comfortable.

@AndriusBartulis
Copy link

AndriusBartulis commented Dec 5, 2024

I feel this is very suitable as the homepage of the official website. At present, the release log on the homepage only needs to display the title of the latest article in highlighted font. In addition, there should be an archive entrance in the navigation bar, which will look much more comfortable.

+1 Very much agree! The landing/home page should be about what PHP is, and why you should trust it for your project (used by x, case studies, use cases, power of the vast ecosystem etc).

Updates/announcements are of course very important, but would work well as a secondary page.

Having said this, the current design of the page in this PR would of course need adjusting to match the styling of the current homepage, potentially keeping the existing top "hero" section.

@pronskiy
Copy link
Contributor

pronskiy commented Dec 9, 2024

@lwlwilliam, @AndriusBartulis, thanks for your feedback!
The plan is to launch it as a separate page, polish, analyse analytics data (#1183) and then plan how to update the main page.

@jacekkarczmarczyk
Copy link

I think it's worth mentioning somewhere at the top:

  • standarized dependency management (composer)
  • built-in strong typing and external type checking and linting tools (phpstan, psalm etc)
  • mature testing libraries (phpunit, pest)
  • standards (PHP-FIG packages like Container, Cache etc., coding standards, PER, PSR)

I think these things are important to show that PHP is not only for simple pages or WP blogs (as many people may see PHP), but also for enterprise applications

{
return new Response(
headers: ['Content-Type' => 'text/html'],
body: '<h1>Welcome to the Modern PHP Application!</h1>'
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
body: '<h1>Welcome to the Modern PHP Application!</h1>'
body: '<h1>Welcome to Modern PHP!</h1>'

Not sure what the best exact wording is, but I believe the current sentence is incorrect, right?

<li>
E-commerce platforms: <a href="https://woocommerce.com/">WooCommerce</a>,
<a href="https://www.shopware.com/">Shopware</a>,
<a href="https://prestashop.com/">PrestaShop</a>.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😉

Suggested change
<a href="https://prestashop.com/">PrestaShop</a>.
<a href="https://prestashop.com/">PrestaShop</a>,
<a href="https://sylius.com/">Sylius</a>

@saundefined saundefined changed the title Why use PHP [WIP] Why use PHP Mar 27, 2025
@pawelkudzia
Copy link

Great job, I really like idea about website like that! I can suggest adding info about the Symfony framework and it's ecosystem. If you can add it, then it would be amazing :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants