[FEATURE] Expanded contribution guides (#7)

Adds information specific to the GitHub tooling, such as linking and where to place image files. Also corrects some formatting. Also introduces the `00Incoming` folder for guides without a known place in the structure.

Author: mabolek

Documentation/00Incoming/Index.md

@@ -0,0 +1,3 @@
+# New guides without a place in the structure
+
+If you're writing a step-by-step guide and don't yet know where to place it in the structure, feel free to put the file here, within the `00Incoming` folder. Reviewers will look at your guide and find a place for it before it is merged into the guides.

Documentation/90Contribute/10Template/Index.md

@@ -2,67 +2,70 @@
 
 *This template includes writing instructions {in curly brackets} and boilerplate text that you can customize with your own text. The [step-by-step Contributor Guide](../20ContributorGuide/Index.md) explains each section in detail, and includes example text for each section. Search the [Guide Registry](../../80GuidesRegistry/Index.md) before you start - your guide might already exist!*
 
+{The template includes an HTML comment with different tags for categorization (look in the source code). Include the ones you think fits and feel free to add new ones. A tag like #TYPO3v13 indicates that the step-by-step guide has been tested in TYPO3 v13. To credit yourself as author, use "@" followed by your my.typo3.org username (e.g. "@username").}
+<!-- #TYPO3v00 #Beginner #Intermediary #Advanced #ContentElements #Frontend #Backend #Templating #Server #Editing #Configuration @username -->
+
 ## Title
 
-{Provide a conceptual overview.}  
-   
-{Feature} enables you to {address pain point}. {Task you are going to learn} helps you {achieve goal}.  
+{Provide a conceptual overview.}
+
+{Feature} enables you to {address pain point}. {Task you are going to learn} helps you {achieve goal}.
 
 ## Learning objective
 
-In this step-by-step guide you will {describe what the learner will accomplish}. 
+In this step-by-step guide you will {describe what the learner will accomplish}.
 
 ## Prerequisites
 
 ### Tools and technology
 
-* {Hardware specifications}  
-* {Software installed}  
-* {Environments} 
+* {Hardware specifications}
+* {Software installed}
+* {Environments}
 
 ### Knowledge and skills
 
-* {Conceptual knowledge}  
+* {Conceptual knowledge}
 * {Prior learning}
 
 ## Watch the video
 
-{**Optional**. If available, embed the YouTube video version of this tutorial from the TYPO3 official channel.}    
-   
+{**Optional**. If available, embed the YouTube video version of this tutorial from the TYPO3 official channel.}
+
 Watch this video to follow along with the steps below.
 
 ## {Task name}
 
 >  **Scope check time**
 >
 > Don't start writing until you have a clear scope.
-> 
-> If you're unsure about the goal, the audience, or the prerequisites — go back and fix it now. Writing the task section without a solid scope will lead to frustration when you’re deep 
+>
+> If you're unsure about the goal, the audience, or the prerequisites — go back and fix it now. Writing the task section without a solid scope will lead to frustration when you’re deep
 > in the details.
 
 {Optional explanatory text}
 
-1. {Write the first step. Start with a verb.}  
-   {Optional: Code sample or screenshot that helps the learner complete this step.}  
-   {Optional: Expected outcome.}  
+1. {Write the first step. Start with a verb.}
+   {Optional: Code sample or screenshot that helps the learner complete this step.}
+   {Optional: Expected outcome.}
 2. {Write the next step. Start with a verb.}
 
 ## {Task name}
 
 {Optional explanatory text}
 
-1. {Write the first step. Start with a verb.}  
-   {Optional: Code sample or screenshot that helps the learner complete this step.}  
-   {Optional: Expected outcome.}  
+1. {Write the first step. Start with a verb.}
+   {Optional: Code sample or screenshot that helps the learner complete this step.}
+   {Optional: Expected outcome.}
 2. {Write the next step. Start with a verb.}
 
 ## {Task name}
 
 {Optional explanatory text}
 
-1. {Write the first step. Start with a verb.}  
-   {Optional: Code sample or screenshot that helps the learner complete this step.}  
-   {Optional: Expected outcome.}  
+1. {Write the first step. Start with a verb.}
+   {Optional: Code sample or screenshot that helps the learner complete this step.}
+   {Optional: Expected outcome.}
 2. {Write the next step. Start with a verb.}
 
 {For Project guides, use this section to link to existing step-by-step guides}
@@ -71,22 +74,22 @@ Watch this video to follow along with the steps below.
 
 {State the outcome of the step-by-step guide to recap what the learner has achieved.}
 
-Congratulations! You now have {outcome}. 
+Congratulations! You now have {outcome}.
 
 ## Next steps
 
 {List links to tasks that the learner could do next.}:
 
 Now that you have {achieved goal}, you might like to:
 
-* Task 1  
-* Task 2  
+* Task 1
+* Task 2
 * Task 3…
 
 ## Resources
 
 {**Optional**. List links to related material.}
 
-* Resource 1  
-* Resource 2  
-* Resource 3…
+* Resource 1
+* Resource 2
+* Resource 3…

Documentation/90Contribute/20ContributorGuide/10WhatAreSBSGuides.md

@@ -0,0 +1,35 @@
+# What are step-by-step guides?
+
+TYPO3 step-by-step guides are hands-on tutorials designed to help newcomers **accomplish one practical task**.
+
+Inspired by the [Diátaxis framework](https://diataxis.fr/map/#expectations-and-guidance), which emphasizes distinct content types in technical documentation, step-by-step guides map to the *tutorials* category.
+
+TYPO3 step-by-step guides follow a few key principles:
+
+* **Hands-on learning**: The fastest way to learn is by doing.
+* **One clear path**: No branches — just one method that works, from start to finish.
+* **Minimal explanation**: Explain only what’s necessary to keep someone moving. Link out for deeper context.
+* **A successful finish**: Every step produces visible progress, and the outcome is reliable and repeatable.
+* **Aligned with TYPO3’s official documentation**: Linking out to deeper material as needed.
+* Takes **less than 30 minutes** to complete
+
+> [!TIP]
+> A good step-by-step guide follows the [single-responsibility principle (SRP)](https://en.wikipedia.org/wiki/Single-responsibility_principle): **it should do one thing, and do it well.** > Every step contributes directly to a single learning objective, and nothing more.
+>
+> If you find yourself adding “If…” or “Alternatively…”, your guide may violate the single-responsibility principle.
+
+## What are they not?
+
+Step-by-step guides aren’t examples. Examples are usually found in the documentation, and help to illustrate concepts — they are meant to be studied and understood. Step-by-step guides, in contrast, take the reader through a path of sequential steps, and are designed to be actively followed to learn a new concept.
+
+## Modular by design
+
+Step-by-step guides are modular. Each guide is an atomic unit of action — small, focused, and self-contained, with one learning objective and one clear outcome. Guides can be combined to form larger tutorials or workshops, or used independently for self-led learning.
+
+## How do step-by-step guides fit in the existing TYPO3 documentation ecosystem?
+
+| TYPO3 documentation                                                                                            | Step-by-step guide                                                                                                   |
+|:---------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------|
+| **Information oriented** Supports exploration and problem-solving for people seeking answers or understanding. | **Learning oriented** Helps people learn through hands-on experience.                                                |
+| **Comprehensive** Presents various approaches, configurations, and possibilities. Also covers edge cases.      | **Single clear path** Follows a carefully managed path from start to finish with guaranteed success.                 |
+| **Blends doing and explaining** Combines how-to instructions, explanations, and reference information.         | **Focused on doing** Prioritizes action with minimal explanation. Links out to deeper material in the documentation. |

Documentation/90Contribute/20ContributorGuide/10WhatAreStepByStepGuides.md

@@ -1,29 +1,29 @@
 # What are project guides?
 
-A project guide is made up of multiple step-by-step guides. 
+A project guide is made up of multiple step-by-step guides.
 
 Project guides help learners complete multi-part processes by combining individual tasks into a coherent whole. They provide a clear learning sequence and maintain a narrative that shows how the parts fit together.
 
 ## How project guides extend step-by-step guides
 
-Project guides compose several atomic step-by-step guides into a larger or more advanced outcome. 
+Project guides compose several atomic step-by-step guides into a larger or more advanced outcome.
 
-Use a project guide when: 
+Use a project guide when:
 
-* Multiple distinct tasks are required  
-* Some tasks are already covered in other guides  
+* Multiple distinct tasks are required
+* Some tasks are already covered in other guides
 * It would take more than 30 minutes or feel overwhelming as one block
 
 **Examples**
 
-* Build a multilingual site  
+* Build a multilingual site
 * Develop a custom frontend plugin with user authentication
 
 ## Project guides are modular
 
 Project guides follow the same template as regular step-by-step guides, the only difference is that the Task section looks a bit different.
 
-Project guides are **fully modular**. They are made entirely by linking out to existing step-by-step guides, like ingredients in a recipe.
+Project guides are *fully modular*. They are made entirely by linking out to existing step-by-step guides, like ingredients in a recipe.
 
 You should only create a project guide once all the step-by-step guides it depends on have been created. This helps avoid incomplete or blocked project guides.