Download the PHP package greenpeace/planet4-gpnl-plugin-gutenberg-blocks without Composer

On this page you can find all versions of the php package greenpeace/planet4-gpnl-plugin-gutenberg-blocks. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package planet4-gpnl-plugin-gutenberg-blocks

Greenpeace P4NL Gutenberg Blocks Plugin

! WorkInProgress

Contents

Introduction

This WordPress plugin provides the necessary blocks to be used with Gutenberg with Twig.

Composer

We use composer as dependency manager for the this plugin. To install dependencies run

$ composer install

Code standards

We follow the WordPress Coding Standards

We use a custom php codesniffer ruleset which adds some rules over WordPress-Core, WordPress-Docs and WordPress-Extra rulesets.

WordPress Coding Standards Rulesets

WordPress Coding Standards Wiki

To run the php codesniffer

$ vendor/bin/phpcs or $ composer sniffs

To run the php code beautifier and fixer

$ vendor/bin/phpcbf or $ composer fixes

Contribute

Please read the Contribution Guidelines for Planet4.

Commit guidelines

Included is a githook (commit-msg) which is run to ensure standardized commit messages. Conventional commits is used as the convention.

In short:

Section Explanation
'Maintenance' type Revert Merge
Type build docs feat fix perf refactor style test chore
Scope Optional explanation of the scope of the change ie ux ui admin etc
Breaking change When a breaking change is introduced use ! after the commit type
Description 10-52 char explanation what the commit does
Body Optionally more axplanation on the what and why

The following commits correlate to SemVer version changes.

Commit SemVer change
commit with ! Major version change, ie 2.x.x
commit type feat Minor version change, ie x.2.x
commit with type fix Patch version change, ie x.x.2

Build process

Development

To watch the files run yarn start.

Build for production

To build files for production run yarn build.

Browserslist

All source code gets transpiled according to our actual usage data. To make sure we don't support too old browsers, the usage data should be refreshed every once in a while (once-twice a year).
Generating the usage data can be done using browserslist-ga-export

Linting

Linters for both CSS and JS are available both for linting and fixing.
yarn lint yarn lint:fix for both CSS and JS
yarn lint:[css/js] for either CSS or JS
yarn lint:[css/js]:fix for either CSS or JS

Release preparation

Release steps are largely automated, this includes: changing branching to loosely follow gitflow, generating assets generating changelogs and tagging the new release. Only (purposely) manual step left is pushing the branches and tags to remote. Changelogs are autogenerated by standard-version if the commit guidelines are followed.
yarn release for running releases yarn dryrelease for checking what the impact of a release is.
CircleCI is used as the CI automation. Steps for releasing new versions are in the Planet4 Documentation

Dependencies

Adding external dependencies for a block can be done by enqueueing an asset and enqueueing external assets like so:

asd

All versions of planet4-gpnl-plugin-gutenberg-blocks with dependencies

PHP Build Version
Package Version
No informations.
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package greenpeace/planet4-gpnl-plugin-gutenberg-blocks contains the following files

Loading the files please wait ....