Coding Standards
Basic standards and linting configuration
Last updated
Basic standards and linting configuration
Last updated
Besides the language specific standards below, we always include an file in code repositories for easier IDE configuration. Most IDEs either support this by default or need .
Since we depend on WordPress, PHP is the main language we use for backend development.
We follow as a base for coding standards, but with some exceptions and additions. To make it easier to lint our code, either in CI or locally in the IDE, we always include a file to the root of all of our code repositories.
We also rely on for autoloading.
We use for managing dependencies.
Python is also being used for certain use cases. Mainly for scripting and functionality that needs to run in a pipeline. In most cases this is done to avoid writing shell scripts that are harder to read and maintain.
We follow PEP8 as a base for coding standards. We include a file in our code repositories to enable linting.
We use for managing dependencies.
For all frontend dependencies we use package manager and for building and bundling assets for production.
Besides using vanilla Javascript, in some cases we also rely on the framework for most of our frontend work.
We are using to enforce coding standards that extends WordPress eslint configuration. We include an file in our code repositories.
Besides using vanilla CSS, when the complexity increases we rely on to achieve better readability and maintenance.
We include a file to enforce linting and certain syntax rules.
We use for automated auditing of new code during our Pull Requests pipelines. We also have enabled vulnerability scanning and automated packages security updates on GitHub.
We use for “end to end” testing. It’s a Javascript based framework, used also by Wordpress.
For technical documentation we use . Since the project is open source, the documentation is also and it’s automatically synced with a .