learn: give meaningful titles to chapters

l-zeuch · l-zeuch · commit aabf0d87fc1a · 2024-09-25T12:12:12.000+02:00
Signed-off-by: Luca Zeuch &lt;l-zeuch@email.de&gt;
diff --git a/content/docs/reference/templates/functions.md b/content/docs/reference/templates/functions.md
@@ -2297,7 +2297,7 @@ Target: {{ .User }}
 Please see our [in-depth guide] in the learning resources for a full breakdown of this function and how to make good use
 of it.
 
-[in-depth guide]: /learn/beginner/inputs-1
+[in-depth guide]: /learn/beginner/command-arguments
 
 #### sdict
 
diff --git a/content/learn/beginner/command-arguments.md b/content/learn/beginner/command-arguments.md
@@ -1,5 +1,5 @@
 +++
-title = "Inputs 1"
+title = "Command Arguments"
 weight = 240
 +++
 
diff --git a/content/learn/beginner/conditional-branching.md b/content/learn/beginner/conditional-branching.md
@@ -1,5 +1,5 @@
 +++
-title = "Control Flow 1"
+title = "Conditional Branching"
 weight = 230
 +++
 
@@ -113,15 +113,17 @@ We provide the following comparison functions in custom commands:
 - `gt` (greater than `>`)
 - `ge` (greater than or equal to `>=`)
 
-These functions can only compare basic data types as introduced in [Data Types 1](/learn/beginner/datatypes-1). Strings
+These functions can only compare basic data types as introduced in [Variables and Data Types][dtypes]. Strings
 are compared on a byte-by-byte basis. Please refer to the [functions documentation](/docs/reference/templates/functions)
 for the syntax of these functions.
 
+[dtypes]: /learn/beginner/variables-and-data-types
+
 ## Blocks And Scope
 
-In [Data Types 1](/learn/beginner/datatypes-1), we introduced the concept of variables. Variables are used to store
-values and give them a name. In programming, variables have a _scope_, which defines where in the code the variable can
-be accessed. Think of each scope as a "container" for things inside it.
+In the previous chapter, we introduced the concept of variables. Variables are used to store values and give them a name.
+In programming, variables have a _scope_, which defines where in the code the variable can be accessed. Think of each
+scope as a "container" for things inside it.
 
 Often, you will want to have a variable available across multiple scopes. In custom commands, the variable is accessible
 in the scope in which it was defined, as well as all nested scopes within. Let us assume that we want to assign a
@@ -166,6 +168,39 @@ block of code.
 
 {{< /callout >}}
 
+## With Blocks
+
+Just like the `if` action, `with` runs a block of code if the given expression is truthy. The only difference is that
+`with` overwrites the dot `.` with the expression if it is truthy.
+
+For instance, the following program
+
+```yag
+{{ $msg := "I <3 the YAGPDB documentation!" }}
+{{ with reFind `\d+` $msg }}
+    pattern found in text; the dot {{ printf "%q" . }} contains the match
+{{ else }}
+    pattern did not match
+{{ end }}
+```
+
+outputs
+
+```text
+pattern found in text; the dot "3" contains the match
+```
+
+Note that the dot `.` has been set to `"3"`—the result of `reFind`. See if you can change the text stored in `$msg` so
+that the program hits the `else` branch instead.
+
+{{< callout context="caution" title="Warning" icon="outline/alert-triangle" >}}
+
+Be careful not to overuse `with` blocks, as they can make your code difficult to follow. In general, prefer using
+a normal `if` conditional and only use `with` if it improves readability; do not use it just to shorten code.
+
+{{< /callout >}}
+
+
 ## Exercises
 
 1. Write a Custom Command to determine if the number stored in a variable `$a` is even or odd and print `Number is Even`
diff --git a/content/learn/beginner/simple-responses.md b/content/learn/beginner/simple-responses.md
@@ -1,5 +1,5 @@
 +++
-title = "Outputs 1"
+title = "Simple Responses"
 weight = 210
 +++
 
diff --git a/content/learn/beginner/variables-and-data-types.md b/content/learn/beginner/variables-and-data-types.md
@@ -1,5 +1,5 @@
 +++
-title = "Data Types 1"
+title = "Variables and Data Types"
 weight = 220
 +++
 
diff --git a/content/learn/intermediate/embeds-and-messages.md b/content/learn/intermediate/embeds-and-messages.md
@@ -1,10 +1,10 @@
 +++
-title = "Outputs 2"
+title = "Embeds and Messages"
 weight = 310
 +++
 
-Until now, we have just used the [default response behavior](/learn/beginner/outputs-1) to make our custom commands
-respond with some text. This makes sense for quick mockups or relatively simple commands. However, this may be
+Until now, we have just used the [default response behavior](/learn/beginner/simple-responses) to make our custom
+commands respond with some text. This makes sense for quick mockups or relatively simple commands. However, this may be
 inconvenient or Not What You Want in some cases. In this chapter, we will explore how to send messages to different
 channels, edit existing messages, and send messages with embeds, vastly expanding your toolbox for creating complex
 custom command systems.
@@ -93,7 +93,7 @@ will return a structured object that can be sent as a message, as demonstrated i
 
 The `"title"` and `"description"` fields are self-explanatory---we can use Discord Markdown in the latter. The `"color"`
 field takes an integer color value, for which we can conveniently use hexadecimal formatting as mentioned in
-[Data Types 1](/learn/beginner/datatypes-1#integers), but it can also take a
+[Variables and Data Types](/learn/beginner/variables-and-data-types#integers), but it can also take a
 [decimal value](https://www.binaryhexconverter.com/hex-to-decimal-converter).
 
 The `"fields"` field is a list (more precisely a _slice_) of dictionaries, where each dictionary represents a field in
diff --git a/content/learn/intermediate/loops.md b/content/learn/intermediate/loops.md
@@ -1,10 +1,10 @@
 +++
-title = "Control Flow 2"
+title = "Loops"
 weight = 330
 +++
 
-In a previous chapter, we learned about [basic control flow](/learn/beginner/control-flow-1). In this chapter, we will
-discuss more advanced control flow actions: namely, `range`, `while`, and `with` actions.
+In a previous chapter, we learned about [conditional branching](/learn/beginner/conditional-branching).
+In this chapter, we will discuss more advanced control flow actions: namely, `range`, `while`, and `with` actions.
 
 ## Loop
 
@@ -262,35 +262,3 @@ In custom commands, we provide two actions to control the flow of loops: `{{ bre
 exits the loop prematurely, whereas `continue` skips the remainder of the current iteration and jumps to the next one.
 These can prove very useful to optimize your code for size and readability, with similar benefits to guard clauses with
 `{{ return }}` introduced in earlier chapters.
-
-## With Blocks
-
-Just like the `if` action, `with` runs a block of code if the given expression is truthy. The only difference is that
-`with` overwrites the dot `.` with the expression if it is truthy.
-
-For instance, the following program
-
-```yag
-{{ $msg := "I <3 the YAGPDB documentation!" }}
-{{ with reFind `\d+` $msg }}
-    pattern found in text; the dot {{ printf "%q" . }} contains the match
-{{ else }}
-    pattern did not match
-{{ end }}
-```
-
-outputs
-
-```text
-pattern found in text; the dot "3" contains the match
-```
-
-Note that the dot `.` has been set to `"3"`—the result of `reFind`. See if you can change the text stored in `$msg` so
-that the program hits the `else` branch instead.
-
-{{< callout context="caution" title="Warning" icon="outline/alert-triangle" >}}
-
-Be careful not to overuse `with` blocks, as they can make your code difficult to follow. In general, prefer using
-a normal `if` conditional and only use `with` if it improves readability; do not use it just to shorten code.
-
-{{< /callout >}}
diff --git a/content/learn/intermediate/maps-and-slices.md b/content/learn/intermediate/maps-and-slices.md
@@ -1,10 +1,10 @@
 +++
-title = "Data Types 2"
+title = "Maps and Slices"
 weight = 320
 +++
 
-When you first started this course, you learned about [primitive data types](/learn/beginner/datatypes-1). In the
-previous chapter we name-dropped two more types: "slice", and "sdict" ("map"), both without much elaboration.
+When you first started this course, you learned about [primitive data types](/learn/beginner/variables-and-data-types).
+In the previous chapter we name-dropped two more types: "slice", and "sdict" ("map"), both without much elaboration.
 In this chapter, we will explore these data types in more detail.
 
 ## Slices
diff --git a/layouts/index.html b/layouts/index.html
@@ -47,7 +47,7 @@ <h2 id="quick-links" class="text-center">Quick Links</h2>
 
         <div class="card-nav d-flex flex-column flex-sm-row">
           {{ $opts := dict
-            "title" "Tools & Utilities"
+            "title" "Tools :& Utilities"
             "icon" "outline/tools"
             "content" `
 - [Self-assignable roles](/docs/tools-and-utilities/self-assignable-roles/)
@@ -60,9 +60,9 @@ <h2 id="quick-links" class="text-center">Quick Links</h2>
             "title" "Learning Resources"
             "icon" "outline/book"
             "content" `
-- [Custom Commands: Outputs 1](/learn/beginner/outputs-1)
-- [Custom Commands: Control Flow 1](/learn/beginner/control-flow-1)
-- [Custom Commands: Inputs 1](/learn/beginner/inputs-1)
+- [Custom Commands: Simple Responses(/learn/beginner/simple-responses)
+- [Custom Commands: Conditional Branching](/learn/beginner/conditional-branching)
+- [Custom Commands: Command Arguments](/learn/beginner/command-arguments)
             ` }}
           {{ partial "inline/home-card.html" $opts }}
         </div>
