6d2eec1c12
* Move section, header, and activity panel out of layout folder * Update file soures * Move documentation into component, and update generation script to handle the duplicated exports |
||
|---|---|---|
| .. | ||
| bin | ||
| client | ||
| docs | ||
| images | ||
| includes | ||
| languages | ||
| lib | ||
| tests | ||
| .babelrc | ||
| .browserslistrc | ||
| .distignore | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .travis.yml | ||
| Gruntfile.js | ||
| README.md | ||
| package-lock.json | ||
| package.json | ||
| phpcs.xml.dist | ||
| phpunit.xml.dist | ||
| postcss.config.js | ||
| wc-admin.php | ||
| webpack.config.js | ||
README.md
WooCommerce Admin
This is a feature plugin for a modern, javascript-driven WooCommerce Admin experience.
⚠️ This project is in active development, and is not ready for general use. You can follow the features in development by looking at the project's issues. We do not recommend running this on production sites.
Prerequisites
Gutenberg and WooCommerce should be installed prior to activating the WooCommerce Admin feature plugin.
For better debugging, it's also recommended you add define( 'SCRIPT_DEBUG', true ); to your wp-config. This will load the unminified version of all libraries, and specifically the development build of React.
Development
After cloning the repo, install dependencies with npm install. Now you can build the files using one of these commands:
npm run build: Build a production versionnpm start: Build a development version, watch files for changes
There are also some helper scripts:
npm run lint: Run eslint over the javascript filesnpm run i18n: Create a PHP file with the strings from the javascript files, used to get around lack of JS support in WordPress.org.