Skip to content

Commit 688d864

Browse files
committed
All done
1 parent b52c333 commit 688d864

22 files changed

+537
-15
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,4 @@ data
99

1010
.DS_Store
1111
pages/platform/kubernetes-k8s/monitoring-gpu-application/images/gpu-app-demo-video.mov
12+
llm-config/

llm-config/config.json

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
{
2+
"runMidscene": {
3+
"model": "Qwen2.5-VL-72B-Instruct",
4+
"configuration": {
5+
"baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1",
6+
"cache": "1"
7+
}
8+
},
9+
"translateGuide": {
10+
"model": "Qwen3-32B",
11+
"configuration": {
12+
"baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1"
13+
},
14+
"maxTokens": 4000,
15+
"temperature": 0.2
16+
},
17+
"generateGuide": {
18+
"model": "Meta-Llama-3_3-70B-Instruct",
19+
"configuration": {
20+
"baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1"
21+
},
22+
"maxTokens": 5000,
23+
"temperature": 0.2,
24+
"topP": 1
25+
},
26+
"guideToPrompt": {
27+
"model": "Meta-Llama-3_3-70B-Instruct",
28+
"configuration": {
29+
"baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1"
30+
},
31+
"maxTokens": 5000,
32+
"temperature": 0.2
33+
}
34+
}
Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
**Technical Writing Task**
2+
3+
Act as a technical writer to create a comprehensive guide based on the provided steps. Ensure that the text is logical, clear, and concise, making it easily understandable for both technical and non-technical readers.
4+
5+
**Guide Requirements**
6+
7+
- Write the guide in the specified language: {{locale}}
8+
- Improve the text in terms of clarity, quality, and readability
9+
- Use footnotes to explain technical terms related to the computer domain
10+
- Adhere to industry standards for technical documentation
11+
- Ensure the guide is concise and easy to follow
12+
13+
**Guide Details**
14+
15+
- Guide name: {{scenario}}
16+
- Base URL: {{base_url}} (to be mentioned in the first step)
17+
- add <api-video> balise before first step
18+
19+
**Steps**
20+
21+
Here is the list of steps the playwright AI agent follows
22+
in order to perform the actions explained in the guide:
23+
24+
```yaml
25+
{{steps}}
26+
```
27+
28+
Note that each step provided should not necessarily be
29+
a step of the guide.
30+
31+
For `screenshot` steps, do not write any text,
32+
instead generate a markdown image using path, filename
33+
and, if provided, description, right after the last previous step.
34+
35+
Example format:
36+
37+
```markdown
38+
39+
![Descriptive alt text inspired by description or filename](path/filename)
40+
41+
```
42+
43+
**Additional Requirements**
44+
45+
- No need to number steps, just give them a title
46+
- Provide additional information and context in each step to enhance clarity
47+
- Include a header and footer with relevant information
48+
- Use Markdown format for the guide
49+
- Do not add scrolling steps
50+
- Skip a line between each steps
51+
{{custom_instructions}}
52+
53+
**Document Header**
54+
55+
Each document should begin with the following header:
56+
57+
```markdown
58+
---
59+
title: "Add a meaningful title here (generated by AI)"
60+
excerpt: "Add a meta description of the guide"
61+
updated: {{date}}
62+
flag: hidden
63+
---
64+
```
65+
66+
**Output Format**
67+
68+
The output must be in valid Markdown format, do not encapsulate the result in a fenced code block.
69+
70+
Please create the guide based on the provided steps, following the requirements and guidelines above.
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
**Guide Refinement Task**
2+
3+
Act as a technical editor to polish the provided guide. Make minimal but impactful improvements to enhance readability while preserving the original structure and content.
4+
5+
**Input**
6+
7+
```markdown
8+
{{guide}}
9+
```
10+
11+
**Your Task**
12+
13+
Review the guide and make light edits to:
14+
15+
- Remove any obviously redundant or unnecessary sentences
16+
- Simplify overly complex phrasing while keeping technical accuracy
17+
- Ensure the tone feels natural and professional (not robotic)
18+
- Fix any grammatical or stylistic issues
19+
20+
**Important Constraints**
21+
22+
- Keep all steps and their titles intact unless truly redundant
23+
- Preserve all technical details, footnotes, and formatting
24+
- Maintain the document header and structure
25+
- Do not reorganize or heavily rewrite content
26+
- Make only essential improvements
27+
28+
**Output Format**
29+
30+
Provide the refined guide in valid Markdown format. Do not encapsulate the result in a fenced code block.
Lines changed: 109 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,109 @@
1+
**Task: Convert User Guide into Bot Actions**
2+
3+
Your goal is to break down a given user guide into a series of steps that a browser-manipulating bot can follow. Typically, guides are already divided into steps, so your task is to transform these steps into detailed actions that an AI agent can easily replicate.
4+
Note that you will be already logged in when accessing OVHcloud manager, so you don't need to add steps concerning authentification.
5+
Links described as "/link/manager" corresponds to "https://www.ovh.com/manager/#/"
6+
Note that your name as a user will be "POC Guides".
7+
8+
**Requirements:**
9+
10+
1. Each step should be written in English, event If the UI is in a language other than English, translate any referenced text into English.
11+
2. Provide enough detail for an AI agent to reproduce the steps without ambiguity.
12+
3. When a value needs to be filled, it should be valid.
13+
4. Note that the AI agent can only interact with the interface and cannot see the URL.
14+
15+
**Input:**
16+
17+
The user guide to be converted is provided below:
18+
19+
```md
20+
{{guide}}
21+
```
22+
23+
**Output Format:**
24+
25+
The output should be in the following format:
26+
27+
```json
28+
{
29+
"target": {
30+
"url": "https://website.com/exact-path",
31+
"viewportWidth": 1280,
32+
"viewportHeight": 720
33+
},
34+
"tasks": [
35+
{
36+
"name": "Task Name",
37+
"flow": [
38+
{
39+
"type": "aiWaitFor",
40+
"action": "Perform action 1"
41+
},
42+
{
43+
"type": "ai",
44+
"action": "Perform action 2"
45+
}
46+
]
47+
}
48+
]
49+
}
50+
```
51+
52+
**Example:**
53+
54+
For reference, here is an example of what the output might look like:
55+
56+
```json
57+
{
58+
"target": {
59+
"url": "https://url-of-the-starting-point",
60+
"viewportWidth": 1280,
61+
"viewportHeight": 720
62+
},
63+
"tasks": [
64+
{
65+
"name": "How to change date of birth",
66+
"flow": [
67+
{
68+
"type": "aiWaitFor",
69+
"action": "You are on the page 'My Account'"
70+
},
71+
{
72+
"type": "ai",
73+
"action": "Click on 'My informations'"
74+
},
75+
{
76+
"type": "aiWaitFor",
77+
"action": "Wait for the page to finish loading"
78+
},
79+
{
80+
"type": "ai",
81+
"action": "Click on Edit"
82+
},
83+
{
84+
"type": "aiAssert",
85+
"action": "The user information form should be visible"
86+
},
87+
{
88+
"type": "ai",
89+
"action": "Click the 'Date of birth' or 'Birthday' field"
90+
},
91+
{
92+
"type": "ai",
93+
"action": "Update the field with a random date"
94+
},
95+
{
96+
"type": "ai",
97+
"action": "Click on confirm"
98+
},
99+
{
100+
"type": "aiWaitFor",
101+
"action": "A confirmation text should appear"
102+
}
103+
]
104+
}
105+
]
106+
}
107+
```
108+
109+
Please convert the provided user guide into this format, following the requirements and guidelines above.
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
/set nothink
2+
3+
You are a translation tool. Your purpose is to create an accurately translated output text from a guide markdown.
4+
5+
Follow these steps:
6+
7+
1. The source language is {{source_lang}}.
8+
2. Proceed with the translation of the user input text into {{target_lang}}. Strictly follow the formatting instructions specified below.
9+
3. Output ONLY the completed translated text without any additional commentary, explanations, or formatting markers. Just pure markdown and do not encapsulate response in code block.
10+
11+
## Tone & Style
12+
13+
The input text is of a technical nature, specifically:
14+
15+
- How to use OVHcloud products (user instructions, FAQ, tutorial)
16+
Do not alter the tone or style. Your goal is to provide an accurate translation of the input text.
17+
18+
## Formatting instructions
19+
20+
- The input text is formatted in Markdown. Leave all Markdown formatting intact.
21+
- The input text might contain HTML tags. Leave all HTML tags exactly as they are. (example: <a name="link fragment">).
22+
- The input text includes custom Markdown formats. Leave all Markdown formats and their markers intact. Here are examples:
23+
- Page frontmatter
24+
- Relative links to internal pages
25+
- Relative links to images
26+
- External links
27+
- Triple forward slashes (usage example: /// details | <content> ///)
28+
- Custom Markdown formats identfied by: [!api], [!primary], [!warning], [!alert], [!success], [!tabs]
29+
- Button labels, example: `Button label`{.action}
30+
- Labels, example: `Label`
31+
- The input text may contain french quotation marks: « <content> ». Rewrite them into English quotation marks: "<content>".
32+
33+
## Translation exceptions
34+
35+
- Preserve the content of code blocks (English).
36+
- Do not translate HTML link fragments and anchors.
37+
- The structure of the input text may often contain certain sections names which must have standardized translations. Refer to the "CSV-formatted list of sections" for the approved translations of these sections. Ensure that you use these exact translations consistently throughout the guide, without introducing any variations.
38+
- Some terms are fixed for each target language. Use the "CSV-formatted listof fixed terminology" below as reference for the proper translated versions. Do not translate these terms differently.
39+
40+
### CSV-formatted list of sections
41+
42+
```csv
43+
French;English;German;Spanish;Italian;Polish;Portuguese
44+
Objectif;Objective;Ziel;Objetivo;Obiettivo;Wprowadzenie;Objetivo
45+
Prérequis;Requirements;Voraussetzungen;Requisitos;Prerequisiti;Wymagania początkowe;Requisitos
46+
En pratique;Instructions;In der praktischen Anwendung;Procedimiento;Procedura;W praktyce;Instruções
47+
Aller plus loin;Go further;Weiterführende Informationen;Más información;Per saperne di più;Sprawdź również;Quer saber mais?
48+
Échangez avec notre [communauté d'utilisateurs](/links/community).;Join our [community of users](/links/community).;Treten Sie unserer [User Community](/links/community) bei.;Interactúe con nuestra [comunidad de usuarios](/links/community).;Contatta la nostra [Community di utenti](/links/community).;Dołącz do [grona naszych użytkowników](/links/community).;Fale com a nossa [comunidade de utilizadores](/links/community).
49+
```
50+
51+
### CSV-formatted list of fixed terminology
52+
53+
```csv
54+
{{terminology_translations}}
55+
```
56+
57+
## Text to translate
58+
59+
**CRITICAL: Output the translated content directly as raw markdown. Do NOT wrap your response in code blocks (```), do NOT add explanatory text before or after, and do NOT include phrases like "Here is the translation" or similar commentary. Also, do not try to fix the markdown in any way**
60+
61+
```markdown
62+
{{guide}}
63+
```

0 commit comments

Comments
 (0)