Writing Style Guide
The main goals for this manual are as follows:
- User Focused
The manual is written for people educated in computer graphics, who understand the basics of 3D and/or know other 3D software. While some areas of computer graphics are highly technical, this manual shall be kept understandable by non-technical users.
The manual provides detailed functional description of all features, tools and options in Blender. While there is a canonical source of truth for each of Blender’s key areas, this does not mean we have to document every small detail. The manual should provide information on what a feature is, how to use it, and its purpose. More background information should be provided when necessary to give deeper understanding of a 3D pipeline.
Computer graphics is an incredibly interesting field, there are many rules, exceptions to the rules, and interesting details. Expanding into details can add unnecessary content, so keep the text concise and relevant to the topic at hand.
Keep in mind that Blender has frequent releases, so try to write content that will not have to be redone the moment some small change is made. This also helps a small documentation community to maintain the manual.
In order to maintain a consistent writing style within the manual, please keep this page in mind and only deviate from it when you have a good reason to do so.
Rules of thumb:
Spell checking is strongly recommended.
Use American English (e.g: modeling and not modelling, color and not colour) also for formatting numbers (e.g: 2,718.28 and not 2 718,28).
Take care about grammar, appropriate wording and use simple English.
Keep sentences short and clear, resulting in text that is easy to read, objective and to the point.
Including why or how an option might be useful is a good idea.
If you are unsure about how a feature works, ask someone else or find out who developed it and ask them.
To be avoided:
Avoid writing in first person perspective, about yourself or your own opinions.
Avoid weasel words and being unnecessarily vague, e.g:“Reloading the file will probably fix the problem”“Most people do not use this option because …”
Avoid including specific details such as:“Blender has 23 different kinds of modifiers.”“Enabling previews adds 65536 bytes to the size of each blend-file (unless it is compressed).”
These details are not useful for users to memorize and they become quickly outdated.
Avoid documenting bugs.
Blender often has 100’s of bugs fixed between releases, so it is not realistic to reference even a fraction of them from the manual, while keeping this list up to date.
Issues that are known to the developers and are not going to be resolved before the next release can be documented as Known Limitations. In some cases, it may be best to include them in the troubleshooting section.
Avoid product placements, i.e. unnecessarily promoting software or hardware brands. Keep content vendor-neutral where possible.
Avoid technical explanations about the mathematical/algorithmic implementation of a feature if there is a simpler way to explain it.
(E.g. explaining how mesh smoothing algorithms work is unnecessary, but the blending types of a Mix node do need a mathematical explanation.)
Avoid repetition of large portions of text. Simply explain it once, and from then on refer to that explanation.
For general terminology, consider defining a
:term:in the glossary.
Avoid enumerations of similar options, such as listing every preset or every frame rate in a select menu.
Their contents may be summarized or simply omitted. – Such lists are only showing what is already obvious in the interface and end up being a lot of text to read and maintain.
Avoid documenting changes in Blender between releases, that is what the release notes are for. We only need to document the current state of Blender.
Unless the unit a value is measured in is obscure and unpredictable, there is no need to mention it.
Do not simply copy the tooltips from Blender. – People will come to the manual to learn more than is provided by the UI.
As a last resort you can add comment (which is not shown in the HTML page, but useful for other editors):
.. TODO, how does this tool work? ask Joe Blogg's.
This section is specifically about the Glossary section, where we define common terms in Blender and computer graphics.
Rules of thumb:
Define the term before providing any further information.
Avoid using constructs such as “it is” or “xyz is” before the definition.
Avoid repeating the term immediately or using it in the definition.
Avoid adding terms not found in Blender’s interface or the manual.
Avoid overly long entries. If an explanation of a complex term is needed, supplement with external links.
Avoid duplicating documentation; if explaining the term is the primary focus of another section of the manual (e.g. if the term is the name of a tool), either just link to that section, or avoid creating a glossary entry entirely.
URL references are to be added at the end, formatted as follows, e.g:
See also `OpenGL <https://en.wikipedia.org/wiki/OpenGL>`__ on Wikipedia.
Uses a grayscale heightmap, like Bump Mapping,
but the image is used to physically move the vertices of the mesh at render time.
This is of course only useful if the mesh has large amounts of vertices.
Would be written like this instead, putting a definition first:
A method for distorting vertices based on an image.
Similar to Bump Mapping, but instead operates on the mesh's actual geometry.
This relies on the mesh having enough geometry.
The Doppler effect is the change in pitch that occurs
when a sound has a velocity relative to the listener.
Would be written more like this, avoiding the immediate repetition of the term:
Perceived change in pitch that occurs
when the source of a sound is moving relative to the listener.
It is a class of objects.
In Blender there are Bézier curves and NURBS curves.
Would be written more like this, avoiding the “it is”:
A type of object defined in terms of a line interpolated between Control Vertices.
Available types of curves include Bézier and NURBS.