3. How to contribute

There are several way how you can contribute to Elliot For Water, and yes, you can contribute also if you are not a coder.
We have various area where your help is more then welcome!

Where you help is needed:

• code changes (new features, bug fixes, testing)
• translation
• testing on different devices
• spread on social networks (todo: add the template here)
• SEO analysis and tips
• improve content

Right now we decided to set some specific tasks in the Projects Board where we need more help on.

This is mostly because we are still a very small team and it would be impossible for us to manage lot of discussion and many different new code changes based on personal ideas.
Please go through the tasks in the Project board and check if there is anything that you would enjoy working on.

If you believe you have an awesome idea to improve the project and we didn't listed in the tasks board, open an issue, label it ideas and let's discuss it all together!

Your First Code Contribution

You can start by looking through these beginner and help-wanted issues:

Good first issues - issues which should only require a few lines of code, and a test or two.
Help wanted issues - issues which should be a bit more involved than beginner issues.

Bugs

Bugs are nasty and can take a lot of precious time to fix them. But they often allow us to learn deeper about a specific topic or area of our code.
If you would like to help out fixing some bugs, we would really appreciate that.
You can simply go in the issues and look for any issue with the label bug

Workflow

Please read our workflow to know how can you make your changes and send it to us in a way that we can merge them with the master version.

Code Styleguide

All JavaScript code is linted with Eslint and formatted with Prettier.

Prefer the object spread operator ({...anotherObj}) to Object.assign()

Place requires in the following order:

1. Built in Node Modules (such as path)
2. Local Modules (using relative paths)

All the Css are linted with Stylelint and formatted with Prettier.

To create a Css Module, simply call the css file with the component name and then use .module.css extension.
If there is not much of style, we include the style in the page or component it self.

Got stuck?

No problem, it happen to all of us and that's why a community is so valuable.
Open an early PR (write [WIP] in the PR name), label it help wanted and ask for help in the comments.
Is always easier to help out when there is something concrete to discuss on.

Want to help but don't feel ready just yet?

Open a discussion on our community forum and ask for help.

Want to work on something that is not in the Projects card?

Open an issue and let us know your idea.
Label your issue ideas and let's discuss together if we can make your wishes come true