Find My BlocksDesign System
Components
ChangelogContributingSubmitting an IssueContibuting CodeDonations

Contributing

Submitting an Issue

Although I try very, very hard to keep this plugin bug-free. Sometimes thingss out of our control happen. There are 2 main ways that you can submit bugs to Find My Blocks.

Github:

Find My Blocks is an open source project, which means that anyone can readily see the code that powers the plugin. This code is hosted on a site called Github.

To submit an issue, click here and then the button labeled New Issue. Fill out the information asked for.

On the right hand side you will see an option to add a label. Use the label bug to report a bug or issue with the plugin, or use the label feature request to request some new functionality.

WordPress:

You can also report a bug or feature request through WordPress support topics.

To report a bug on WordPress please prefix your topic with BUG: and for a new feature or functionality, please prefix your topic with REQUEST:. This will help to prioritize what to work on next.

Contibuting Code

Are you a developer and would like to contribute to Find My Blocks? The process for contributing is quite simple.

  1. Follow the Readme to get set up.
  2. Indicate a bug or feature request that you would like to work on
    • If the bug or feature request is not in Github issues, please add it
  3. Fork Find My Blocks and make your changes.
    • If this is your first time contributing to an open source project, DigitalOcean has a great resource to help walk you through the steps.
  4. Submit a PR against Find My Blocks referencing the bug or feature request that you are working on.
  5. Once approved, I will merge into master.

Some notes about contributing

There are a few things that you should know before contributing to Find My Blocks

  1. Find My Blocks is written primarily in React and Typescript with a little bit of PHP used to handle the WordPress features.
  2. Linting and Testing are a must. Pull requests will not be approved if sufficient testing is not included.
  3. Documentation is important. All code submitted should be properly documented through docz or commented in code.