Merge pull request #58 from DA0-DA0/totallysarious-patch-1

Totallysarious patch 1

docs/dao-governance/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "DAO Governance",
+  "position": 3
+}

docs/configuration/_category_.json → docs/dao-governance/configuration/_category_.json

@@ -1,4 +1,4 @@
 {
   "label": "Configuration",
-  "position": 5
+  "position": 1
 }

docs/configuration/proposal-submission.md → docs/dao-governance/configuration/proposal-submission.md

@@ -4,20 +4,13 @@ sidebar_position: 2
 
 # Proposal submission
 
-A DAO's proposal submission configuration manages the rules around submitting a
-proposal for voting.
+A DAO's proposal submission configuration manages the rules around submitting a proposal for voting.
 
 ## How to update the proposal submission configuration
 
-To change the proposal submission configuration of a DAO, you must submit a
-[governance proposal](/features/proposals/what) containing the `Update Proposal
-Submission Config` action from the `DAO Governance` category.
+To change the proposal submission configuration of a DAO, you must submit a [governance proposal](../proposals/what.md) containing the `Update Proposal Submission Config` action from the `DAO Governance` category.
 
-If you have multiple choice proposals enabled, you will instead see two
-different actions, one labeled `Update Single Choice Proposal Submission Config`
-and the other `Update Multiple Choice Proposal Submission Config`. You may
-configure each proposal type (single and multiple choice) separately, though
-they should probably be kept in sync so the voting experience is consistent.
+If you have multiple choice proposals enabled, you will instead see two different actions, one labeled `Update Single Choice Proposal Submission Config` and the other `Update Multiple Choice Proposal Submission Config`. You may configure each proposal type (single and multiple choice) separately, though they should probably be kept in sync so the voting experience is consistent.
 
 ## Parameters
 
@@ -26,9 +19,7 @@ time.
 
 ### Proposal deposit
 
-This is a required deposit someone must put down to create a proposal. This can
-be the DAO's governance token, if it exists, or any other token on the chain. By
-default, this is disabled.
+This is a required deposit someone must put down to create a proposal. This can be the DAO's governance token, if it exists, or any other token on the chain. By default, this is disabled.
 
 #### Refunding proposal deposits
 

docs/dao-governance/configuration/staking.md

@@ -0,0 +1,19 @@
+---
+sidebar_position: 3
+---
+
+# Staking
+
+A DAO's staking configuration determines the rules of the token staking process. Only token-based and NFT-based DAOs have a staking process to configure. Member-based DAOs do not have staking because they do not use tokens.
+
+## How to update the staking configuration
+
+To change the staking configuration of a DAO, you must submit a [governance proposal](../proposals/what.md) containing the `Update Staking Config` action from the `DAO Governance` category.
+
+## Parameters
+
+### Unstaking duration
+
+After someone stakes tokens in a DAO, those tokens cannot be immediately unstaked. The unstaking duration is how long they remain locked after deciding to unstake. During the unstaking process, they do _not_ count towards your voting power, and you cannot transfer them.
+
+This adds a time cost to staking and ensures a greater level of participatory commitment from members.

docs/dao-governance/configuration/voting-config.md

@@ -0,0 +1,75 @@
+---
+sidebar_position: 1
+---
+
+# Voting
+
+A DAO's voting configuration determines the rules of the voting process. Things like the passing threshold and voting duration.
+
+## How to update the voting configuration
+
+To change the voting configuration of a DAO, you must submit a [governance proposal](../proposals/what.md) containing the `Update Voting Config` action from the `DAO Governance` category.
+
+If you have multiple choice proposals enabled, you will instead see two different actions, one labeled `Update Single Choice Voting Config` and the other `Update Multiple Choice Voting Config`. You may configure each proposal type (single and multiple choice) separately, though they should probably be kept in sync so the voting experience is consistent.
+
+## Parameters
+
+You can update all of these parameters with the action(s) mentioned above at any time.
+
+### Passing threshold and quorum
+
+The **_passing threshold_** is the `Yes` threshold needed to pass a proposal. It defaults to majority (i.e. any votes above 50%). It sounds simple, but it gets trick very fast because it works differently depending on whether or not the quorum is enabled.
+
+The **_quorum_** is the proportion of all voting power that must vote for a proposal to be **passable**. It defaults to 20%. For single choice proposals, quorum can be disabled.
+
+#### Multiple choice proposals
+
+Multiple choice proposals use quorum in the same way, but they do not have a passing threshold. Instead, as long as the quorum is met, whichever option received more votes (i.e. the plurality of votes) wins. You cannot disable quorum for multiple choice proposals.
+
+Read on to understand how passing threshold and quorum affect each other for single choice proposals.
+
+#### With quorum enabled
+
+If your DAO has a quorum set, the passing threshold is only calculated among **those who voted**.
+
+For example, with a quorum of 40% and a passing threshold of 75%, a proposal could pass with only 30% of the total voting power having voted `Yes` if exactly 40% of voters vote. Imagine: 40% of the total voting power votes on the proposal. Quorum is met. Of those who voted, 75% vote `Yes`. The rest of the votes are split between `Abstain` and `No`. `Yes` will have won the vote with a 75% threshold of quorum, even though only 30% of the _total_ voting power voted `Yes`.
+
+Setting quorum to 0% means that any single voter can pass a proposal by themself. _This is different from disabling quorum._
+
+:::tip
+
+Enabling a quorum helps when there is a risk of low participation in a DAO. Large token-based DAOs likely face this risk as membership is fluid and attention is finite. Setting a quorum low enough ensures that the DAO cannot be locked due to lack of sufficient participation. However, setting a quorum too low can lead to proposals passing that do not represent enough member's preferences (if not enough people are paying attention).
+
+:::
+
+#### With quorum disabled
+
+If your DAO has no quorum set, the passing threshold is calculated among **all possible voters**. This is considered an absolute threshold.
+
+For example, with a passing threshold of 67%, a proposal will pass if 67% of the total voting power voted `Yes`.
+
+:::caution
+
+Threshold and quorum can be very confusing. Please be careful and check your understanding with others before making any changes.
+
+:::
+
+### Only members execute
+
+If enabled, only members may execute passed proposals. If disabled, anyone can. This defaults to enabled.
+
+### Voting duration
+
+This is the maximum time proposals remain open for voting.
+
+### Allow revoting
+
+If enabled, votes can be changed before the voting duration ends. This defaults to disabled.
+
+:::tip
+
+When this is enabled, proposals always remain open for their entire duration. This is because the proposal outcome cannot be determined if votes can be changed.
+
+When this is disabled, proposals will pass or fail early if sufficient voters cast votes to determine an outcome.
+
+:::

docs/features/proposals/_category_.json → docs/dao-governance/proposals/_category_.json

@@ -1,4 +1,4 @@
 {
   "label": "Proposals",
-  "position": 1
+  "position": 2
 }

docs/how-to/how-to-create-a-proposal.md → docs/dao-governance/proposals/how-to-create-a-proposal.md

@@ -1,24 +1,20 @@
 ---
-sidebar_position: 1
+sidebar_position: 3
 ---
 
 # How to create a proposal
 
-If you don't know what a proposal is, read the [proposal explanation
-doc](/features/proposals/what) first.
+If you don't know what a proposal is, read the [proposal explanation doc](../what.md) first.
 
 :::note
 
-Members must join the DAO before a proposal is made in order to vote on it.
-Membership changes during a proposal's voting period are ignored as they only
-apply to future proposals.
+Members must join the DAO before a proposal is made in order to vote on it. Membership changes during a proposal's voting period are ignored as they only apply to future proposals.
 
 :::
 
 ## Steps
 
-To begin, starting from your DAO's page, navigate to **Proposals > New
-Proposal**.
+To begin, starting from your DAO's page, navigate to **Proposals > New Proposal**.
 
 ![Create proposal button](/img/how-to/proposals-tab.png)
 
@@ -28,20 +24,15 @@ Then, fill in the proposal's name, description, and actions (if needed).
 
 :::tip What is an action?
 
-[Proposal actions](/features/proposals/what#actions) allow you to add rich
-functionality to proposals: software instructions that execute on the blockchain
-when a proposal is passed and executed. Read the [proposal
-docs](/features/proposals/what) to learn more.
+[Proposal actions](../what.md#actions) allow you to add rich functionality to proposals: software instructions that execute on the blockchain when a proposal is passed and executed. Read the [proposal docs](../what.md) to learn more.
 
 :::
 
-If you want to create a multiple choice proposal, check out the [multiple choice
-proposal docs](/features/proposals/types#multiple-choice).
+If you want to create a multiple choice proposal, check out the [multiple choice proposal docs](../types.md#multiple-choice).
 
 To preview how the proposal will look once its created, press **Preview**.
 
-Once you are satisfied with the proposal, press **Publish**. Your wallet will
-prompt you to approve the transaction.
+Once you are satisfied with the proposal, press **Publish**. Your wallet will prompt you to approve the transaction.
 
 Once you approve it, your proposal will be live and the DAO members can vote on it!
 

docs/how-to/how-to-vote-on-a-proposal.md → docs/dao-governance/proposals/how-to-vote-on-a-proposal.md

@@ -1,16 +1,14 @@
 ---
-sidebar_position: 2
+sidebar_position: 4
 ---
 
 # How to vote on a proposal
 
-Once you've [created a proposal](/how-to/how-to-create-a-proposal), members of
-the DAO need to vote on it.
+Once you've [created a proposal](../how-to-create-a-proposal.md), members of the DAO need to vote on it.
 
 ## Steps
 
-To begin, starting from your DAO's page, navigate to the proposal from the
-**Proposals** tab.
+To begin, starting from your DAO's page, navigate to the proposal from the **Proposals** tab.
 
 ![Proposals tab](/img/how-to/proposals-tab-with-proposals.png)
 
@@ -22,11 +20,8 @@ Click on the desired vote option on the left side of the page.
 
 ![Vote options](/img/how-to/single-choice-proposal-vote-options.png)
 
-Click on the **Cast your vote** button to submit your vote. Approve the
-transaction in your wallet to confirm submission.
+Click on the **Cast your vote** button to submit your vote. Approve the transaction in your wallet to confirm submission.
 
 ![Proposal still open](/img/how-to/open-proposal-already-voted.png)
 
-The proposal will be updated with your vote. If your vote was sufficient to pass
-or fail the proposal, it will now be complete. Since this proposal's outcome has
-not yet been determined, it is still open for voting.
+The proposal will be updated with your vote. If your vote was sufficient to pass or fail the proposal, it will now be complete. Since this proposal's outcome has not yet been determined, it is still open for voting.