PHPackages                             enpii/wp-proj - 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. enpii/wp-proj

ActiveWordpress-project[Utility & Helpers](/categories/utility)

enpii/wp-proj
=============

The WordPress project setup for WordPress modern development with Laravel featuring EnpiiBase plugin

v1.0.2(1y ago)019MITPHPPHP ^8.0

Since May 11Pushed 1y ago2 watchersCompare

[ Source](https://github.com/enpiicom/wp-proj)[ Packagist](https://packagist.org/packages/enpii/wp-proj)[ RSS](/packages/enpii-wp-proj/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (20)Versions (6)Used By (0)

### Initialize

[](#initialize)

- Create the project (stable version)

```
composer create-project enpii/wp-proj

```

- Use development version (branch **master**)

```
composer create-project -s dev enpii/wp-proj

```

in case you want to specify the branch (e.g. branch **develop**)

```
composer create-project -s dev enpii/wp-proj:dev-develop

```

- Ensure that you have the **.env** file, if it doesn't exists, you can copy from the example file

```
cp .env.example .env

```

- Then use the appropriate env variables for you working environment, remember to check the SALTS section to use correct ones.

Development
-----------

[](#development)

- Install (or update) the dependencies

```
docker run --rm --interactive --tty -e XDEBUG_MODE=off -v $PWD:/app -v ~/.composer:/root/.composer npbtrac/php80_cli composer install

```

### Deploy with Docker

[](#deploy-with-docker)

The Docker file is built on top of `serversideup/docker-php`  (which are ready for production according to **Server Side** Up team)

- Start all containers

```
docker-compose up -d

```

then the website would be available at (the port 19180 can be edited in **.env** file) - If WP\_DEBUG set to 0 or 'off' or not set, the container wordpress would have xDebug working as we are in the debug mode

- Update composer with Docker (disable xDebug should help the composer install/update faster)

```
docker-compose exec -e XDEBUG_MODE=off wordpress composer update

```

- Run wp-cli (you must run with the user webuser to avoid running as root)

```
docker-compose exec --user=webuser wordpress wp plugin list

```

or check system info

```
docker-compose exec --user=webuser wordpress wp enpii-base info

```

or add Admin user

```
docker-compose exec --user=webuser wordpress wp user create   --user_pass= --role=administrator

```

- Run wp-app artisan

```
docker-compose exec --user=webuser wordpress ./wp-enpii-base-artisan wp-app:hello

```

or

```
docker-compose exec --user=webuser wordpress wp enpii-base artisan wp-app:hello

```

### Working with GIT

[](#working-with-git)

- You can put your own plugins, themes, mu-plugins to corresponding folders. Then if you use git, you can add these things to your repository by:
    - Update the `./wp-content/.gitignore` to allow your plugins, mu-plugins, themes
    - *e.g.* you have a plugin called `hello-world`, you need to add this

    ```
    !plugins/hello-world
    !plugins/hello-world/**

    ```

    - Then you can `git add ` to the repo

### Compiling assets (CSS, JS)

[](#compiling-assets-css-js)

- This repo consists of a sample plugin **Demoda** and a sample theme **Appeara Alpha**, it has the webpack configs to compile plugin and theme CSS and JS. The assets would be compiled to `public-assets/dist` folders

To install dependencies

```
docker compose exec wordpress yarn install

```

Compile plugin assets

```
docker compose exec wordpress yarn build-plugin

```

or to watch and compile

```
docker compose exec wordpress yarn dev-plugin

```

Similarly to the theme with

```
docker compose exec wordpress yarn build-theme

```

and watch

```
docker compose exec wordpress yarn dev-theme

```

### Working with Translation

[](#working-with-translation)

- Create the pot file for the Appeara Alpha theme

```
docker compose exec --user=webuser wordpress yarn i18n:make-pot

```

*e.g.*

```
docker compose exec --user=webuser wordpress yarn i18n:make-pot public/wp-content/themes/appeara-alpha public/wp-content/themes/appeara-alpha/languages/appeara-alpha.pot

```

**Notes**: if you are using Yarn < 1.0, you need to add `--` before arguments like this

```
docker compose exec --user=webuser wordpress yarn i18n:make-pot -- public/wp-content/themes/appeara-alpha public/wp-content/themes/appeara-alpha/languages/appeara-alpha.pot

```

- Update the pot file to existing po files (same parent folder)

```
docker compose exec --user=webuser wordpress yarn i18n:update-po

```

*e.g.*

```
docker compose exec --user=webuser wordpress yarn i18n:update-po public/wp-content/themes/appeara-alpha/languages/appeara-alpha.pot

```

- Create mo file (from po file), same parent folder

```
docker compose exec --user=webuser wordpress yarn i18n:make-mo

```

*e.g.*

```
docker compose exec --user=webuser wordpress yarn i18n:make-mo public/wp-content/themes/appeara-alpha/languages/appeara-alpha-vi.po

```

**Notes**: Of course you can update the script (in package.json) to match your project.

### Working with PHP Code Styling (PHPCS)

[](#working-with-php-code-styling-phpcs)

- Check PHP code style of the project (using phpcs configuration file)

```
docker compose exec wordpress yarn phpcs

```

- Check PHP code style of a certain directory

```
docker compose exec wordpress yarn phpcs

```

*e.g.*

```
docker compose exec wordpress yarn phpcs public/wp-content/plugins/demoda

```

you should use the relative path

- Repair PHP code style

```
docker compose exec wordpress yarn phpcbf

```

*e.g.*

```
docker compose exec wordpress yarn phpcbf public/wp-content/plugins/demoda

```

### Working with Unit Test

[](#working-with-unit-test)

This project uses PHPUnit and configured Codeception Test framework. You should use PHPUnit to run the test because it supports isolationProcess which allow Mockery overload, alias to happen. You can run Codeception if you want.

#### Creating test files

[](#creating-test-files)

- Add a new Unit Test file

```
docker-compose exec --user=webuser wordpress wp enpii-base artisan wp-app:make:phpunit

```

e.g

```
docker-compose exec --user=webuser wordpress wp enpii-base artisan wp-app:make:phpunit tests/Unit/Demoda/App/WP/Tmp_Test

```

or with Codeception

```
docker compose exec wordpress yarn codecept:generate-unit Demoda/Test/Test.php

```

this command will create the file `Demoda/Test/Test.php` to the path of codeception unit setting `suites/tests/unit`. **DO REMEMBER** to use the `setUp()` method instead of the `_before()` to be able to run the test file with the PHPUnit as well.

#### Running Unit Test

[](#running-unit-test)

- Run Unit Test on a single file/folder with PHPUnit

```
docker compose exec wordpress yarn phpunit tests/Unit/Demoda

```

- If you want to run Unit Test for a file/folder and only want the coverage report on a certain file/folder you can run with PHPUnit

```
docker compose exec wordpress yarn phpunit:coverage-single --whitelist=

```

*e.g.* (with extra `--debug` option)

```
docker compose exec wordpress yarn phpunit:coverage-single --bootstrap=tests/bootstrap-unit.php --debug --whitelist=public/wp-content/plugins/demoda/src/App/WP/Demoda_WP_Plugin.php tests/Unit/Demoda/App/WP/Demoda_WP_Plugin_Test.php

```

- Run Unit Test with PHPUnit (with coverage report to the folder `tests/_output/phpunit`)

```
docker compose exec wordpress yarn phpunit:coverage-html tests/_output/phpunit

```

or you just want to see the result in the console (not an HTML file)

```
docker compose exec wordpress yarn phpunit:coverage

```

**Notes**: You can use Codeception for Unit testing as the configuration is there but Codeception does not support isolationProcess, that means the test with Mokery overload would fail.

```
docker compose exec wordpress yarn codecept:unit

```

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance39

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity49

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 50% 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 ~102 days

Total

3

Last Release

527d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/7f8da7894da0f0f0b698496fd19ce845bbfe19987b5e990fa6793715b4698464?d=identicon)[npbtrac](/maintainers/npbtrac)

---

Top Contributors

[![loikimle](https://avatars.githubusercontent.com/u/50190659?v=4)](https://github.com/loikimle "loikimle (7 commits)")[![npbtrac](https://avatars.githubusercontent.com/u/295365?v=4)](https://github.com/npbtrac "npbtrac (7 commits)")

---

Tags

laravelwordpressboilerplatewordpress laravelEnpiiBaseEnpiiTeamEnpiiDev

###  Code Quality

TestsPHPUnit

Static AnalysisPHPStan

Type Coverage Yes

### Embed Badge

![Health badge](/badges/enpii-wp-proj/health.svg)

```
[![Health](https://phpackages.com/badges/enpii-wp-proj/health.svg)](https://phpackages.com/packages/enpii-wp-proj)
```

###  Alternatives

[johnpbloch/wordpress

WordPress is open source software you can use to create a beautiful website, blog, or app.

6079.5M471](/packages/johnpbloch-wordpress)[log1x/pagi

A better WordPress pagination.

59105.4k](/packages/log1x-pagi)

PHPackages © 2026

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