Commit a62d93f9 authored by Marcia Ramos's avatar Marcia Ramos Committed by Mike Lewis

Docs: require release version in image filenames

parent 78c3e2d3
...@@ -409,11 +409,20 @@ To indicate the steps of navigation through the UI: ...@@ -409,11 +409,20 @@ To indicate the steps of navigation through the UI:
## Images ## Images
- Place images in a separate directory named `img/` in the same directory where - Place images in a separate directory named `img/` in the same directory where
the `.md` document that you're working on is located. Always prepend their the `.md` document that you're working on is located.
names with the name of the document that they will be included in. For - Images should have a specific, non-generic name that will
example, if there is a document called `twitter.md`, then a valid image name differentiate and describe them properly.
could be `twitter_login_screen.png`. - Always add to the end of the file name the GitLab release version
- Images should have a specific, non-generic name that will differentiate and describe them properly. number corresponding to the release milestone the image was added to,
or corresponding to the release the screenshot was taken from, using the
format `image_name_vX_Y.png`.
([Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/61027) in GitLab 12.1.)
- For example, for a screenshot taken from the pipelines page of
GitLab 11.1, a valid name is `pipelines_v11_1.png`. If you're
adding an illustration that does not include parts of the UI,
add the release number corresponding to the release the image
was added to. Example, for an MR added to 11.1's milestone,
a valid name for an illustration is `devops_diagram_v11_1.png`.
- Keep all file names in lower case. - Keep all file names in lower case.
- Consider using PNG images instead of JPEG. - Consider using PNG images instead of JPEG.
- Compress all images with <https://tinypng.com/> or similar tool. - Compress all images with <https://tinypng.com/> or similar tool.
...@@ -426,7 +435,7 @@ To indicate the steps of navigation through the UI: ...@@ -426,7 +435,7 @@ To indicate the steps of navigation through the UI:
Inside the document: Inside the document:
- The Markdown way of using an image inside a document is: - The Markdown way of using an image inside a document is:
`![Proper description what the image is about](img/document_image_title.png)` `![Proper description what the image is about](img/document_image_title_vX_Y.png)`
- Always use a proper description for what the image is about. That way, when a - Always use a proper description for what the image is about. That way, when a
browser fails to show the image, this text will be used as an alternative browser fails to show the image, this text will be used as an alternative
description. description.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment