diff options
author | skullY <skullydazed@gmail.com> | 2020-03-01 08:57:26 -0800 |
---|---|---|
committer | skullydazed <skullydazed@users.noreply.github.com> | 2020-03-05 16:00:10 -0800 |
commit | 961477c791195ebf2d4c1f533807cb46c194d939 (patch) | |
tree | fbea653155e884505beedddc10a6003622fb6228 /docs/support.md | |
parent | 6956784ac1ae1a48e42ca0a695b7c666abd52846 (diff) | |
download | qmk_firmware-961477c791195ebf2d4c1f533807cb46c194d939.tar.gz qmk_firmware-961477c791195ebf2d4c1f533807cb46c194d939.zip |
make sure all our redirects are in order
Diffstat (limited to 'docs/support.md')
-rw-r--r-- | docs/support.md | 44 |
1 files changed, 9 insertions, 35 deletions
diff --git a/docs/support.md b/docs/support.md index d960992c3..79c1dbc1b 100644 --- a/docs/support.md +++ b/docs/support.md | |||
@@ -1,43 +1,17 @@ | |||
1 | # Support | 1 | # Getting Help |
2 | 2 | ||
3 | If you need help with something, the best place to get quick support is going to be on our [Discord Server](https://discord.gg/Uq7gcHh). There is usually somebody online, and there are a bunch of very helpful people there. | 3 | There are a lot of resources for getting help with QMK. |
4 | |||
5 | Don't forget to read our [Code of Conduct](https://qmk.fm/coc/). | ||
6 | |||
7 | ## Help! I don't know where to start! | ||
8 | |||
9 | If this is the case, then you should start with our [Newbs Guide](newbs.md). There is a lot of great info there, and that should cover everything you need to get started. | ||
10 | |||
11 | If that's an issue, hop onto the [QMK Configurator](https://config.qmk.fm), as that will handle a majority of what you need there. | ||
12 | |||
13 | ## Help! I'm having issues flashing! | ||
14 | |||
15 | First, head to the [Compiling/Flashing FAQ Page](faq_build.md). There is a good deal of info there, and you'll find a bunch of solutions to common issues there. | ||
16 | |||
17 | ## Help, I have an issue that isn't covered by the links above | ||
18 | 4 | ||
19 | Okay, that's fine. Then please check the [open issues in our GitHub](https://github.com/qmk/qmk_firmware/issues) to see if somebody is experiencing the same thing (make sure it's not just similar, but actually the same). | 5 | Please read our [Code of Conduct](https://qmk.fm/coc/) before participating in any of our community spaces. |
20 | 6 | ||
21 | If you can't find anything, then please open a [new issue](https://github.com/qmk/qmk_firmware/issues/new)! | 7 | ## Realtime Chat |
22 | 8 | ||
23 | ## What if I found a bug? | 9 | If you need help with something, the best place to get quick support is going to be on our [Discord Server](https://discord.gg/Uq7gcHh). There is usually somebody online, and there are a bunch of very helpful people there. |
24 | |||
25 | Then please open an [issue](https://github.com/qmk/qmk_firmware/issues/new), and if you know how to fix it, open up a Pull Request on GitHub with the fix. | ||
26 | |||
27 | ## But `git` and `GitHub` are intimidating! | ||
28 | |||
29 | Don't worry, we have some pretty nice [Guidelines](newbs_git_best_practices.md) on how to start using `git` and GitHub to make things easier to develop. | ||
30 | |||
31 | Additionally, you can find additional `git` and GitHub related links [here](newbs_learn_more_resources.md). | ||
32 | |||
33 | ## I have a Keyboard that I want to add support for | ||
34 | |||
35 | Awesome! Open up a Pull Request for it. We'll review the code, and merge it! | ||
36 | 10 | ||
37 | ### What if I want to do brand it with `QMK`? | 11 | ## OLKB Subreddit |
38 | 12 | ||
39 | That's amazing! We would love to assist you with that! | 13 | The official QMK forum is [/r/olkb](https://reddit.com/r/olkb) on [reddit.com](https://reddit.com). |
40 | 14 | ||
41 | In fact, we have a [whole page](https://qmk.fm/powered/) dedicated to adding QMK Branding to your page and keyboard. This covers pretty much everything you need (knowledge and images) to officially support QMK. | 15 | ## Github Issues |
42 | 16 | ||
43 | If you have any questions about this, open an issue or head to [Discord](https://discord.gg/Uq7gcHh). | 17 | You can open an [issue on GitHub](https://github.com/qmk/qmk_firmware/issues). This is especially handy when your issue will require long-term discussion or debugging. |