Updated Home (markdown)

Steph Piper 2024-12-01 12:04:26 +10:00
commit be147fc15d

@ -8,7 +8,7 @@ This wiki is a guide on how to contribute to the project through bug requests, n
* Third, the template is polished by an admin with icons added and added as a final, downloadable, printable PDF file.
* Fourth, translations can be created by uploading the original .svg file to the [Skill Tree Generator](https://schme16.github.io/MakerSkillTree-Generator/) and submitting translations as an .svg file as an issue or pull request.
Using this workflow it avoids re-translating skill trees that are not polished or reviewed by other experts. This system was not implemented from the start and you may find translated works that are not up to date with the final file in the repository that need re-translation. Bug fixes are accepted at any stage in the process. You can check the progress of each tree in the table in the Readme on the front page.
Using this workflow it avoids re-translating skill trees that are not polished or reviewed by other experts. This system was not implemented from the start and you may find translated works that are not up to date with the final file in the repository that need re-translation. You might also find some skill areas that do not yet have an SVG file compatible with the Skill Tree Generator and I am working on adding these, and they can also be submitted. Bug fixes are accepted at any stage in the process. You can check the progress of each tree in the table in the Readme on the front page.
# How to Create a New Skill Tree
@ -69,7 +69,8 @@ Peer reviewers must be an expert in the skill area and contribute detailed feedb
* Weaker tiles that could be swapped for stronger tiles
* If a skill tree is broad in topic, it is fine for it to have tiles that are in duplicate to subdisciplines in that topic. For example, if both the Sports & Fitness and Running Skill trees have a 'Run 2kms' tile, this is fine.
If a skill tree has been peer reviewed twice, it is now ready for translation and indicates a high level of confidence in the content. Peer reviewers may contribute this feedback as an issue in Github with 'Peer review' in the title, and can receive a contributor sticker in the mail if they wish by completing the bug feedback form above.
Peer reviewers may contribute this feedback as an issue or pull request with a fixed .svg in Github with 'Peer review' in the title. Peer reviewers can receive a contributor sticker in the mail if they wish. If a skill tree has been peer reviewed twice, it is now ready for translation and indicates a high level of confidence in the content.
# How to Translate a Skill Tree
Translators may contribute translations by uploading the .svg file to the [Skill Tree Generator](https://schme16.github.io/MakerSkillTree-Generator/). , translating the tiles, downloading the .svg file and submitting as an issue or pull request in Github with 'Translation to [Insert Language]' in the title. Translators can receive a contributor sticker in the mail if they wish.