Templates#
The following guide provides patterns for interface elements and directories.
Panels#
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#
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#
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
=======
Ureditev direktorija#
Razdelki naj bodo strukturirani tako:
ime_direktorija/
index.rst
(vsebuje povezave v notranje datoteke)introduction.rst
razdelek_1.rst
razdelek_2.rst
Na primer:
rendering/
index.rst
cycles/
index.rst
introduction.rst
materials/
index.rst
introduction.rst
volumes.rst
Poanta je v združevanju vsebine razdelka v mapi. Idealno je, da ima vsak razdelek svojo datoteko index.rst
(ki vsebuje kazalo tega razdelka) in datoteko introduction.rst
(uvod), ki uvaja v vsebino razdelka.
Kazalo#
Privzeto naj ima kazalo dva nivoja:
.. toctree::
:maxdepth: 2
introduction.rst
perspective.rst
depth_of_field.rst