From 04e7ca3ccb0dbe02027549108695d8497f0429f2 Mon Sep 17 00:00:00 2001
From: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
Date: Wed, 8 Jun 2022 17:58:23 -0500
Subject: [PATCH] Guidelines for adding images on docs (#6159)
Added two bullet points.
---
handbook/community.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/handbook/community.md b/handbook/community.md
index 9253d1b49f84..1bb9d52317e8 100644
--- a/handbook/community.md
+++ b/handbook/community.md
@@ -228,6 +228,8 @@ When adding or reordering a page, try to leave as much room between values as po
Try to keep images in the docs at a minimum. Images can be a quick way to help users understand a concept or direct them towards a specific user interface(UI) element. Still, too many can make the documentation feel cluttered and more difficult to maintain.
When adding images to the Fleet documentation, follow these guidelines:
+- UI screenshots should be a 4:3 aspect ratio (1280x960). This is an optimal size for the container width of the docs and ensures that content in screenshots is as clear as possible to view in the docs (and especially on mobile devices).
+- You can set up a custom preset in the Google Chrome device toolbar (in Developer Tools) to quickly adjust your browser to the correct size for taking a screenshot.
- Keep the images as simple as possible to maintain. Screenshots can get out of date quickly as UIs change.
- Exclude unnecessary images. Images should be used to help emphasize information in the docs, not replace it.
- Minimize images per doc page. For doc maintainers and users, more than one or two per page can get overwhelming.
@@ -414,4 +416,4 @@ This group maintains the following [Slack channels](https://fleetdm.com/handbook
-
\ No newline at end of file
+