At now this is only a plain HTML site, but we are working with Omar Aguirre one of the project co-maintainers to convert this to a Drupal 8 site. I will keep you informed.

The new installer

One of the most recurring questions since project started is why is the installation process modifying the composer.json & composer.lock file, or why is the installer adding new libraries to "core/vendor" directory, because you know that is considered hacking the core.

When using the new installer method, we are no longer modifying the composer.json & composer.lock files or adding extra libraries to "core/vendor" directory.

The new executable phar file

Before showing you how to execute the console.phar lets try to undestand what is a phar file, based on the official php documentation

Phar archives are best characterized as a convenient way to group several files into a single file. As such, a phar archive provides a way to distribute a complete PHP application in a single file and run it from that file without the need to extract it to disk. Additionally, phar archives can be executed by PHP as easily as any other file, both on the commandline and from a web server. Phar is kind of like a thumb drive for PHP applications.

How to execute the console.phar file:

//Use the console.phar
$ php console.phar

You can see how easy is to run the installation process and execute the console.phar file on the following animated gif (I am using this image format because is vintage and cool).

Putting all the pieces together, and as I mentioned on twitter a few days ago. I will show you how to create a Drupal 8 module in 4 easy steps:

Feel fee to try the new installer and console executable phar file and make sure you let us know any inconvenience, error messages or recommendations commenting on this page, or adding a new issue on the drupal project page or the github repository.