The following guide provides patterns for interface elements and directories.
Panels should be documented by their own heading, nested panels should use decreasing heading levels. Each panel could have its own page based on the length of documentation and/or the amount of panels. Expanded menus that toggle what properties are presented to the user should be treated like subpanels:
Panel Title =========== Nested Panel Title ------------------
Properties should be documented using definition lists. Properties that are hidden based on other properties should used nested definitions:
Property Property description. Hidden Property Hidden property description.
Select menus should be documented using the following syntax:
Menu Label General description of the menu. :Menu Item: Menu Item Definition. :Menu Item: Menu Item Definition. :Menu Item: Menu Item Definition.
Nodes should always have three headings inputs, properties and outputs with a note of absence if the node has none. At the end of the page can be an optional example(s) section:
********** World Node ********** .. figure:: /images/render_shader-nodes_output_world_node.png :align: right The World node. Introduction and general use case(s). Inputs ====== This node has no inputs. Properties ========== This node has no properties. Outputs ======= This node has no outputs. Example =======
Sections should be generally structured as follows:
index.rst(contains links to internal files)
The idea is to enclose all the content of a section inside of a folder. Ideally every section
should have an
index.rst (containing the TOC for that section) and an
(introducing) to the contents of the section.
Table of Contents¶
By default, a table of contents should show two levels of depth:
.. toctree:: :maxdepth: 2 introduction.rst perspective.rst depth_of_field.rst