PHPackages                             achttienvijftien/building-techniques - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. achttienvijftien/building-techniques

ActivePhpcodesniffer-standard[Utility & Helpers](/categories/utility)

achttienvijftien/building-techniques
====================================

Building techniques for WordPress

1.1.0(1y ago)22.5k↑38.6%12GPL-3.0-or-laterPHP

Since Nov 6Pushed 1y ago3 watchersCompare

[ Source](https://github.com/achttienvijftien/building-techniques)[ Packagist](https://packagist.org/packages/achttienvijftien/building-techniques)[ RSS](/packages/achttienvijftien-building-techniques/feed)WikiDiscussions main Synced 2d ago

READMEChangelogDependencies (2)Versions (3)Used By (12)

Building techniques for WordPress
=================================

[](#building-techniques-for-wordpress)

This package contains the building techniques (=code style) used in WordPress projects.

### About

[](#about)

This package provides a ruleset for PHP\_CodeSniffer that extends the ruleset for [Timber](https://github.com/timber/timber), which is composed of the [WordPress coding standard](https://github.com/WordPress/WordPress-Coding-Standards) with some added exceptions. The deviations from the WordPress coding standard are:

- Class filenames should adhere to PSR-4.
- Classnames should use StudlyCaps.
- Lines should be 100 chars long maximum (triggers warning),
- Lines should in no case exceed 120 characters (triggers error).
- Allow `/` as word delimiter in hook names.
- Allow short array syntax (`[]`).

### Prerequisites

[](#prerequisites)

Install [Composer](https://getcomposer.org/) to add this package to your project.

### Installing

[](#installing)

Install the package using composer:

```
composer require --dev achttienvijftien/building-techniques
```

After the installation, the `phpcs` and `phpcbf` scripts are available in the `vendor/bin` folder.

We recommend also installing [phpcodesniffer-composer-installer](https://github.com/DealerDirect/phpcodesniffer-composer-installer)to automatically register the coding standard with PHP\_CodeSniffer:

```
composer require --dev dealerdirect/phpcodesniffer-composer-installer
```

Now, the coding standard should be available for use when running `phpcs`. You can check the installed coding standards by running:

```
./vendor/bin/phpcs -i
```

The list should contain `1815BuildingTechniques`.

### Usage

[](#usage)

To run PHP\_CodeSniffer with the appropriate coding standard:

```
./vendor/bin/phpcs --standard=1815BuildingTechniques path/to/file-or-directory
```

To fix code style violations that can be corrected automatically:

```
./vendor/bin/phpcbf --standard=1815BuildingTechniques path/to/file-or-directory
```

#### Adding composer scripts

[](#adding-composer-scripts)

Composer scripts for `phpcs` and `phpcbf` can be added to composer.json for convenience.

```
{
    "scripts": {
        "format": "phpcbf --standard=1815BuildingTechniques --report-summary --report-source",
        "lint": "phpcs --standard=1815BuildingTechniques"
    }
}
```

#### IDE Support

[](#ide-support)

Please refer to the Wiki for guides on integrating PHP\_Codesniffer with IDEs like PhpStorm.

###  Health Score

32

—

LowBetter than 69% of packages

Maintenance34

Infrequent updates — may be unmaintained

Popularity23

Limited adoption so far

Community20

Small or concentrated contributor base

Maturity44

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~338 days

Total

2

Last Release

632d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/6b266fbc7c6022e0bd39e3e1f06d75029dda33bae8d4a109d79824cb6f3bbf18?d=identicon)[dennisenderink](/maintainers/dennisenderink)

![](https://www.gravatar.com/avatar/d1030590f60d21fefa30620a1c50195fa207c5ed67f618326ba6ad781264301c?d=identicon)[omnisite](/maintainers/omnisite)

![](https://www.gravatar.com/avatar/25ddb3567dc50c66226060bf3be9ea79e580f8c16852a021f2b0c007af75d06f?d=identicon)[tmdk](/maintainers/tmdk)

---

Top Contributors

[![dennisenderink](https://avatars.githubusercontent.com/u/329734?v=4)](https://github.com/dennisenderink "dennisenderink (4 commits)")

---

Tags

coding-standardswordpress

### Embed Badge

![Health badge](/badges/achttienvijftien-building-techniques/health.svg)

```
[![Health](https://phpackages.com/badges/achttienvijftien-building-techniques/health.svg)](https://phpackages.com/packages/achttienvijftien-building-techniques)
```

###  Alternatives

[humanmade/coding-standards

Human Made Coding Standards

160443.1k59](/packages/humanmade-coding-standards)[wp-cli/wp-cli-tests

WP-CLI testing framework

423.1M142](/packages/wp-cli-wp-cli-tests)[woocommerce/woocommerce-sniffs

WooCommerce sniffs

497.5M54](/packages/woocommerce-woocommerce-sniffs)[infinum/eightshift-coding-standards

Eightshift WordPress Coding Standards

1790.9k6](/packages/infinum-eightshift-coding-standards)[syde/phpcs

Syde PHP coding standards for WordPress projects.

1027.6k9](/packages/syde-phpcs)[awesomemotive/wpforms-phpcs

WPForms Coding Standards

148.5k](/packages/awesomemotive-wpforms-phpcs)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)