Dive into Flow

docs/concepts/flix.md → docs/overview/dive-in/flix.md

@@ -1,6 +1,6 @@
 ---
-sidebar_position: 7
-sidebar_label: FLIX (FLIP 934)
+title: Proposals
+sidebar_position: 3
 ---
 
 # FLIX (FLIP 934)
@@ -22,4 +22,4 @@ Flow provides an implementation of the Flow interaction template service as an o
 There are currently two clients integrating FLIX APIs you can use in your code. 
 **Go client** [https://github.com/onflow/flixkit-go](https://github.com/onflow/flixkit-go)
 
-**FCL client you** read how to get started [tools/clients/fcl-js/interaction-templates](../tools/clients/fcl-js/interaction-templates.mdx)
+**FCL client you** read how to get started [tools/clients/fcl-js/interaction-templates](../../tools/clients/fcl-js/interaction-templates.mdx)

docs/building-on-flow/core-contracts/fungible-tokens.md → docs/overview/dive-in/fungible-tokens.md

@@ -1,3 +1,7 @@
+---
+title: Tokens 101
+sidebar_position: 1
+---
 
 # How to Launch a Fungible Token on Flow
 
@@ -42,7 +46,7 @@ For example, your users could be categorized in any of the following, non-exhaus
 
 You can also draw inspiration from this map of the Flow ecosystem. 
 
-![flow ecosystem](flow-ecosystem.png)
+![flow ecosystem](./flow-ecosystem.png)
 
 Write down the list that is most relevant to your dApp and for each type of user, outline succinctly what behavior is expected of them, and what will incentivize them to display this behavior. A good way to summarize the way users interact with your dApp (and with one another) is to draw up a flowchart showing the flow of incentives and behaviors for each user type. For now, ignore the token and only focus on the high-level behaviors/incentives.
 
@@ -165,11 +169,11 @@ While there are a number of ways you can split your token allocation. We have re
 - **Team**: 5-20%
 - **Advisors**: 0-5%
 
-![token allocation](token-allocation.png)
+![token allocation](./token-allocation.png)
 
 Importantly, this type of pie chart only captures **half** of the allocation picture. The other half consists of showing how each slice of the pie receives that allocation **over time**. This is where vesting/unlock comes in. Typically we see, an allocation over time that looks something like this:
 
-![token distribution](token-distribution.png)
+![token distribution](./token-distribution.png)
 
 In the example above, we’re using a 100 million fixed token supply model, and distributing the tokens on a 6-year timeline. The x-axis represents the years since launch, and the y-axis represents the token supply in circulation. As you can see, the number of tokens in circulating supply increases gradually over time and starts to taper off as we get closer to the 6-year mark. Token allocations for team members, investors, and advisors start vesting a year after launch at the cliff date, while airdrop, public sale, and community allocations unlock right at launch, at year zero.
 

docs/building-on-flow/governance.mdx → docs/overview/dive-in/governance.md

@@ -1,6 +1,7 @@
 ---
 title: Governance
 description: Learn about Flow's governance model and how it's empowering our community of users and builders.
+sidebar_position: 4
 sidebar_custom_props:
   icon: 🏛️
 ---

vercel.json

@@ -1019,6 +1019,21 @@
       "source": "/next/community-resources/projects",
       "destination": "/next/overview/getting-started/projects",
       "permanent": true
-    }
+    },
+    {
+      "source": "/next/building-on-flow/core-contracts/fungible-tokens",
+      "destination": "/next/overview/dive-in/fungible-tokens",
+      "permanent": true
+    },
+    {
+      "source": "/next/concepts/flix",
+      "destination": "/next/overview/dive-in/flix",
+      "permanent": true
+    },
+    {
+      "source": "/next/building-on-flow/governance",
+      "destination": "/next/overview/dive-in/governance",
+      "permanent": true
+    },
   ]
 }