# Contributing to Light Blue Your contributions are welcome and are greatly appreciated! Every little bit helps, and credit will always be given. Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved. ## Conduct Please, follow the [golden rule](https://en.wikipedia.org/wiki/Golden_Rule). Be respectful, even to those that are disrespectful. ## Feedback Feedback is the breakfast for champions! We'd love to hear your opinions, discuss potential improvements, architecture, theory, internal implementation, etc. Please, join or start a new conversation in our [issue tracker](https://github.com/flatlogic/light-blue-dashboard/issues). ## Documentation We need your help with improving documentation to the project. This might be the easiest way for you to contribute, because you don't even need to clone the repo but can edit or create new `.md` files right from GitHub website as described [here](https://help.github.com/articles/editing-files-in-your-repository/). ## Bugs & Feature Requests Before opening an issue, please: * Check [Documentation](https://demo.flatlogic.com/sing-app/documentation). * Search the [issue tracker](https://github.com/flatlogic/light-blue-dashboard/issues) to make sure your issue hasn’t already been reported. * If your issue sounds more like a question, please post it on StackOverflow.com instead with the tag [light-blue-dashboard](http://stackoverflow.com/questions/tagged/light-blue-dashboard). ## Pull Requests Before you submit a [pull request](https://help.github.com/articles/using-pull-requests/) from your forked repo, check that it meets these guidelines: * If the pull request adds functionality, the docs should be updated as part of the same PR. * Create a separate PR for each small feature or bug fix. * [Squash](http://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git) your commits into one for each PR. * When contributing to an opt-in feature, apply the `[feature/...]` tag as a prefix to your PR title ## Style Guide We follow [Airbnb's Style Guide](https://github.com/airbnb/javascript) for best practices writing javascript code. ## Commit Message Guidelines We have very precise rules over how our git commit messages can be formatted. This leads to **more readable messages** that are easy to follow when looking through the **project history**. But also, we use the git commit messages to **generate the ngx-admin change log**. ### Commit Message Format Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**: ``` ():