Document the new AUTOTITLE shortcut (#34462)

Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>

Author: sarahs

Diff for: content/README.md

@@ -357,6 +357,10 @@ and when viewed on GitHub Enterprise Server docs, the version is included as wel
 /en/enterprise-server@2.20/github/writing-on-github/creating-a-saved-reply
 ```
 
+### Using AUTOTITLE for internal links
+
+If you create an internal link, you can use the AUOTITLE keyword to generate an article's title in the rendered link. See the [markup reference](../contributing/content-markup-reference.md#internal-links-with-autotitle) for details.
+
 ### Linking to the current article in a different version of the docs
 
 Sometimes you may want to link from an article to the same article in a different product version. For example:

Diff for: contributing/content-markup-reference.md

@@ -16,6 +16,7 @@
   - [Usage](#usage-5)
 - [Reusable and variable strings of text](#reusable-and-variable-strings-of-text)
 - [Tables with codeblocks](#tables-with-codeblocks)
+- [Internal links with AUTOTITLE](#internal-links-with-autotitle)
 
 ## Writing in Markdown
 
@@ -254,3 +255,17 @@ If this happens, add the following CSS style to the `<table>` HTML tag:
 ```
 
 For a current example of this usage, see the [GitHub Actions examples workflow library](https://docs.github.com/en/actions/examples).
+
+## Internal links with AUTOTITLE
+
+When linking to another GitHub docs page, use standard Markdown syntax like `[]()` but type `AUTOTITLE` instead of the page title. The application will replace `AUTOTITLE` with the title of the linked page during rendering. This special keyword is case-sensitive, so take care with your typing or the replacement will not work.
+
+### Usage
+
+- `For more information, see "[AUTOTITLE](/path/to/page)."`
+- `For more information, see "[AUTOTITLE](/path/to/page#section-link)."`
+- `For more information, see the TOOLNAME documentation in "[AUTOTITLE](/path/to/page?tool=TOOLNAME)."`
+
+Note that **same-page section links do not work** with this keyword. Type out the full header text instead.
+
+Read more about links in the [content style guide](./content-style-guide.md#links).

Diff for: contributing/content-style-guide.md

@@ -332,17 +332,26 @@ For plain text, use linebreaks to separate paragraphs in the source (two consecu
 
 ## Links
 
-Introduce links consistently using a standard format that clearly indicates where we’re linking.
+Introduce links consistently using a standard format that clearly indicates where we're linking.
 
-- For links to other articles in the GitHub docs: `For more information, see "[Page or article title]()."`
-- For links to another section in the same article: `For more information, see "[Header text]()."`
-- For links to specific sections in other articles in the GitHub docs: `For more information, see "[Article title]()."`
-- For links to an article with a specific tool selected: `For more information, see the TOOLNAME documentation in "[ARTICLE TITLE](/PATH/TO/ARTICLE?tool=TOOLNAME).`
-- For links to external documentation: `For more information, see [Page or article title]() in the X documentation.`
+For any link that points to another GitHub docs page, use the special keyword `AUTOTITLE`. See details in the [content markup reference](./content-markup-reference.md#internal-links-with-autotitle).
+
+Usage examples:
+
+- For links to other pages: `For more information, see "[AUTOTITLE](/path/to/page)."`
+- For links to sections in other pages: `For more information, see "[AUTOTITLE](/path/to/page#section-link)."`
+- For links to a page with a tool selected: `For more information, see the TOOLNAME documentation in "[AUTOTITLE](/path/to/page?tool=TOOLNAME).`
+
+Same-page section links do **not** work with `AUTOTITLE`. Instead, type out the full header text: `For more information, see "[Header text](#section-link)."`
+
+For links to external documentation, type out the full article name: `For more information, see [Page or article title](https://some-docs.com/path/to/page) in the X documentation.`
 
 Do not include quotation marks within a hyperlink.
 
-Links should be meaningful and provide high value to the user’s journey - link out carefully. Move links that are helpful but not necessary to an article’s further reading section. Do not repeat the same link more than once in the same article or under the same H2 header.
+Some best practices for using links:
+- Links should be meaningful and provide high value to the user’s journey—link out carefully.
+- Move links that are helpful but not necessary to an article’s further reading section.
+- Do not repeat the same link more than once in the same article or under the same H2 header.
 
 For accessibility and readability, avoid inline or midsentence links.
 - **Use:** OAuth2 tokens can be acquired programmatically for applications that are not websites. For more information, see "[Setting up and registering OAuth Apps](https://developer.github.com/apps/building-integrations/setting-up-and-registering-oauth-apps/)" and "[Create a new authorization](https://docs.github.com/en/enterprise-server@2.22/rest/reference/oauth-authorizations/#create-a-new-authorization)."