|
| 1 | +## Information |
| 2 | + |
| 3 | +This repository is for a WIP EmuDeck Wiki using MkDocs: [https://www.mkdocs.org/](https://www.mkdocs.org/) |
| 4 | + |
| 5 | +The theme is mkdocs-material: [https://github.com/squidfunk/mkdocs-material](https://github.com/squidfunk/mkdocs-material) |
| 6 | + |
| 7 | +The EmuDeck Wiki Website: [emudeck.github.io](https://emudeck.github.io/) |
| 8 | + |
| 9 | +This **repository** is not for the EmuDeck application, you can find that here: [https://github.com/dragoonDorise/EmuDeck/issues](https://github.com/dragoonDorise/EmuDeck/issues). If you are having any issues with the EmuDeck application, emulators or tools, use the EmuDeck Discord for support. If you have any feedback on the EmuDeck application, open an issue on the aforementioned repository. |
| 10 | + |
| 11 | +## How to Contribute |
| 12 | + |
| 13 | +You can contribute to the EmuDeck Wiki in a couple of ways. |
| 14 | + |
| 15 | +### Option 1: A quick shout-out |
| 16 | + |
| 17 | +Send a quick message on EmuDeck's Discord stating what needs to be edited or added. |
| 18 | + |
| 19 | +[EmuDeck Discord Link](https://discord.gg/b9F7GpXtFP) |
| 20 | + |
| 21 | +### Option 2: Opening an Issue |
| 22 | + |
| 23 | +You will need to create a GitHub account to open an issue. |
| 24 | + |
| 25 | +Once you have created an account, you can visit this page: [https://github.com/EmuDeck/emudeck.github.io/issues](https://github.com/EmuDeck/emudeck.github.io/issues) and submit an issue. |
| 26 | + |
| 27 | +### Option 3: Editing the Markdown files |
| 28 | + |
| 29 | +You will need to create a GitHub account to open a Pull Request. |
| 30 | + |
| 31 | +Markdown is a fairly straightforward markup language. If you are not familiar, you can take a quick look at the documents in the `docs` folder. |
| 32 | + |
| 33 | +Depending on your comfort level with GitHub, you can either use GitHub's web editor to edit any markdown files or you may also clone the repository and edit the markdown files that way. |
| 34 | + |
| 35 | +To edit markdown files in GitHub's web editor, open a document in the `docs` folder, and click the small pencil icon in the top right. Once you are finished, click `Commit changes..`. GitHub will prompt you to open a Pull Request, which will then be merged once it is reviewed. |
| 36 | + |
| 37 | +Once the PR is merged and reviewed, your changes will automatically be deployed to the website. |
| 38 | + |
| 39 | +If you do choose to clone the repository, you only need to clone the `main` branch. |
| 40 | + |
| 41 | +Depending on your permission level, when you are finished making edits, either push your changes to `main` or create a Pull Request. Any changes you make to the markdown files will automatically be pushed to the `gh-pages` branch and deployed to the website once you have either pushed your changes to `main` or your Pull Request is approved and merged. |
| 42 | + |
| 43 | +*** |
| 44 | + |
| 45 | +Thank you for contributing! |
0 commit comments