Official repository containing all docs & guides of OVH Group
Find a file
benchbzh b6dd85d7f8
Merge pull request #8901 from ovh/BenCh_fixes
Telco - minor fixes on Linphone guide
2026-01-09 16:56:53 +01:00
docs-guideline feat: Update all API console links 2023-11-16 09:44:06 +00:00
links Merge branch 'develop' into sa-opennebula-deployment 2025-12-08 05:59:01 +01:00
pages Merge pull request #8901 from ovh/BenCh_fixes 2026-01-09 16:56:53 +01:00
templates update_links 2025-11-20 10:46:20 +01:00
.editorconfig Pull request #99: [bmasson] [D2I-2372] API Domain 2022-05-11 08:27:40 +02:00
.gitignore Merge branch 'develop' into lifecycle 2025-12-19 09:44:14 +01:00
.travis.yml refactor(travis): support docs-rendering submodules 2020-11-09 15:05:40 +00:00
CONTRIBUTING.md Updating readme, contributing and docs-guideline files 2023-05-16 14:54:49 +02:00
LICENSE Initial commit of docs 2018-03-26 14:43:23 +02:00
pull_request_template.md Pull Request template update 2025-10-24 15:00:09 +02:00
readme.md Readme update + Pull Request template creation 2025-03-27 16:06:14 +01:00

OVHcloud Documentation

This repository contains all the public documentation available about OVHcloud products, in 7 languages. A good way to find answers to some "how to" questions about OVHcloud products.

A web version also exists here. This website and this repository are synced.

This project is under active development, and new guides are added or updated on a daily basis.

Contributing

We will be happy to take a look at your contributions. You can contribute to this project by updating some existing guides, completing them or creating new ones.

A good way to easily get started with contributions is to fork the ovh/docs repo, write your changes on your fork then create a pull request (PR) from your fork to the ovh/docs repo.

Your PR must be done on the develop branch.

Our guides editing team will then review your contribution and choose to edit, validate or reject it.

If you are an OVHcloud employee, do not use a fork. Instead, please contact the OVHcloud Guides Team so to be granted /write access to this repository.

Please take into consideration the following guidelines :

Content

  • Verify and test every action you describe: do not write about anything you cannot test by yourself.
  • Please provide us with a description regarding your contribution.
  • All OVHcloud guides are built with the same layout and structure, please use them as a template to write your own contributions.

New guide

When creating a new guide, you must also do the following:

  • Create a meta.yaml file in your new guide's folder. This file must contain the 2 following fields:
    • id:: generate a UUID4 unique identifier using either https://www.uuidgenerator.net/version4 or the uuidgen command from a terminal.
    • full_slug:: this will generate the slug component of the future guide's URL. Please rely on the already existing and related guides so to prefix your ``full_slug` accordingly. Also only include important keywords and try keeping it short.
  • Update the index so that your new guide is listed in its right category. If that category doesn't exist yet, you can create it but you will also have to generate its translations in the 7 index-translations.<language>.md files.

Screenshots

  • Prefer to use the English version of the OVHcloud Control Panel or any other interface when taking screenshots.
  • The extension of your screenshots must be in .png format
  • Please use the OrangeSunrise colour to highlight any information in screenshots (#ff9803 - RGBA: 255, 152, 3, 1)

Licensing

When contributing you agree with the licensing terms, provided in the LICENSE file.