Commit 2ff0ba5f authored by Craig Norris's avatar Craig Norris

Merge branch 'selhorn-patch-236' into 'master'

Update image guidelines

Closes #233171

See merge request gitlab-org/gitlab!42418
parents e8abe728 384de89d
...@@ -1120,16 +1120,14 @@ they need to interact with the application. ...@@ -1120,16 +1120,14 @@ they need to interact with the application.
When you take screenshots: When you take screenshots:
- *Capture the most relevant area of the page.* Don't include unnecessary white - *Capture the most relevant area of the page.* Don't include unnecessary white
space or areas of the page that don't help illustrate your point. Also, don't space or areas of the page that don't help illustrate the point. The left
include the entire page if you don't have to, but also ensure the image sidebar of the GitLab user interface can change, so don't include the sidebar
contains enough information to allow the user to determine where things are. if it's not necessary.
- *Be consistent.* Find a browser window size that works for you that also - *Keep it small.* If you don't need to show the full width of the screen, don't.
displays all areas of the product, including the left navigation (usually > A value of 1000 pixels is a good maximum width for your screenshot image.
1200px wide). For consistency, use this browser window size for your - *Be consistent.* Coordinate screenshots with the other screenshots already on
screenshots by installing a browser extension for setting a window to a a documentation page. For example, if other screenshots include the left
specific size (for example, sidebar, include the sidebar in all screenshots.
[Window Resizer](https://chrome.google.com/webstore/detail/window-resizer/kkelicaakdanhinjdeammmilcgefonfh/related?hl=en)
for Google Chrome).
### Save the image ### Save the image
......
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