diff options
| author | Nick Brassel <nick@tzarc.org> | 2024-05-30 12:00:41 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-30 12:00:41 +1000 |
| commit | 6ef97172889ccd5db376b2a9f8825489e24fdac4 (patch) | |
| tree | 334e3bf41c8554d4bee73a140822f95f60eb64e9 /docs/faq_general.md | |
| parent | 395766657ff98a4b1fd0dcba5917557f8acbb9e4 (diff) | |
Vitepress conversion of docs. (#23795)
Diffstat (limited to 'docs/faq_general.md')
| -rw-r--r-- | docs/faq_general.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/faq_general.md b/docs/faq_general.md index 56b150da29..69ef4efa17 100644 --- a/docs/faq_general.md +++ b/docs/faq_general.md | |||
| @@ -6,13 +6,13 @@ | |||
| 6 | 6 | ||
| 7 | ## I don't know where to start! | 7 | ## I don't know where to start! |
| 8 | 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. | 9 | If this is the case, then you should start with our [Newbs Guide](newbs). There is a lot of great info there, and that should cover everything you need to get started. |
| 10 | 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. | 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 | 12 | ||
| 13 | ## How can I flash the firmware I built? | 13 | ## How can I flash the firmware I built? |
| 14 | 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. | 15 | First, head to the [Compiling/Flashing FAQ Page](faq_build). There is a good deal of info there, and you'll find a bunch of solutions to common issues there. |
| 16 | 16 | ||
| 17 | ## What if I have an issue that isn't covered here? | 17 | ## What if I have an issue that isn't covered here? |
| 18 | 18 | ||
| @@ -26,9 +26,9 @@ Then please open an [issue](https://github.com/qmk/qmk_firmware/issues/new), and | |||
| 26 | 26 | ||
| 27 | ## But `git` and `GitHub` are intimidating! | 27 | ## But `git` and `GitHub` are intimidating! |
| 28 | 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. | 29 | Don't worry, we have some pretty nice [Guidelines](newbs_git_best_practices) on how to start using `git` and GitHub to make things easier to develop. |
| 30 | 30 | ||
| 31 | Additionally, you can find additional `git` and GitHub related links [here](newbs_learn_more_resources.md). | 31 | Additionally, you can find additional `git` and GitHub related links [here](newbs_learn_more_resources). |
| 32 | 32 | ||
| 33 | ## I have a Keyboard that I want to add support for | 33 | ## I have a Keyboard that I want to add support for |
| 34 | 34 | ||
| @@ -46,7 +46,7 @@ If you have any questions about this, open an issue or head to [Discord](https:/ | |||
| 46 | 46 | ||
| 47 | TMK was originally designed and implemented by [Jun Wako](https://github.com/tmk). QMK started as [Jack Humbert](https://github.com/jackhumbert)'s fork of TMK for the Planck. After a while Jack's fork had diverged quite a bit from TMK, and in 2015 Jack decided to rename his fork to QMK. | 47 | TMK was originally designed and implemented by [Jun Wako](https://github.com/tmk). QMK started as [Jack Humbert](https://github.com/jackhumbert)'s fork of TMK for the Planck. After a while Jack's fork had diverged quite a bit from TMK, and in 2015 Jack decided to rename his fork to QMK. |
| 48 | 48 | ||
| 49 | From a technical standpoint QMK builds upon TMK by adding several new features. Most notably QMK has expanded the number of available keycodes and uses these to implement advanced features like `S()`, `LCTL()`, and `MO()`. You can see a complete list of these keycodes in [Keycodes](keycodes.md). | 49 | From a technical standpoint QMK builds upon TMK by adding several new features. Most notably QMK has expanded the number of available keycodes and uses these to implement advanced features like `S()`, `LCTL()`, and `MO()`. You can see a complete list of these keycodes in [Keycodes](keycodes). |
| 50 | 50 | ||
| 51 | From a project and community management standpoint TMK maintains all the officially supported keyboards by himself, with a bit of community support. Separate community maintained forks exist or can be created for other keyboards. Only a few keymaps are provided by default, so users typically don't share keymaps with each other. QMK encourages sharing of both keyboards and keymaps through a centrally managed repository, accepting all pull requests that follow the quality standards. These are mostly community maintained, but the QMK team also helps when necessary. | 51 | From a project and community management standpoint TMK maintains all the officially supported keyboards by himself, with a bit of community support. Separate community maintained forks exist or can be created for other keyboards. Only a few keymaps are provided by default, so users typically don't share keymaps with each other. QMK encourages sharing of both keyboards and keymaps through a centrally managed repository, accepting all pull requests that follow the quality standards. These are mostly community maintained, but the QMK team also helps when necessary. |
| 52 | 52 | ||
