Re: Add installtion instruction

Hello Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, February 9, 2019 1:48 PM, Peter Kokot <peterkokot@gmail.com> wrote: > Hello, > > On Wed, 6 Feb 2019 at 14:17, azjezz azjezz@protonmail.com wrote: > > > Good afternoon. > > as some of you may know, i am currently working on a new design for the php.net website > > and i came across the installation page[1]. > > the page contains information about "how to compile php from source" but no > > "how to install it" and i think this is not a good for newbies. > > when i started PHP as a kid, i remember using XMAPP on windows, not because i needed > > Apache or MySQL, but because the PHP site kept telling me that i need C > > runtime, VC CRT11 and then i should compile the > > source code and i didn't know how to do that at the time and everything seemed just > > complicated. > > for this, i suggest that w add a new "installation instructions" to the php > > website, and move the current pages to a new section called "compile from source". > > i have added installation instruction page in the mock ups of the new design, you might > > take a look at it here : > > https://github.com/azjezz/web-php-mock-ups/blob/master/screenshots/windows-installation.png > > [1] : https://secure.php.net/manual/en/install.php > > The mockups in general looks great. Installation chapter itself is in > need of major refactoring for sure. Some things are not relevant > anymore and many are missing. Basically, what you're after in this > step is the way to go probably - to mention more options how to get up > and running fast. This probably needs to be synced with the options in > the manual or if a separate docs for only installation should be done > here. PHP installation itself is a very large topic. Compilation from > source is part of the PHP installation chapter. Also installing PHP on > Solaris, for example is also relevant. Goal of PHP is to be used on > any system, even Android and exotic things such as micro controllers. > How that works in practice at the moment, is another topic but for an > overview maybe. > > Few quick tips: > > - There is a migration to Git from SVN happening for the PHP manual. > Yes, the PHP manual is still in SVN at the moment. It is built from > the sources in XML files. Doing some major functionality changes to > the manual means also syncing things with this part and how the manual > is generated. > > - There was a discussion happening about PHP.net mirrors getting > removed so that's one of the major things to be done probably with the > php.net site before other steps maybe. Mirrors at the moment block the > https migration and usage and upgrading the website code to PHP > 7.2/7.3. There is still PHP 5.3 used. And mirrors mean 80+ webservers.. > > -- > Peter Kokot > Today i bought a VPS so i can host the mockups for people to see instead of just looking at the screenshots. I think removing mirrors would be a good step or at least the ones that are using PHP <= 7.2. Another question i have in mind is, after migrating to GIT, is there any plan to switch to markdown instead of XML ? this would be a really great step for the PHP.net website, as we can host the documentation using GitHub Pages without having to worry about deployment etc. and we would just need to make a theme for Jeklly. in the next few days i will host the mock ups, and start writing more about PHP installation in different systems and add the compile from source section. as people would expect something like apt install php ( or similar command on other OSs ) when trying to install php and get started, not "download a compiler , x and y libraries then try to compile it"