[docsy] Promote Metadata section to top-level docs

Author: chalin

content/en/docs/faq.md

@@ -1,7 +1,7 @@
 ---
 title: Frequently Asked Questions
 LinkTitle: FAQ
-weight: 450
+weight: 800
 description: Get your questions answered!
 aliases: [/faq]
 ---

content/en/docs/overview/metadata.md renamed to content/en/docs/metadata.md

@@ -1,9 +1,7 @@
 ---
 title: Roles and Metadata
-LinkTitle: Metadata
-weight: 15
-description: Understand Roles and Metadata
 aliases: [/metadata]
+weight: 300
 ---
 
 TUF uses roles to define the set of actions a party can perform. The concept of
@@ -85,13 +83,13 @@ available from a given repository mirror.
 
 A delegated role file is located at:
 
-/DELEGATED_ROLE.json
+`/DELEGATED_ROLE.json`
 
 where DELEGATED_ROLE is the name of the role specified in targets.json. If this
 role further delegates trust to a role named ANOTHER_ROLE, that role's signed
 metadata file would be found at:
 
-/ANOTHER_ROLE.json
+`/ANOTHER_ROLE.json`
 
 See
 [example](https://raw.githubusercontent.com/theupdateframework/tuf/develop/tests/repository_data/repository/metadata/role1.json)

content/en/docs/overview/_index.md renamed to content/en/docs/overview.md

@@ -1,7 +1,7 @@
 ---
 title: Project
 aliases: [/project]
-weight: 400
+weight: 600
 ---
 
 The TUF project consists of three components:

content/en/docs/project/_index.md

@@ -35,5 +35,4 @@ four core principles continue to be central to its design.
   reduces the risk that they can be stolen or compromised. In 2016, the TUF
   research group set up a process whereby the community could
 
-[paper]:
-  https://theupdateframework.github.io/papers/survivable-key-compromise-ccs2010.pdf?raw=true
+[paper]: /papers/survivable-key-compromise-ccs2010.pdf

content/en/docs/project/history.md

@@ -1,6 +1,6 @@
 ---
 title: Security
-weight: 300
+weight: 400
 description: Security properties of TUF repositories
 aliases: [/security]
 ---