# Help wallabag

## Report bugs

### Contact wallabag support

If you have a problem while installation or using wallabag (either with the web application or the smartphone applications), use the support site http://support.wallabag.org.

We will look if we can do to help you promptly, or if it is an new bug that we will need to correct.

It is better to use the support site than sending us an email: the followup is easier for us and the solution to your problem may help another user.

### Create a new issue

If you find a bug during wallabag use, thanks for opening a new issue on Github (an account is required).

First of all, read the advices about the submission of a new issue. The better you report the issue, the more we will be able to help you.

- for a bug in the web application, open a new issue here
- for a bug in the Android application, open a new issue here
- for a bug in the Windows Phone application, open a new issue here
- for a bug in the iOS application , open a new issue here
- for a bug in the Firefox extension, open a new issue here
- for a bug in the Chrome extension, open a new issue here

## Write and fix documentation

The documentation you are reading is likely to miss some points, to be out-of-date, to require a translation in your language. Hence, we invite you to take part in its writing.

The Github repository is here: https://github.com/wallabag/documentation.

## Fix bugs

Two options:

- when a wallabag user asks a new question on the support site, you could answer him directly if you are a more advanced wallabag user.
- on Github, some issues are likely to match your skills. Go through the issue list and help yourself.

You are welcome to suggest changes to the wallabag code. Look at the advices about the submission of a new issue.

## Spread the word

It's not so complicated: just talk about wallabag! Use #wallabag hashtag on all your social networks: twitter, Facebook, Diaspora*, Google+, etc.

Here are our accounts on social networks:

- Diaspora*
- twitter
- Facebook
- Google+