ahmadawais / gutenberg-multi-block-webpack-es6

WORK IN PROGRESS

[WORK-IN-PROGRESS] Stricly, WIP at the moment. Do NOT use it or announce, share it anywhere until I remove this notice and release it to the public.

Gutenberg-Multi-Block-Webpack-ES6

This is a basic custom Gutenberg block. Files explained below.

• block.js — We register Custom Gutenberg block here.
• block.build.js — Built file from block.js via NPM Script and Webpack.
• editor.css _ Block CSS for the editor.
• style.css — Block CSS for the front end.
• index.php — Enqueue block's assets for the editor and the front end.
• .babelrc — Babel custom configuration.
• .gitignore — Git ignore file to ignore node_modules and such other files.
• package.json & package-lock.json — NPM related file for holding NPM related metadata and build/dev NPM scripts.
• webpack.config.js — Webpack configuration file.

Getting Started!

Read the files explained above. All of the files are heavily inline documented. All you have to do is following:

• Open up your favorite terminal app.
• Makes sure NodeJS and NPM are installed by running node -v or npm -v to check their versions.
• Access this directory cd /path/to/gutenberg-boilerplate/block/02-basic-esnext/
• Install node dependencies by running node install or sudo node install
• For building the block.js file into block.build.js you can use run npm scripts.
• To watch and build run npm run dev
• To build for production run npm run build

gutenberg-multi-block-webpack-es6's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.