Option A (status quo): Every article that
transcludes a given navbox should normally also be included as a link in the navbox, so that the navigation is bidirectional.
Option B: Articles that
transclude a given navbox should normally be included as a link in the navbox, enabling bidirectional navigation, but exceptions may be made when inclusion would be
undue.
Option C: There is no requirement that articles that
transclude a given navbox have to be included as a link in the navbox.
Add the tag {{rfc|xxx}} at the top of a
talk page section, where "xxx" is the category abbreviation. The different category abbreviations that should be used with {{
rfc}} are listed above in parenthesis. Multiple categories are separated by a vertical pipe. For example, {{rfc|xxx|yyy}}, where "xxx" is the first category and "yyy" is the second category.
Option A (status quo): Every article that
transcludes a given navbox should normally also be included as a link in the navbox, so that the navigation is bidirectional.
Option B: Articles that
transclude a given navbox should normally be included as a link in the navbox, enabling bidirectional navigation, but exceptions may be made when inclusion would be
undue.
Option C: There is no requirement that articles that
transclude a given navbox have to be included as a link in the navbox.
Add the tag {{rfc|xxx}} at the top of a
talk page section, where "xxx" is the category abbreviation. The different category abbreviations that should be used with {{
rfc}} are listed above in parenthesis. Multiple categories are separated by a vertical pipe. For example, {{rfc|xxx|yyy}}, where "xxx" is the first category and "yyy" is the second category.