From fa1702c9ff152b85a8fe91ed6027746762953402 Mon Sep 17 00:00:00 2001 From: skyace65 Date: Fri, 26 Jan 2018 22:54:05 -0500 Subject: [PATCH] Use less words --- .../contributing/docs_writing_guidelines.rst | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/community/contributing/docs_writing_guidelines.rst b/community/contributing/docs_writing_guidelines.rst index 87c7ae013..e25679d66 100644 --- a/community/contributing/docs_writing_guidelines.rst +++ b/community/contributing/docs_writing_guidelines.rst @@ -386,3 +386,24 @@ class names, which you can't fold, are ``Classes`` e.g. the ``KinematicBody2D class``. And individual lines with key-value pairs are ``properties``. E.g. ``position`` or ``modulate color`` are both ``properties``. + +Image Contribution guidelines +----------------------------- + +A significant part of the documentation is images, and there are several important +guidelines to follow. + +First, you should always be using the default editor theme and text when taking screenshots. + +For 3D screenshots use 4xMSAA, enable anisotropic filtering on the projects textures, +and set the anisotropic filter quality to 16x in Project Settings + +Screenshot size should not exceed 1920x1080. + +When you need to highlight an area of the editor to show something, like a +button or option, use a 2 pixel thick outline without a bevel. + +Before you add or replace any images in the documentation, they should be run through +a png compressor to save size. The built in lossless compressor in programs like Krita +or Photoshop should be done. However you should also use a lossy one, such as `pngquant `_ +where almost no image quality is lost during compression. \ No newline at end of file