Add anchor links to headers (#1271)

* Add anchor links to about page

Author: jyn514

templates/core/about/builds.html

@@ -19,15 +19,15 @@ <h1>Builds</h1>
         {%- endif -%}
     </p>
 
-    <h3 id="notes-on-docsrs">Notes on using Docs.rs</h3>
+    <h3 id="notes-on-docsrs"> <a href="#notes-on-docsrs">Notes on using Docs.rs</a> </h3>
 
-    <h4 id="setting-a-readme">Setting a README</h4>
+    <h4 id="setting-a-readme"> <a href="#setting-a-readme">Setting a README</a> </h4>
     <p>
         The README of a crate is taken from the <code>readme</code> field defined in
         <code>Cargo.toml</code>. If this field is not set, no README will be displayed.
     </p>
 
-    <h4 id="detecting-docsrs">Detecting Docs.rs</h4>
+    <h4 id="detecting-docsrs"> <a href="#detecting-docsrs">Detecting Docs.rs</a> </h4>
     <p>
         To recognize Docs.rs from <code>build.rs</code> files, you can test for the environment variable <code>DOCS_RS</code>, e.g.:
         {% filter dedent(levels=4) -%}
@@ -42,7 +42,7 @@ <h4 id="detecting-docsrs">Detecting Docs.rs</h4>
         This approach can be helpful if you need dependencies for building the library, but not for building the documentation.
     </p>
 
-    <h4 id="cross-compiling">Cross-compiling</h4>
+    <h4 id="cross-compiling"> <a href="#cross-compiling">Cross-compiling</a> </h4>
     <p>
       All targets other than <code>x86_64-unknown-linux-gnu</code> are cross-compiled. For implementation reasons, this is unlikely to change for the foreseeable future.
     </p>
@@ -61,32 +61,32 @@ <h4 id="cross-compiling">Cross-compiling</h4>
         This approach is also useful for setting <a href="https://doc.rust-lang.org/cargo/reference/features.html">cargo features</a>.
     </p>
 
-    <h4 id="testing-builds-locally">Testing documentation builds locally</h4>
+    <h4 id="testing-builds-locally"> <a href="#testing-builds-locally">Testing documentation builds locally</a> </h4>
     {%- set build_subcommand = docsrs_repo ~ "/blob/master/README.md#build-subcommand" -%}
     <p>
         The Docs.rs <a href="{{ build_subcommand | safe }}">README</a> describes how to build
         unpublished crate documentation locally using the same build environment as the Docs.rs build agent.
     </p>
 
-    <h3 id="diagnosing-failed-builds">Diagnosing failed builds</h3>
+    <h3 id="diagnosing-failed-builds"> <a href="#diagnosing-failed-builds">Diagnosing failed builds</a> </h3>
 
-    <h4 id="missing-dependencies">Missing dependencies</h4>
+    <h4 id="missing-dependencies"> <a href="#missing-dependencies">Missing dependencies</a> </h4>
     <p>
         Missing dependencies are a common reason for failed builds.
         Docs.rs dependencies are managed through
         <a href="https://github.com/rust-lang/crates-build-env">crates-build-env</a>.
         See <a href="https://forge.rust-lang.org/docs-rs/add-dependencies.html">Forge</a> for how to add a dependency.
     </p>
 
-    <h4 id="read-only-directories">Write attempt on read-only directories</h4>
+    <h4 id="read-only-directories"> <a href="#read-only-directories">Write attempt on read-only directories</a> </h4>
     <p>
         Most of the sandbox is a read-only file system, including the source directory of your crate and its dependencies.
         If your <code>build.rs</code> generates files that are relevant for documentation, consider writing to the
         <a href="https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates">cargo output directory</a>,
         passed in the environment variable <code>OUT_DIR</code>.
     </p>
 
-    <h4 id="hitting-resource-limits">Hitting resource limits</h4>
+    <h4 id="hitting-resource-limits"> <a href="#hitting-resource-limits">Hitting resource limits</a> </h4>
     <p>
         All the builds are executed inside a sandbox with limited resources. The current limits are:
     </p>
@@ -104,7 +104,7 @@ <h4 id="hitting-resource-limits">Hitting resource limits</h4>
         </ul>
     </p>
 
-    <h4 id="failures-and-rebuilds">Other failures and requesting rebuilds</h4>
+    <h4 id="failures-and-rebuilds"> <a href="#failures-and-rebuilds">Other failures and requesting rebuilds</a> </h4>
     <p>
         If your crate fails to build for a reason not listed here, please <a href="{{ docsrs_repo | safe }}/issues">file an issue</a>.
         Some build failures can be fixed by Docs.rs, e.g., by issuing a rebuild after a bug in Docs.rs has been fixed.

templates/core/about/index.html

@@ -25,18 +25,18 @@ <h1 id="crate-title">About Docs.rs</h1>
         </p>
 
 
-        <h2 id="more-about-docsrs">More about Docs.rs</h2>
+        <h2 id="more-about-docsrs"> <a href="#more-about-docsrs">More about Docs.rs</a> </h2>
         <ol>
             <li><a href="/about/badges">Badges</a>: How to use badges generated by Docs.rs</li>
             <li><a href="/about/builds">Builds</a>: How Docs.rs builds documentation for a crate</li>
             <li><a href="/about/metadata">Metadata</a>: How you can configure a build</li>
             <li><a href="/about/redirections">Redirections</a>: How Docs.rs uses semantic versioning in URLs</li>
         </ol>
 
-        <h3 id="version">Version</h3>
+        <h3 id="version"> <a href="#version">Version</a> </h3>
         <p>Currently running Docs.rs version is: <strong>{{ docsrs_version() }}</strong></p>
 
-        <h3 id="contact">Contact</h3>
+        <h3 id="contact"> <a href="#contact">Contact</a> </h3>
         {%- set governance_link = "https://www.rust-lang.org/governance/teams/dev-tools#docs-rs" -%}
         <p>
             Docs.rs is run and maintained by the <a href="{{ governance_link | safe }}">Docs.rs team</a>.