use explicit sections on the main page

This commit is contained in:
Daniel Micay 2020-12-06 12:27:24 -05:00
parent 11c2c70150
commit 73223bfda8

View File

@ -118,9 +118,8 @@
href="https://attestation.app/tutorial">tutorial</a>. These also support other href="https://attestation.app/tutorial">tutorial</a>. These also support other
operating systems.</p> operating systems.</p>
<h2 id="never-google-services"> <section id="never-google-services">
<a href="#never-google-services">No Google apps or services</a> <h2><a href="#never-google-services">No Google apps or services</a></h2>
</h2>
<p>GrapheneOS will never include either Google Play services or another implementation <p>GrapheneOS will never include either Google Play services or another implementation
of Google services like microG. Those are not part of the Android Open Source Project of Google services like microG. Those are not part of the Android Open Source Project
@ -160,10 +159,10 @@
monopolistic approach of forcing it to be bundled into the OS in a deeply integrated monopolistic approach of forcing it to be bundled into the OS in a deeply integrated
way with special privileged permissions and capabilities unavailable to other cloud way with special privileged permissions and capabilities unavailable to other cloud
service providers competing with them.</p> service providers competing with them.</p>
</section>
<h2 id="history"> <section id="history">
<a href="#history">History</a> <h2><a href="#history">History</a></h2>
</h2>
<p>GrapheneOS was founded by Daniel Micay in late 2014. It started as a solo project <p>GrapheneOS was founded by Daniel Micay in late 2014. It started as a solo project
incorporating his previous open source privacy/security work. The project initially incorporating his previous open source privacy/security work. The project initially
@ -207,10 +206,10 @@
AndroidHardening and then to GrapheneOS and it has continued down the original path of AndroidHardening and then to GrapheneOS and it has continued down the original path of
being an independent open source project. It will never again be closely tied to any being an independent open source project. It will never again be closely tied to any
particular sponsor or company.</p> particular sponsor or company.</p>
</section>
<h2 id="copyright-and-licensing"> <section id="copyright-and-licensing">
<a href="#copyright-and-licensing">Copyright and licensing</a> <h2><a href="#copyright-and-licensing">Copyright and licensing</a></h2>
</h2>
<p>The copyright for GrapheneOS code is entirely owned by the GrapheneOS developers <p>The copyright for GrapheneOS code is entirely owned by the GrapheneOS developers
and is made available under OSI-approved Open Source licenses. The upstream licensing and is made available under OSI-approved Open Source licenses. The upstream licensing
@ -237,10 +236,10 @@
GrapheneOS. GrapheneOS does not contain any code based on code under non-commercial GrapheneOS. GrapheneOS does not contain any code based on code under non-commercial
usage licensing. Great care was taken to avoid pulling in anything that was not solely usage licensing. Great care was taken to avoid pulling in anything that was not solely
owned by Daniel Micay, which was the case for nearly everything in the project.</p> owned by Daniel Micay, which was the case for nearly everything in the project.</p>
</section>
<h2 id="roadmap"> <section id="roadmap">
<a href="#roadmap">Roadmap</a> <h2><a href="#roadmap">Roadmap</a></h2>
</h2>
<p>Details on the roadmap of the project will be posted on the site in the near <p>Details on the roadmap of the project will be posted on the site in the near
future.</p> future.</p>
@ -271,12 +270,13 @@
<p>Hardware and firmware security are core parts of the project, but it's currently <p>Hardware and firmware security are core parts of the project, but it's currently
limited to research and submitting suggestions and bug reports upstream. In the long limited to research and submitting suggestions and bug reports upstream. In the long
term, the project will need to move into the hardware space.</p> term, the project will need to move into the hardware space.</p>
</section>
<h2 id="device-support"> <section id="device-support">
<a href="/faq#device-support">Device support</a> <h2><a href="/faq#device-support">Device support</a></h2>
</h2>
<p>See <a href="/faq#device-support">the FAQ section on device support</a>.</p> <p>See <a href="/faq#device-support">the FAQ section on device support</a>.</p>
</section>
</main> </main>
<footer> <footer>
<a href="/"><img src="/logo.png" width="512" height="512" alt=""/>GrapheneOS</a> <a href="/"><img src="/logo.png" width="512" height="512" alt=""/>GrapheneOS</a>