Scientific and interactive Gutenberg Blocks for WordPress
- Node.js (our recommendation: nvm)
- docker
- use EditorConfig plugin
- use Prettier and enable the option
Format On Save
- switch to project's node version
nvm use
- install dependencies
npm ci
- start wp dev environment
npx wp-env start
- start dev server
npm start
Each commit message must conform to Conventional Commits spec. A message must be structured as follows:
<type>(<scope>): <short summary>
- The
type
andshort summary
are mandatory - The
scope
is optional - The
short summary
must be in present tense
example
docs: correct spelling of README
Must be one of the following:
- build: Changes that affect the build system or external dependencies
- ci: Changes to our CI configuration files
- docs: Documentation changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
A branch name should be composed as follows:
<type>/<description>
example
feat/add-blue-button
- feat: Adds features or general changes
- bugfix: Fixes a bug
- release: Maintains a specific release version
- wip: unknown, when it will be completed