Hello, On Sat, 9 Feb 2019 at 18:56, azjezz <[email protected]> wrote: > > Today i bought a VPS so i can host the mockups for people to see instead of > just looking at the screenshots.
GitHub pages can do that also fine. And they are simpler to use for the case of mockups maybe. Only thing is to learn and understand Jekyll themes and the Liquid template engine. Deployment and stability works like a charm. Or even better one - Sculpin generator (works in PHP, Twig templating engine, generates static files) [1]. > 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. To get a better overview, this is the PHP manual in XML sources (a mirror, not for pull requests) [2]. Migrating the PHP manual sources to Markdown would take a very very long time (I estimate it in several years). Markdown works ok for smaller documentations. Where not so many references, links, additional plugins are required. Markdown has options via custom or 3rd party parsers to make it work a bit like these Sphinx, AsciiDoc and similar generators. One of the good examples is Pandoc. However, here I would leave the final decisions to move from XML to something else to other people who are more suitable and who know what this means. It is a very big step. Too big for only the website remake "task". Hosting on GitHub pages - I'm not sure this is something for PHP.net manual... There is also some dynamics happening there, but don't take me for granted on this part... > 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" Important to understand in this concept is also, that a proper installation chapter wouldn't discriminate against an Alpine Linux. Or some FreeBSD. Or Fedora based distributions which don't use apt package management. Can this be done via patches to existing documentation first maybe or do you think that the docs format need to be adjusted somehow for this? We probably would need to define some frames what we'll be doing here and what even needs to be done in approximate phases. I'm not sure what would be the best way to go here yet. More later on... Have a nice day... [1] https://sculpin.io/ [2] https://github.com/salathe/phpdoc-en -- Peter Kokot -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
