use explicit sections on the contact page

1 files changed, 74 insertions, 69 deletions

diff --git a/static/contact.html b/static/contact.html
index 7fd45dc4..81ba4133 100644
--- a/static/contact.html
+++ b/static/contact.html
@@ -44,93 +44,98 @@
                 <a href="#contact">Contact</a>
             </h1>
 
-            <h2 id="contacting-the-project">
-                <a href="#contacting-the-project">Contacting the project</a>
-            </h2>
+            <section id="contacting-the-project">
+                <h2>
+                    <a href="#contacting-the-project">Contacting the project</a>
+                </h2>
 
-            <p>Do not contact us with offers to sell us products or services.</p>
+                <p>Do not contact us with offers to sell us products or services.</p>
 
-            <p>Please don't contact the GrapheneOS project or developers to request support /
-            device support / features or to report bugs.  Use the <a href="#community">community
-            platforms</a> and <a href="#reporting-issues">issue trackers</a> listed below. The
-            developers are active on the IRC / Matrix channel but the broader community can
-            usually answer most questions, and this allows the developers to focus their time and
-            energy on the project.</p>
+                <p>Please don't contact the GrapheneOS project or developers to request support /
+                device support / features or to report bugs.  Use the <a href="#community">community
+                platforms</a> and <a href="#reporting-issues">issue trackers</a> listed below. The
+                developers are active on the IRC / Matrix channel but the broader community can
+                usually answer most questions, and this allows the developers to focus their time and
+                energy on the project.</p>
 
-            <p>Email is the preferred way to contact the project. Twitter direct messages are
-            checked much less frequently. A public @reply in a tweet is not a good way to contact
-            the project. It is not considered sending a message by Twitter and is not queued up as
-            a message to be read, only as a regular notification that is likely to be missed or
-            forgotten.</p>
+                <p>Email is the preferred way to contact the project. Twitter direct messages are
+                checked much less frequently. A public @reply in a tweet is not a good way to contact
+                the project. It is not considered sending a message by Twitter and is not queued up as
+                a message to be read, only as a regular notification that is likely to be missed or
+                forgotten.</p>
 
-            <p>Please do not send multiple copies / versions of the same email to different
-            addresses. Either send it to a single address or CC the other addresses. In general,
-            it's the same person handling every email address, and they don't need to see multiple
-            copies of the same email in their inbox.</p>
+                <p>Please do not send multiple copies / versions of the same email to different
+                addresses. Either send it to a single address or CC the other addresses. In general,
+                it's the same person handling every email address, and they don't need to see multiple
+                copies of the same email in their inbox.</p>
 
-            <p>You can contact <a href="mailto:contact@grapheneos.org">contact@grapheneos.org</a>
-            for topics related to GrapheneOS. Please don't send emails unrelated to GrapheneOS to
-            this address.</p>
+                <p>You can contact <a href="mailto:contact@grapheneos.org">contact@grapheneos.org</a>
+                for topics related to GrapheneOS. Please don't send emails unrelated to GrapheneOS to
+                this address.</p>
 
-            <p>The <a href="mailto:security@grapheneos.org">security@grapheneos.org</a>
-            address is for reporting high priority security issues related to GrapheneOS. Please
-            don't send other kinds of emails to this address. It is not a way of increasing the
-            priority of emails that are not security reports. Your emails will be treated as a
-            much lower priority if you misuse this address.</p>
+                <p>The <a href="mailto:security@grapheneos.org">security@grapheneos.org</a>
+                address is for reporting high priority security issues related to GrapheneOS. Please
+                don't send other kinds of emails to this address. It is not a way of increasing the
+                priority of emails that are not security reports. Your emails will be treated as a
+                much lower priority if you misuse this address.</p>
 
-            <p>The email address of the lead developer is
-            <a href="mailto:daniel.micay@grapheneos.org">daniel.micay@grapheneos.org</a>.</p>
+                <p>The email address of the lead developer is
+                <a href="mailto:daniel.micay@grapheneos.org">daniel.micay@grapheneos.org</a>.</p>
 
-            <p>The official Twitter account for the project is <a href="https://twitter.com/GrapheneOS">@GrapheneOS</a>
-            which is used for official announcements. The account of the lead developer is
-            <a href="https://twitter.com/DanielMicay">@DanielMicay</a> and is primarily focused on
-            the privacy and security research/engineering work on GrapheneOS.</p>
+                <p>The official Twitter account for the project is <a href="https://twitter.com/GrapheneOS">@GrapheneOS</a>
+                which is used for official announcements. The account of the lead developer is
+                <a href="https://twitter.com/DanielMicay">@DanielMicay</a> and is primarily focused on
+                the privacy and security research/engineering work on GrapheneOS.</p>
+            </section>
 
-            <h2 id="community">
-                <a href="#community">Community</a>
-            </h2>
+            <section id="community">
+                <h2>
+                    <a href="#community">Community</a>
+                </h2>
 
-            <p>The official chat room used to discuss the project is the IRC channel #grapheneos
-            on irc.freenode.net and
-            <a href="https://freenode.logbot.info/grapheneos">publicly logged</a>. The channel is
-            bridged to Matrix and is available at #grapheneos:matrix.org for Matrix users.</p>
+                <p>The official chat room used to discuss the project is the IRC channel #grapheneos
+                on irc.freenode.net and
+                <a href="https://freenode.logbot.info/grapheneos">publicly logged</a>. The channel is
+                bridged to Matrix and is available at #grapheneos:matrix.org for Matrix users.</p>
 
-            <p>The official subreddit is <a href="https://reddit.com/r/GrapheneOS">/r/GrapheneOS</a>.</p>
+                <p>The official subreddit is <a href="https://reddit.com/r/GrapheneOS">/r/GrapheneOS</a>.</p>
+            </section>
 
-            <h2 id="reporting-issues">
-                <a href="#reporting-issues">Reporting issues</a>
-            </h2>
+            <section id="reporting-issues">
+                <h2>
+                    <a href="#reporting-issues">Reporting issues</a>
+                </h2>
 
-            <p>Most issues should be reported to the global OS issue tracker for GrapheneOS
-            sub-projects. However, standalone projects and anything outside of the GrapheneOS
-            source tree (like the websites) has a dedicated issue tracker. The issue trackers are
-            listed for reference:</p>
+                <p>Most issues should be reported to the global OS issue tracker for GrapheneOS
+                sub-projects. However, standalone projects and anything outside of the GrapheneOS
+                source tree (like the websites) has a dedicated issue tracker. The issue trackers are
+                listed for reference:</p>
 
-            <ul>
-                <li><a href="https://github.com/GrapheneOS/os_issue_tracker/issues">OS issue tracker</a> for all GrapheneOS repositories that are not standalone projects</li>
-                <li><a href="https://github.com/GrapheneOS/hardened_malloc/issues">hardened_malloc issue tracker</a></li>
-            </ul>
+                <ul>
+                    <li><a href="https://github.com/GrapheneOS/os_issue_tracker/issues">OS issue tracker</a> for all GrapheneOS repositories that are not standalone projects</li>
+                    <li><a href="https://github.com/GrapheneOS/hardened_malloc/issues">hardened_malloc issue tracker</a></li>
+                </ul>
 
-            <p>Standalone app projects:</p>
+                <p>Standalone app projects:</p>
 
-            <ul>
-                <li><a href="https://github.com/GrapheneOS/Auditor/issues">Auditor issue tracker</a></li>
-                <li><a href="https://github.com/GrapheneOS/PdfViewer/issues">PDF Viewer issue tracker</a></li>
-                <li><a href="https://github.com/GrapheneOS/platform_packages_apps_Updater/issues">Update client issue tracker</a></li>
-                <li><a href="https://github.com/GrapheneOS/Vanadium/issues">Vanadium (Chromium variant) issue tracker</a></li>
-            </ul>
+                <ul>
+                    <li><a href="https://github.com/GrapheneOS/Auditor/issues">Auditor issue tracker</a></li>
+                    <li><a href="https://github.com/GrapheneOS/PdfViewer/issues">PDF Viewer issue tracker</a></li>
+                    <li><a href="https://github.com/GrapheneOS/platform_packages_apps_Updater/issues">Update client issue tracker</a></li>
+                    <li><a href="https://github.com/GrapheneOS/Vanadium/issues">Vanadium (Chromium variant) issue tracker</a></li>
+                </ul>
 
-            <p>Services:</p>
-
-            <ul>
-                <li><a href="https://github.com/GrapheneOS/AttestationServer/issues">AttestationServer (attestation.app) issue tracker</a></li>
-                <li><a href="https://github.com/GrapheneOS/grapheneos.org/issues">grapheneos.org issue tracker</a></li>
-                <li><a href="https://github.com/GrapheneOS/releases.grapheneos.org/issues">Update server (releases.grapheneos.org) issue tracker</a></li>
-                <li><a href="https://github.com/GrapheneOS/connectivitycheck.grapheneos.org/issues">Connectivity check server (connectivitycheck.grapheneos.org) issue tracker</a></li>
-                <li><a href="https://github.com/GrapheneOS/mail.grapheneos.org/issues">Mail server (mail.grapheneos.org) issue tracker</a></li>
-                <li><a href="https://github.com/GrapheneOS/time.grapheneos.org/issues">HTTPS time server (time.grapheneos.org) issue tracker</a></li>
-            </ul>
+                <p>Services:</p>
 
+                <ul>
+                    <li><a href="https://github.com/GrapheneOS/AttestationServer/issues">AttestationServer (attestation.app) issue tracker</a></li>
+                    <li><a href="https://github.com/GrapheneOS/grapheneos.org/issues">grapheneos.org issue tracker</a></li>
+                    <li><a href="https://github.com/GrapheneOS/releases.grapheneos.org/issues">Update server (releases.grapheneos.org) issue tracker</a></li>
+                    <li><a href="https://github.com/GrapheneOS/connectivitycheck.grapheneos.org/issues">Connectivity check server (connectivitycheck.grapheneos.org) issue tracker</a></li>
+                    <li><a href="https://github.com/GrapheneOS/mail.grapheneos.org/issues">Mail server (mail.grapheneos.org) issue tracker</a></li>
+                    <li><a href="https://github.com/GrapheneOS/time.grapheneos.org/issues">HTTPS time server (time.grapheneos.org) issue tracker</a></li>
+                </ul>
+            </section>
         </main>
         <footer>
             <a href="/"><img src="/logo.png" width="512" height="512" alt=""/>GrapheneOS</a>