Skip to content

Latest commit

 

History

History
47 lines (32 loc) · 2.76 KB

CONTRIBUTING.md

File metadata and controls

47 lines (32 loc) · 2.76 KB
Raw

Contributing to Classic Commerce ✨

There are many ways to contribute to the Classic Commerce project!

  • Translating strings into your language.
  • Answering questions on GitHub Classic Commerce Issues Page.
  • Submitting fixes, improvements and enhancements through PRs.
  • Testing the development builds and filing issues

Classic Commerce is still growing and your help making it even more awesome will be greatly appreciated :)

If you think something can be improved and you wish to contribute code, fork Classic Commerce, commit your changes, and send a pull request. We'll be happy to review your changes!

Feature Requests

Feature requests can be submitted to our issue tracker. Be sure to include a description of the expected behavior and use case, and before submitting a request, please search for similar ones in the closed issues.

Feature request issues will remain closed until we see sufficient interest via comments and 👍 reactions from the community.

You can see a list of current feature requests which require votes here.

Technical Support / Questions

We currently offer technical support on GitHub so we recommend using the following:

Technical support, General usage and development questions If you have a problem, you may want to write an issue to the Classic Commerce GitHub Repo: https://github.com/ClassicPress-plugins/classic-commerce/issues

Submit a PR

Start by cloning this repo into your staging site plugins folder via the terminal or command prompt using:

  • Run git clone https://github.com/ClassicPress-plugins/classic-commerce
  • Run cd classic-commerce
  • Run composer install
  • Run npm install
  • Make a branch using git checkout -b short-title-to-your-changes
  • Run npm run build-watch or npm run build as you make changes. These fixes translation string changes in the .pot file, scripts and styles.
  • Push your PR commits and changes to the develop branch.

Testing the development builds

As we push the plugin to a better version of itself, testing the plugin is of great help. We recommend

  • A fresh installation of ClassicPress or WordPress
  • A fresh installation of Classic Commerce in your \wp-content\plugins folder
  • Activate the plugin and begin tests.