In September-October 2015, we changed the way we add cross references that link across guides (aka RTD projects) to the documentation set.
(Previously, if one guide included a link to another guide, we provided the URL of the destination as the link.)
Here are some notes from a team meeting on 24 Sept in case we need a cheat sheet during the transition period.
- The change applies to files in the edx-documentation repo only. (We should continue to use a links.rst file and the `Name of Linked Document`_ rst markup in other repos.)
- For links to different RTD projects, use the
:ref:`prefix:label` format for cross references.
- The prefix comes from the Intersphinx mappings at the bottom of the new shared conf.py file.
- The label is the bookmark value that we add to the top of rst files and above headings to pinpoint topic locations, using
.. _Label: format.
- Going forward, DO NOT change any of the labels.
- If you do change a label, make sure to search the entire doc repo (and the analytics dashboard repo too!) and fix it everywhere.
- You must be connected to the Internet to
make html locally.
make html looks for live, published URLs when it runs, and throws messages if it can't find them. So,
make html for release notes in particular will throw warnings.
- There will be one links.rst file for the entire repo, containing links to external URLs (for example, GitHub, Twitter, etc.)
- Again, we only have to use the
:ref:`prefix:label` format for a link to a different RTD project. For cross references within the same project, don't use the prefix – the xref will go to that location within the current guide.
List of InterSphinx Map Prefixes
Important! For the most up-to-date list, ALWAYS refer to the edx-documentation/shared/conf.py file, and look in the "intersphinx_mapping" section at the end of the page.