Go to file

Sergey Biryukov 00384f94db Docs: Update URLs in some `@link` tags and switch them to HTTPS. Props tsuyoring. Fixes #48479. git-svn-id: https://develop.svn.wordpress.org/trunk@46626 602fd350-edb4-49c9-b593-d223f7449a82		2019-11-01 14:55:51 +00:00
src	Docs: Update URLs in some `@link` tags and switch them to HTTPS.	2019-11-01 14:55:51 +00:00
tests	Code Modernization: Pass an appropriate error level to `trigger_error()` in `_doing_it_wrong()` and related functions:	2019-11-01 00:39:04 +00:00
tools	Block Editor: Remove experimental Social Links blocks	2019-10-15 15:35:03 +00:00
.editorconfig
.env
.gitignore
.jshintrc
.npmrc
.nvmrc
.travis.yml	Build/Test Tools: Don't hardcode the directory name of the repo	2019-10-28 04:15:37 +00:00
appveyor.yml
composer.json	Build/Test Tools: Move Composer script command line directives to the PHPCS ruleset.	2019-09-25 14:01:51 +00:00
composer.lock
docker-compose.yml	Build Tools: Pass the current uid/gid to Docker containers.	2019-09-26 04:57:38 +00:00
Gruntfile.js	Build/Test Tools: Add banner to RTL CSS and minified JS files.	2019-10-26 00:15:53 +00:00
jsdoc.conf.json
package-lock.json	Block Editor: Bug fixes targetted for WordPress 5.3 RC3.	2019-10-28 14:11:06 +00:00
package.json	Block Editor: Bug fixes targetted for WordPress 5.3 RC3.	2019-10-28 14:11:06 +00:00
phpcompat.xml.dist
phpcs.xml.dist	Build/Test Tools: Move Composer script command line directives to the PHPCS ruleset.	2019-09-25 14:01:51 +00:00
phpunit.xml.dist	Ensure `svn:eol-style` is consistently set for all files (part 2).	2019-10-25 19:27:49 +00:00
README.md
webpack.config.js
wp-cli.yml
wp-config-sample.php	Ensure `svn:eol-style` is consistently set for all files.	2019-10-25 16:36:41 +00:00
wp-tests-config-sample.php

README.md

WordPress

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

Getting Started

WordPress is a PHP/MySQL-based project. We have a basic development environment that you can quickly get up and running with a few commands. First off, you will need to download and install Docker, if you don't have it already. After that, there are a few commands to run:

Development Environment Commands

Running these commands will start the development environment:

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

Additionally, npm run env:stop will stop the environment.

npm run env:cli runs the WP-CLI tool. 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.

npm run test:php and npm run test:e2e run the PHP and E2E test suites, respectively.