Namespaces

PHP part of this project lives in eightshiftLibs namespace.

Because WordPress lives in a global namespace, we had to provide the way for your project to be unique. That is why we implemented Imposter script inside composer.json. Imposter adds a namespace prefix on all the packages inside the vendor folder that uses namespacing.

You can change the vendor prefix in your composer.json file. But if you do this, make sure you delete the vendor folder before running the command to install the composer packages again with the composer install command.

"autoload": {
  "psr-4": {
    "CustomProject\\": "src/"
  }
},
"extra": {
  "imposter": {
    "namespace": "eightshiftBoilerplateVendor"
  }
}

For example, with the default setup, your project will have the namespace you defined in the setup process. But let's say you have the structure from the parent code:

• Your current namespace is: CustomProject.
• Namespace for all packages used from eightshift libs is eightshiftBoilerplateVendor\CustomProject.
• Also, every package you additionally install will follow the same convention: eightshiftBoilerplateVendor\SomePackageNamespace.

To sum it up: you don't need to change the default vendor prefix if you only run one theme or one plugin with eightshift Boilerplate. But if you have multiple eightshift Boilerplate powered themes or plugins installed, please change the vendor prefix on each of the projects.