Format section templates and PR template accordingly

.github/pull_request_template.md

@@ -1,10 +1,8 @@
 ### What this PR does / why we need it
 
-<!-- Please mention any GitHub issue, set a descriptive PR title, and use this space for additional explanations. -->
+<!-- Reference a GitHub issue, set a descriptive PR title, and use this space for additional explanations. -->
 
 ### Things to check/remember before submitting
 
-- If you made content changes
-
-    - Run `make lint dev` to render and proofread content changes locally.
-    - Bump `last_review_date` in the front matter header if you reviewed the entire page.
+- If it's one of your first contributions, make sure you've read the [Contributing Guidelines](https://handbook.giantswarm.io/docs/content/docs-guide).
+- Bump `last_review_date` in the front matter header of the pages you've touched.

src/content/getting-started/_template.md.tpl

@@ -9,7 +9,7 @@ user_questions:
   - List of questions that users might ask about this topic.
 ---
 
-Today, the `getting started` pages are about guiding a new user or platform engineer to build their platform with Giant Swarm. The articles are ordered to be followed one after the other to show all the features we offer from the suffice. If you want to go deeper into the topics, we have tutorials or reference pages for that purpose. Here is just an introduction.
+Today, the `getting started` pages are about guiding a new user or platform engineer to build their platform with Giant Swarm. The articles are ordered to be followed one after the other to show all the features we offer from the suffice. Also, read the [contributing guideline](https://handbook.giantswarm.io/docs/content/docs-guide) before writing the content.
 
 Recommended sections can help you to start with the article:
 

src/content/overview/_template.md.tpl

@@ -9,7 +9,7 @@ user_questions:
   - List of questions that users might ask about this topic.
 ---
 
-Could you describe the area topic from an overview point of view? Don`t go too deep into the matter; we have tutorials or reference pages for that purpose. Here is just an introduction.
+Could you describe the area topic from an overview point of view? Don`t go too deep into the matter; use tutorials or reference pages for technical content. Here we explain our product for a high level person. Also, read the [contributing guideline](https://handbook.giantswarm.io/docs/content/docs-guide) before writing the content.
 
 Here, you can write an intro paragraph that responds to the question, "What do we mean by `TOPIC_TO_DEVELOP`"
 

src/content/tutorials/_template.md.tpl

@@ -0,0 +1,30 @@
+---
+title: Short title for this page, it is shown as title in upper section and menu
+description: At least 70 characters that describe the purpose of this page.
+weight: from 10 to 100. Lower is higher in the menu.
+last_review_date: 2025-01-01
+owner:
+  - https://github.com/orgs/giantswarm/teams/${OWNER}
+user_questions:
+  - List of questions that users might ask about this topic.
+---
+
+Today, the `tutorials` represent the content for advanced users which needs some guidance to accomplish or learn about certain topics. We recommend to create an outline of the tutorial before writing the content.
+
+Some sections that can be included in a tutorial are:
+
+## Introduction (dont need this title)
+
+General description of the goal you want to achieve. It should be a brief explanation of what the user will learn in this tutorial.
+
+## Requirements
+
+Indicate the prerequisites that the user must have to follow the tutorial. For example, a specific version of the software, a specific configuration, or a specific environment.
+
+## Steps or Process (H2 section title)
+
+Describe the steps or process that the user must follow to achieve or learn about the matter. Follow the [contributing guidelines](https://handbook.giantswarm.io/docs/content/docs-guide) to write the content.
+
+## Next steps or Follow-up
+
+Internal or external links to other tutorials or resources that the user can follow to continue learning about the topic.