Allow clicking on header to get fragment link

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/commentary/orchard.html b/docs/commentary/orchard.html
index 12b5b9a9..0f2aaf42 100644
--- a/docs/commentary/orchard.html
+++ b/docs/commentary/orchard.html
@@ -4,7 +4,7 @@
   <title>BQN: The APL Orchard</title>
 </head>
 <div class="nav">(<a href="https://github.com/mlochbaum/BQN">github</a>) / <a href="../index.html">BQN</a> / <a href="index.html">commentary</a></div>
-<h1 id="the-apl-orchard">The APL Orchard</h1>
+<h1 id="the-apl-orchard"><a class="header" href="#the-apl-orchard">The APL Orchard</a></h1>
 <p>BQN users have largely moved to Matrix or Discord chat, and I no longer recommend using the APL Orchard (perhaps also known by the shortcut URL apl.chat). Chat options are discussed <a href="../index.html#where-can-i-find-bqn-users">in the README</a>; this page gives the reasons we switched forums.</p>
 <p>StackExchange chat requires a StackExchange account with enough reputation, or moderator-granted permissions, to talk, and sets a reputation threshold for some minor features within the chat as well. Those who don't use StackExchange have to make an account and send an email to get permission. While this filtering probably leads to a more dedicated forum base, it does this at the expense of keeping out a lot of people, including many who have a lot to contribute. I think this isn't a good tradeoff, and this seems to be the community concensus as well.</p>
 <p>StackExchange is not built for bots, and existing tooling for it is not very good. At the time of writing the bot that used to link the APL Orchard to IRC #apl is able to write but not read posts, so that the link only runs one way.</p>