Linking to other documentation pages
To create a link to another document in our documentation, we use the
For example, this link points to the document
:doc:`box.error reference </reference/reference_lua/box_error>`
Our convention is to put the full path to the referred document so that we can
easily replace the path if it changes.
Note that we can omit the
.rst part of the filename.
You can use the target document’s title as the link text.
To do so, omit the text in the link definition:
And you will get this:
Linking to labels (anchors)
To generate a link to the certain place in the page, we use the
For this purpose, we add our own labels for linking to any place in this documentation.
Our naming convention is as follows:
- Character set: a through z, 0 through 9, dash, underscore.
path dash filename dash tag
c_api is the directory name,
box_index is the file name (without “.rst”), and
iterator_type is the tag.
Use a dash “-” to delimit the path and the file name. In the documentation
source, we use only underscores “_” in paths and file names, reserving dash “-”
as the delimiter for local links.
The tag can be anything meaningful. The only guideline is for Tarantool syntax
items (such as members), where the preferred tag syntax is
module_or_object_name dash member_name. For example,
Linking to external resources
To make an external link, use the following syntax:
This is a paragraph that contains `a link <http://example.com/>`_.
Avoid separating the link and the target definition, like this:
This is wrong way to make `a link`_.
.. _a link: http://example.com/
Warning: Every separated link tends to cause troubles when this documentation
is translated to other languages. Please avoid using separated links.