Tutorial: create first kata (#224)

* Migrated from old wiki

* Navigation

* Autoformat with Prettier

* Organization, navigation

* Navigation

* Organization

* Organization

* Organization

* Organization

* Fill in TODOs

* Add note on required honor

* Apply suggestions from code review

Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>

* Apply suggestions from code review

Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>

* Apply suggestions from code review

Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>

* Update content/authoring/kata/create-first-kata.md

Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>

* Apply suggestions from code review

Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>

* Apply suggestions from code review

Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>

* Remarks from code review

* Apply suggestions from code review

Co-authored-by: Steffan <40404519+Steffan153@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: kazk <kazk.dev@gmail.com>

* tone down the language a bit

* Apply suggestions from code review

Co-authored-by: Steffan <40404519+Steffan153@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: kazk <kazk.dev@gmail.com>
Co-authored-by: Steffan <40404519+Steffan153@users.noreply.github.com>
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>

* Apply suggestions from code review

Co-authored-by: kazk <kazk.dev@gmail.com>
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>

* Apply suggestions from code review

Co-authored-by: Steffan <40404519+Steffan153@users.noreply.github.com>

* Redo 'avoid duplicates'; hold back with approving translations

* formatting

* organization

Co-authored-by: hobovsky <hobovsky@users.noreply.github.com>
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>
Co-authored-by: Steffan <40404519+Steffan153@users.noreply.github.com>
Co-authored-by: kazk <kazk.dev@gmail.com>

Author: 4 people

content/authoring/index.md

@@ -5,38 +5,16 @@ next: /authoring/kata/
 
 # Authoring of Codewars Content
 
-## Overview
+All content available on Codewars is created by members of the Codewars community. It's ideas of Codewars users that get turned into kata, and the fact that users are familiar with plenty of programming languages allows for a large number of available translations.
 
-All content available on Codewars is created by members of the Codewars community. It's ideas of Codewars users that get turned into kata, and only the fact that users are familiar with plenty of programming languages allows for a large number of available translations.
+This section of the documentation is meant mostly for authors and translators who would like to introduce new challenges and make them available for other Codewars users. Creating a kata or translating it, even an easy one, is a difficult task. It requires a much wider set of skills compared to that of just solving a kata. Unlike problem solvers, authors need to master skills related to software development in general, as well as problem design, writing good test suites, documenting the task and its requirements, and communicating with reviewers.
 
-This section of the documentation is meant mostly for authors and translators, who would like to introduce new challenges and make them available for other Codewars users. Creating a kata or translating it, even an easy one, is a difficult task. It requires a much wider set of skills compared to the one required for just solving a kata. Unlike problem solvers, authors need to master skills related to software development in general, as well as to design of the problems, writing good test suites, documenting the task and its requirements, and communicating with reviewers. 
+To support users in creating good quality kata and translations, a set of help pages were created with articles related to content authoring activities: tutorials explaining how to create and translate a kata, and a reference of [guidelines][authoring-guidelines] and requirements that every author should follow to make sure that a piece of content created by them meets quality criteria.
 
-To support users in creating good quality kata and translations, a set of help pages were created with articles related to content authoring activities: tutorials explaining how to create and translate a kata, and a reference of [guidelines][guidelines-authoring] and requirements that every author should follow to make sure that a piece of content created by them meets quality criteria.
+For more details, see help pages related to creating a specific type of content:
+- [Creating a kata][authoring-kata]
+- [Creating a translation][authoring-translation]
 
-## Creating a Kata
-
-_TBD: improve this stub_
-
-Users new to creating kata can use [tutorial(TODO)](/authoring/kata/).
-
-Some [languages](/languages/) also have a page dedicated to creating a kata, with code examples and best practices.
-
-Every kata author should follow [kata authoring guidelines](/authoring/guidelines/kata/).
-
-After being published, every kata goes through the [beta process](/concepts/kata/beta-process/) and is subject to a series of [reviews](/curating/kata/).
-
-## Translating a Kata
-
-_TBD: improve this stub_
-
-New translators can use [tutorial(TODO)](/authoring/translation/).
-
-Some [languages](/languages/) also have a page dedicated to creating a kata, with code examples and best practices.
-
-Every translator should follow [translation authoring guidelines](/authoring/guidelines/translation/).
-
-After being published, every translation goes through a series of [reviews](/curating/translation/) before it can be approved.
-
-
-[guidelines-authoring]: /authoring/guidelines/
-[docs-curating]: /curating/
+[authoring-guidelines]: /authoring/guidelines/
+[authoring-kata]: /authoring/kata/
+[authoring-translation]: /authoring/translation/

content/authoring/kata/create-first-kata.md

@@ -1,12 +1,30 @@
 ---
-kind: tutorial
 sidebar: authoring
 next: /authoring/
 prev: /authoring/translation/
 ---
 
-# How to create a kata
+# Kata
 
-_This page is a stub._
+_TBD: improve this stub_
 
+## Requirements
 
+To create a new kata, a user needs to earn the ["Create Kata" privilege][reference-privileges]. After reaching the required amount of Honor, the privilege is granted and the user can select the **"New Kata"** option from their profile menu.
+
+
+## Kata Editor
+
+Kata are created with the [kata editor](/references/ui/kata-editor/)
+
+Users new to creating kata may refer to the [tutorial(TODO)](/authoring/kata/).
+
+Some [languages](/languages/) also have a page dedicated to authoring kata, with code examples and best practices.
+
+Every kata author should follow [kata authoring guidelines](/authoring/guidelines/kata/).
+
+After being published, every kata goes through the [beta process](/concepts/kata/beta-process/) and is subject to a series of [reviews](/curating/kata/).
+
+
+[reference-privileges]: /references/gamification/privileges/
+[docs-curating]: /curating/

content/authoring/kata/img/new_kata-dark.png

@@ -1,13 +1,20 @@
 ---
-kind: tutorial
 sidebar: authoring
 prev: /authoring/kata/
 next: /authoring/guidelines/
 ---
 
-# How to translate a kata
+# Translations
 
-_TBD: this page was imported from the old CW wiki and needs to be reviewed/redacted._
+_TBD: improve this stub_
+
+New translators may refer to the [tutorial(TODO)](/authoring/translation/).
+
+Some [languages](/languages/) also have a page dedicated to authoring kata, with code examples and best practices.
+
+Every translator should follow [translation authoring guidelines](/authoring/guidelines/translation/).
+
+After being published, every translation goes through a series of [reviews](/curating/translation/) before it can be approved.
 
 <!--
 TODO: this page would relate to creating both initial language version, as well as new translation

content/authoring/kata/img/new_kata-light.png

@@ -13,62 +13,4 @@ next: /references/ui/kata-trainer/
 
 ## What is the Kata Editor?
 
-The Kata Editor is the authoring tool used to create and modify kata. It is accessible through the profile menu, found in the top right corner of this site. Only users who have earned the [[Create Kata|Privileges]] privilege.
-
-## Anatomy of a Kata
-
-In order to create a kata you must first understand the elements of a kata.
-
-### Name
-
-The name is used to uniquely identify a kata. You can be creative with the name that you use. Best practice is to use a name that gives other users a good idea of what type of challenge they will be getting themselves into.
-
-### Discipline
-
-The discipline is the category that the kata belongs to. You should pick the category that best describes what the kata is intended to focus on. As of now there are four categories
-
-- Reference - Focuses on core language and API knowledge.
-- Algorithm - Focuses on the logic required to complete the task.
-- Bug Fix - Focuses on taking existing code, determining the issue and fixing it.
-- Refactor - Focuses on taking existing code and making it better.
-
-### Description
-
-The description field is used to provide instructions to the users who will be training on the kata. This field recognizes [[Github/Codewars flavored markdown|Markdown-Formatting]]. You can use the preview tab to see the markdown.
-
-For complex katas you may need to create a lengthy description in order to fully describe the requirements. For easier katas it is best to keep the description as short and concise as possible. Feel free to use code block examples within the description. It is always best to use the three back tick (```) code block style instead of indentation.
-
-### Describing code examples for multiple languages
-
-The markdown we provide adds an additional feature useful for displaying code blocks of multiple languages. If you use the ``` [language name] markdown format for indicating which code syntax should be used then you can define all of the languages examples within the description field. When your markdown is displayed it will filter out the languages that are not relevant (based off of the current context). In order for this to work you must use the language's full name and have your examples grouped together without any additional content in between them.
-
-The following is an example of how to provide example code blocks for both javascript and coffeescript:
-
-~~~
-```javascript
-var a = []
-```
-```coffeescript
-a = []
-```
-~~~
-
-### Final Solution
-
-When creating your kata you will probably want to start with the final solution and test fixture code blocks. If you are used to TDD then you will write your tests within the test fixture and then you will create a fully working solution within the final solution code block. If you need to load some preloaded code then you may need to do that before working on the final solution code block.
-
-### Initial Solution
-
-After you have a working solution then you will want to next focus on getting the code setup for how other users will initially see it. The way in which you setup your initial solution code will depend heavily on the discipline that you have selected. For bug and refactor disciplines you will end up needing to include almost working or already fully working code within this block. For reference and algorithm disciplines you will likely only include skeleton code. Perhaps an empty function/method called "solution" or some other code that has missing code that needs to be completed. Sometimes you may just want to include some comments to help get the user started, but no actual code.
-
-The initial solution block is required so you will have to include something (at the very least some comments) in order for the kata to be able to be published.
-
-### Preloaded
-
-The preloaded code block is an optional feature that you can use if you need it. Its useful for when you want to load some code that mimics an API that your kata is based around. Its also useful if you want to define some code that needs to be used within the solution, but shouldn't be editable within the solution itself. For example maybe you want to create a kata that asks a user to add an item to an array. It would be better to define the array within the preloaded code block so that the user already has the array created for them, and will be more likely to just add an item to the array using the appropriate array method, instead of updating the array constructor to include the value (and bypassing using an array method all together).
-
-### Test Fixture
-
-The test fixture is used to write code that will validate the kata solution.
-The entire set of code in this block acts as a single test case. To validate solution code
-you can use the Test.expect(passed_boolean, optional_message) method. More advanced testing methods are also available. Check out the kata test framework documentation for more information.
+The Kata Editor is the authoring tool used to create and modify kata. It is accessible through the profile menu found in the top right corner of this site. Only users who have earned the [[Create Kata|Privileges]] privilege may access the Kata Editor.

content/authoring/kata/index.md

@@ -127,6 +127,10 @@ module.exports = {
               "/authoring/guidelines/kata/",
             ],
           },
+          {
+            title: "Tutorials",
+            items: ["/authoring/kata/create-first-kata/"],
+          },
         ],
       },
       {