Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78311
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.44 as permitted sender)
MIME-Version: 1.0
Date: Fri, 24 Oct 2014 22:52:55 +0400
Message-ID: <CAHpw9AfyLRPmD6Yr35WNDju83oozVNeu3WyAGJAygBO2SxisEw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8f502c588ca8f005062fb194
Subject: Thoughts on the PHP.net website
From: drgomesp@gmail.com (Daniel Ribeiro)

--e89a8f502c588ca8f005062fb194
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Good evening, Internals!

*Disclaimer: *I wanted to bring this discussion inside the internals
mailing list not only because of the fact that the PHP.net website's source
code on GitHub doesn't have issues enabled, but especially because I think
it's part of the PHP environment, just like the spec or the actual C code
itself.

You all know the http://php.net website and it's source code
<https://github.com/php/web-php>. It comes to my attention that this source
code is pretty much a very good example of how *not *to build websites in
PHP =E2=80=94 the source code predates the PHP 3 days, but that's just one =
of the
problems. I'm not go further into the details of the problems we actually
have inside that code, as they are very obvious and the source code speaks
for itself =E2=80=94 of course, if needed, we can discuss this in more deta=
il later.

What I wanted to know from you is: would it be interesting if we started a
complete rewrite of the website, not only for actually improving it, but
also for making it serve as a reference for people to see how the PHP
environment has evolved and what are the good practices we use these days
for building websites?

Cheers!

Daniel Ribeiro
http://danielribeiro.org

--e89a8f502c588ca8f005062fb194--