Download the PHP package wp-forge/wp-plugin without Composer
On this page you can find all versions of the php package wp-forge/wp-plugin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Table of contents
Download wp-forge/wp-plugin
More information about wp-forge/wp-plugin
Files in wp-forge/wp-plugin
Download wp-forge/wp-plugin
More information about wp-forge/wp-plugin
Files in wp-forge/wp-plugin
Vendor wp-forge
Package wp-plugin
Short Description Create a new WordPress plugin via Composer
License GPL-2.0-or-later
Package wp-plugin
Short Description Create a new WordPress plugin via Composer
License GPL-2.0-or-later
Please rate this library. Is it a good library?
Informations about the package wp-plugin
WordPress Plugin
A WordPress plugin scaffolding template that can be easily installed using Composer.
Requirements
Installation
Run this command in the terminal:
Be sure to append a directory name to the end of the command to customize the folder name that your project will be installed into!
The installation process will check your environment for the required PHP version and PHP extensions. If this presents a
problem and you want to force install anyway, just add the --ignore-platform-reqs
flag to the command.
Notes
- The
.scripts
and.templates
folders are used for scaffolding purposes only and won't exist in your end project. - We use the
@wordpress/env
package to provide a local development environment. This package requires Docker to be installed on your machine. If you don't want to use Docker, you can remove the@wordpress/env
package from thepackage.json
file and delete the.wp-env.json
file. - We use the concept of a hooks folder. Rather than having a bunch of WordPress hooks scattered around your
plugin, the
hooks
folder contains anactions
andfilters
folder where each file name corresponds to the name of a hook (except with dashes in place of underscores). All items that belong in a particular hook are added to the appropriate file, making it easy to find, edit, and add hooks in a consistent way. - This repo has a
source
folder, where you can store any files that require a build step (e.g. scss and js). Theassets
folder is where you store the compiled files that will be used in your plugin. By default, we .gitignore theassets/css
andassets/js
folders. - Currently, this template does not implement any kind of build process. This is something that will be added in the future.
- This repo creates an
.nvmrc
file. If you use NVM, you'll be able to runnvm use
to automatically switch to the correct version of Node for this project. It will default to the version of Node that is running on your machine at the time of install. - This template creates GitHub Action workflows for your plugin. If you are publicly releasing your plugin on the
WordPress.org plugin directory, you will need to add a
SVN_USERNAME
andSVN_PASSWORD
environment variable to your GitHub repository settings. - If your plugin is to be publicly released, the
.wporg
folder is used to store the assets that will be uploaded to the WordPress.org plugin repository.
Reminders
Don't forget to:
- Run
git remote add origin <url>
to add your remote repository - Add a
SVN_USERNAME
andSVN_PASSWORD
environment variable to your GitHub repository settings (if your plugin is to be publicly released) - Push your code to GitHub by running
git push -u origin master
All versions of wp-plugin with dependencies
PHP Build Version
Package Version
The package wp-forge/wp-plugin contains the following files
Loading the files please wait ....