Go to file
Sergey Biryukov 0d26989e15 Tests: Update wp_add_inline_script() unit tests to account for the jquery handle being an alias for jquery-core again.
Follow-up to [48323], [48324], [48890].

Props davidbaumwald, audrasjb.
See #50919.

git-svn-id: https://develop.svn.wordpress.org/trunk@48892 602fd350-edb4-49c9-b593-d223f7449a82
2020-08-27 20:52:36 +00:00
.github General: Introduce a pull request template. 2020-02-21 18:23:28 +00:00
src Script Loader: Change the jquery handle back to an alias for jquery-core. 2020-08-27 20:31:23 +00:00
tests Tests: Update wp_add_inline_script() unit tests to account for the jquery handle being an alias for jquery-core again. 2020-08-27 20:52:36 +00:00
tools Block Editor: Add a script to run Gutenberg end 2 end tests on Core. 2020-07-07 16:06:43 +00:00
.editorconfig General: Instruct file editors not to trim trailing whitespace in markdown files. 2018-03-20 22:14:53 +00:00
.env Docs: Fix typo in .env file description. 2019-12-30 13:46:17 +00:00
.eslintignore Build/Test Tools: Enable JSDocs to be linted with ESLint. 2020-07-27 23:33:51 +00:00
.eslintrc-jsdoc.js Build/Test Tools: Enable JSDocs to be linted with ESLint. 2020-07-27 23:33:51 +00:00
.gitignore Build/Test Tools: Introduce Install-changed. It keeps a hash of package.json and compares it when run. If it has any changes, it runs npm install. 2020-03-24 01:04:43 +00:00
.jshintrc Build tools: Fix the travis:js build. 2018-12-24 13:53:11 +00:00
.npmrc Once upon a midnight dreary, while I coded, weak and weary, 2018-05-23 10:04:22 +00:00
.nvmrc Once upon a midnight dreary, while I coded, weak and weary, 2018-05-23 10:04:22 +00:00
.travis.yml Tests: Download Chromium for e2e and JS tests only. 2020-07-13 15:18:49 +00:00
appveyor.yml Build/Test Tools: Remove the dependency on a globally installed Grunt. 2019-05-26 19:34:24 +00:00
composer.json Build/Test Tools: Update the wp-coding-standards/wpcs package. 2020-06-08 20:09:53 +00:00
composer.lock Build/Test Tools: Update the wp-coding-standards/wpcs package. 2020-06-08 20:09:53 +00:00
docker-compose.yml Docs: Fix a typo in the Docker compose file. 2020-06-04 16:51:32 +00:00
Gruntfile.js Build/Test Tools: Replace the banner text from wp-emoji-loader.min.js in formatting.php during build process. 2020-06-19 22:06:28 +00:00
jsdoc.conf.json Build Tools: Fix JSDoc configuration include paths. 2018-06-14 12:45:06 +00:00
package-lock.json Build/Test Tools: Update the package lock file. 2020-08-27 18:56:46 +00:00
package.json Editor: update packages. 2020-08-27 16:34:37 +00:00
phpcompat.xml.dist General: Continuing to work towards a passing PHP Compatibility scan. 2020-06-03 17:38:56 +00:00
phpcs.xml.dist Sitemaps: Add XML sitemaps functionality to WordPress. 2020-06-17 15:22:49 +00:00
phpunit.xml.dist Build/Test Tools: Update code coverage setup in the phpunit.xml.dist file to point to the build directory. 2020-08-23 17:22:28 +00:00
README.md Build/Test Tools: Further enhancements to the local development environment readme. 2020-05-03 14:41:03 +00:00
SECURITY.md Trunk is now 5.6 alpha. 2020-07-28 20:54:37 +00:00
webpack.config.js Build tools: Allow building WordPress to src. 2018-12-24 13:28:22 +00:00
wp-cli.yml Build/Tests: Default to running unit tests from src. 2019-01-09 10:09:02 +00:00
wp-config-sample.php Code Modernization: Replace dirname( __FILE__ ) calls with __DIR__ magic constant. 2020-02-06 06:31:22 +00:00
wp-tests-config-sample.php Tests: Revert the dirname( __FILE__ ) replacement in wp-tests-config-sample.php for now, to avoid breaking unit tests created with WP-CLI scaffold command. 2020-02-06 21:49:13 +00:00

WordPress

Build Status

Welcome to the WordPress development repository! Please check out the contributor handbook for information about how to open bug reports, contribute patches, test changes, write documentation, or get involved in any way you can.

Getting Started

WordPress is a PHP, MySQL, and JavaScript based project, and uses Node for its JavaScript dependencies. A local development environment is available to quickly get up and running.

You will need a basic understanding of how to use the command line on your computer. This will allow you to set up the local development environment, to start it and stop it when necessary, and to run the tests.

You will need Node and npm installed on your computer. Node is a JavaScript runtime used for developer tooling, and npm is the package manager included with Node. If you have a package manager installed for your operating system, setup can be as straightforward as:

  • macOS: brew install node
  • Windows: choco install node
  • Ubuntu: apt install nodejs npm

If you are not using a package manager, see the Node.js download page for installers and binaries.

You will also need Docker installed and running on your computer. Docker is the virtualization software that powers the local development environment. Docker can be installed just like any other regular application.

Development Environment Commands

Ensure Docker is running before using these commands.

To start the development environment for the first time

npm install
npm run build:dev
npm run env:start
npm run env:install

Your WordPress site will accessible at http://localhost:8889. You can see or change configurations in the .env file located at the root of the project directory.

To watch for changes

If you're making changes to WordPress core files, you should start the file watcher in order to build or copy the files as necessary:

npm run watch

To stop the watcher, press ctrl+c.

To run a WP-CLI command

npm run env:cli <command>

WP-CLI has a lot of useful commands you can use to work on your WordPress site. Where the documentation mentions running wp, run npm run env:cli instead. For example:

npm run env:cli help

To run the tests

These commands run the PHP and end-to-end test suites, respectively:

npm run test:php
npm run test:e2e

To restart the development environment

You may want to restart the environment if you've made changes to the configuration in the docker-compose.yml or .env files. Restart the environment with:

npm run env:restart

To stop the development environment

You can stop the environment when you're not using it to preserve your computer's power and resources:

npm run env:stop

To start the development environment again

Starting the environment again is a single command:

npm run env:start

Credentials

These are the default environment credentials:

  • Database Name: wordpress_develop
  • Username: root
  • Password: password

To login to the site, navigate to http://localhost:8889/wp-admin.

  • Username: admin
  • Password: password

To generate a new password (recommended):

  1. Go to the Dashboard
  2. Click the Users menu on the left
  3. Click the Edit link below the admin user
  4. Scroll down and click 'Generate password'. Either use this password (recommended) or change it, then click 'Update User'. If you use the generated password be sure to save it somewhere (password manager, etc).