Merge branch 'main' into MTA-5781

Author: bene2k1

changelog/march2025/2025-03-17-transactional-email-added-tem-scale-plan-is-live.mdx

@@ -0,0 +1,15 @@
+---
+title: TEM Scale Plan now available
+status: added
+date: 2025-03-17
+category: managed-services
+product: transactional-email
+---
+
+The new Scale Plan is now available, including 100K emails/month and a dedicated IP for optimal deliverability.
+
+Discover all the details in our [documentation](https://www.scaleway.com/en/docs/transactional-email/how-to/manage-tem-plans/).
+
+Explore it now in the [Scaleway console](https://console.scaleway.com/transactional-email/plans).
+
+

docs/TROUBLESHOOTING_TEMPLATE.mdx

@@ -0,0 +1,51 @@
+---
+meta: 
+  title: Title describing the PROBLEM (I cannot..., I am experiencing..., My resource..., I am unable to..., Resource not found, etc.)
+  description: Description for SEO and referencing purposes that complements the title
+content:
+  h1: Title describing the PROBLEM (I cannot..., I am experiencing..., My resource..., I am unable to..., Resource not found, etc.)
+  paragraph: Description for SEO and referencing purposes that complements the title
+tags: fail error troubleshooting help unable cannot
+dates:
+  validation: 2025-03-10
+  posted: 2025-03-10
+categories:
+  - XXXXX
+---
+
+## Problem
+
+A short explanation of the problem, including symptoms, error message/code, unexpected behavior, etc.
+
+<Message type="note">
+  If several problems are listed, use the following structure for the page:
+  ```
+  ## Problem 1
+  ### Cause
+  ### Solution
+
+  ## Problem 2
+  ### Cause
+  ### Solution
+
+  [...]
+
+  ## Going further
+  ```
+</Message>
+
+## Cause
+
+Explain the reason(s) why this error happened. A problem can have several causes, in this case, list every possible cause.
+
+## Possible solution
+
+List the possible solution(s) to solve the issue. It can be a list of items to check, a procedure, links to other documentation, etc.
+
+## Going further
+
+Provide links to documentation pages that may be useful if the issue has not been solved.
+
+If required, add a paragraph containing elements to provide the support with when creating a support ticket.
+
+<Macro id="troubleshooting-ticket">

macros/general/troubleshooting-ticket.mdx

@@ -0,0 +1,29 @@
+---
+macro: troubleshooting-ticket
+---
+
+If you still cannot solve your problem, [open a support ticket](/account/how-to/open-a-support-tickets/#writing-an-effective-subject-and-description), providing as many details as possible including the information below:
+    - Resource ID
+    - Resource name
+    - Date and time (timestamp)
+    - User-agent (SDK, client, console, etc.)
+    - Transaction ID (if possible)
+    - Log / trace of the error (if possible)
+    - Screenshots (using our secure [pastebin tool](https://privatebin.iliad.fr/))
+    - HTTP status code (if applicable)
+    - Request type (PUT, GET, etc., if applicable) 
+
+<Grid>
+<DefaultCard 
+  title="AI search"
+  description="Use our AI assistant to find solutions."
+  url="/ai-search/"
+  label="Ask AI"
+/>
+<DefaultCard 
+  title="FAQ"
+  description="Get general information on Scaleway products."
+  url="/faq/"
+  label="Read FAQ"
+/>
+</Grid>