An open API service indexing awesome lists of open source software.

https://github.com/donini/wc-poa-2017

WordCamp POA 2017 remote CSS environment.
https://github.com/donini/wc-poa-2017

wordcamp wordpress wordpress-development

Last synced: about 2 months ago
JSON representation

WordCamp POA 2017 remote CSS environment.

Awesome Lists containing this project

README

          

# WordCamp POA 2017

WordCamp POA 2017 remote CSS environment.

## Configuration

The project configuration is managed by WP-CLI. [Click here](http://wp-cli.org/config/) 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.

## Installation

Be sure that you set your local configuration. You must have installed composer and NPM.

To install the environment, run

$ bin/install.sh

## Server

The environment can be executed over the PHP Internal Server. To run the server, execute

$ vendor/bin/wp server

## Grunt tasks

The Grunt task runner is used to automate the common tasks of the project.

### default

The default task update the project with the server. Execute this task before starting the development ou after git synchronization.

$ grunt

### watch

Listen all changes in the project files. This command is integrated with the [Livereload](http://livereload.com/extensions/) 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

Build the CSS file that is imported by the WordCamp website. The location of the file is `build/style.css`.

$ grunt build

## WordPress Management

The project use [WP-CLI](http://wp-cli.org/) and [WPackagist](http://wpackagist.org/) 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](http://wpackagist.org/) home page to see how to define them.

## The public directory

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.

## Stylus

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](http://stylus-lang.com/).