WordCamp POA 2018 remote CSS environment.
The project configuration is managed by WP-CLI. Click here to read more about WP-CLI configuration.
Create a copy of the wp-cli.yml file called wp-cli.local.yml and configure with your local parameters.
Be sure that you set your local configuration. You must have installed composer and NPM.
To install the environment, run
$ bin/install.sh
The environment can be executed over the PHP Internal Server. To run the server, execute
$ vendor/bin/wp server
The Grunt task runner is used to automate the common tasks of the project.
The default task update the project with the server. Execute this task before starting the development ou after git synchronization.
$ grunt
Listen all changes in the project files. This command is integrated with the Livereload browser extension. To any server file change, the browser automatically refresh the page. This command maintain alive until you kill it with a ctrl + c. Maintain alive while you work in the development.
$ grunt watch
Build the CSS file that is imported by the WordCamp website. The location of the file is build/style.css.
$ grunt build
The project use WP-CLI and WPackagist to manage the WordPress Core, plugins and themes installation.
The WP-CLI manage the core updates and maintenance tasks, like wp-config generation and database installation. The plugins and themes of the official WordPress repository is defined in the composer.json. Read the WPackagist home page to see how to define them.
The public directory contain the WordPress installation. This directory is not part of the project. The files in this directory cannot be modified. They can overrid during an install or update command.
Configure your webserver to the public directory to be the root directory of the server.
This env use stylus to preprocess the CSS styles. The files stay inner the theme/stylus. The files is processed by grunt tasks. Read the Stylus documentation.