w3f · lsaether · Sep 25, 2020 · Sep 14, 2020 · Sep 15, 2020 · Sep 15, 2020
diff --git a/docs/assets/identity/01.jpg b/docs/assets/identity/01.jpg
diff --git a/docs/assets/identity/02.jpg b/docs/assets/identity/02.jpg
diff --git a/docs/assets/identity/03.jpg b/docs/assets/identity/03.jpg
diff --git a/docs/assets/identity/04.jpg b/docs/assets/identity/04.jpg
diff --git a/docs/assets/identity/05.jpg b/docs/assets/identity/05.jpg
diff --git a/docs/assets/identity/06.jpg b/docs/assets/identity/06.jpg
diff --git a/docs/assets/identity/07.jpg b/docs/assets/identity/07.jpg
diff --git a/docs/assets/identity/08.jpg b/docs/assets/identity/08.jpg
diff --git a/docs/assets/identity/09.jpg b/docs/assets/identity/09.jpg
diff --git a/docs/assets/identity/10.jpg b/docs/assets/identity/10.jpg
diff --git a/docs/assets/identity/11.jpg b/docs/assets/identity/11.jpg
diff --git a/docs/assets/identity/12.jpg b/docs/assets/identity/12.jpg
diff --git a/docs/assets/identity/13.jpg b/docs/assets/identity/13.jpg
diff --git a/docs/assets/identity/14.jpg b/docs/assets/identity/14.jpg
diff --git a/docs/assets/identity/15.jpg b/docs/assets/identity/15.jpg
diff --git a/docs/assets/identity/16.jpg b/docs/assets/identity/16.jpg
diff --git a/docs/assets/identity/clear.gif b/docs/assets/identity/clear.gif
diff --git a/docs/assets/new-claims/claim-1.jpg b/docs/assets/new-claims/claim-1.jpg
diff --git a/docs/assets/new-claims/claim-1.png b/docs/assets/new-claims/claim-1.png
diff --git a/docs/assets/new-claims/claim-10.jpg b/docs/assets/new-claims/claim-10.jpg
diff --git a/docs/assets/new-claims/claim-10.png b/docs/assets/new-claims/claim-10.png
diff --git a/docs/assets/new-claims/claim-2-1.jpg b/docs/assets/new-claims/claim-2-1.jpg
diff --git a/docs/assets/new-claims/claim-2-1.png b/docs/assets/new-claims/claim-2-1.png
diff --git a/docs/assets/new-claims/claim-2.jpg b/docs/assets/new-claims/claim-2.jpg
diff --git a/docs/assets/new-claims/claim-2.png b/docs/assets/new-claims/claim-2.png
diff --git a/docs/assets/new-claims/claim-7.jpg b/docs/assets/new-claims/claim-7.jpg
diff --git a/docs/assets/new-claims/claim-7.png b/docs/assets/new-claims/claim-7.png
diff --git a/docs/assets/new-claims/claim-8.jpg b/docs/assets/new-claims/claim-8.jpg
diff --git a/docs/assets/new-claims/claim-8.png b/docs/assets/new-claims/claim-8.png
diff --git a/docs/assets/new-claims/claim-9.jpg b/docs/assets/new-claims/claim-9.jpg
diff --git a/docs/assets/new-claims/claim-9.png b/docs/assets/new-claims/claim-9.png
diff --git a/docs/assets/new-claims/new-attest-1.jpg b/docs/assets/new-claims/new-attest-1.jpg
diff --git a/docs/assets/new-claims/new-attest-1.png b/docs/assets/new-claims/new-attest-1.png
diff --git a/docs/assets/new-claims/new-attest-3.jpg b/docs/assets/new-claims/new-attest-3.jpg
diff --git a/docs/assets/new-claims/new-attest-3.png b/docs/assets/new-claims/new-attest-3.png
diff --git a/docs/assets/new-claims/new-attest-4.jpg b/docs/assets/new-claims/new-attest-4.jpg
diff --git a/docs/assets/new-claims/new-attest-4.png b/docs/assets/new-claims/new-attest-4.png
diff --git a/docs/assets/new-claims/new-attest-5.jpg b/docs/assets/new-claims/new-attest-5.jpg
diff --git a/docs/assets/new-claims/new-attest-5.png b/docs/assets/new-claims/new-attest-5.png
diff --git a/docs/assets/new-claims/ps-claim-1.jpg b/docs/assets/new-claims/ps-claim-1.jpg
diff --git a/docs/assets/new-claims/ps-claim-1.png b/docs/assets/new-claims/ps-claim-1.png
diff --git a/docs/assets/new-claims/ps-claim-4.png b/docs/assets/new-claims/ps-claim-4.png
diff --git a/website/static/img/treasury/constants.jpg → docs/assets/treasury/constants.jpg b/website/static/img/treasury/constants.jpg → docs/assets/treasury/constants.jpg
diff --git a/website/static/img/treasury/motion.jpg → docs/assets/treasury/motion.jpg b/website/static/img/treasury/motion.jpg → docs/assets/treasury/motion.jpg
diff --git a/docs/assets/treasury/new-council.jpg b/docs/assets/treasury/new-council.jpg
diff --git a/docs/assets/treasury/new-motion.jpg b/docs/assets/treasury/new-motion.jpg
diff --git a/docs/assets/treasury/new-proposal.jpg b/docs/assets/treasury/new-proposal.jpg
diff --git a/website/static/img/treasury/proposal.jpg → docs/assets/treasury/proposal.jpg b/website/static/img/treasury/proposal.jpg → docs/assets/treasury/proposal.jpg
diff --git a/website/static/img/treasury/propose.jpg → docs/assets/treasury/propose.jpg b/website/static/img/treasury/propose.jpg → docs/assets/treasury/propose.jpg
diff --git a/docs/claims.md b/docs/claims.md
@@ -63,16 +63,16 @@ maximum security), you can start by navigating to the Claims app on Polkadot-JS
 account you would like to claim the DOT into and click the blue "Continue" button to proceed. Your
 screen should look something like this:
 
-![claim-1](assets/new-claims/claim-1.png)
+![claim-1](assets/new-claims/claim-1.jpg)
 
 Now you will need to provide the Ethereum address that is associated with the DOT indicator tokens
 that you will claim. Enter the Ethereum address into the box and click "Continue".
 
-![claim-2](assets/new-claims/claim-2.png)
+![claim-2](assets/new-claims/claim-2.jpg)
 
 Next your screen should look the image below.
 
-![claim-2-1](assets/new-claims/claim-2-1.png)
+![claim-2-1](assets/new-claims/claim-2-1.jpg)
 
 The hex-encoded string that follows the sentence: "Pay DOT to the Polkadot account:" is the
 hex-encoded public key of your Polkadot account, minus the `0x` prefix.
@@ -96,12 +96,12 @@ When you click "Sign Message" you will get a JSON output like the one below:
 Copy and paste the JSON output of the signed message from MyCrypto into the input box on the
 Polkadot-JS UI and click "Confirm Claim."
 
-![claim-7](assets/new-claims/claim-7.png) ![claim-8](assets/new-claims/claim-8.png)
+![claim-7](assets/new-claims/claim-7.jpg) ![claim-8](assets/new-claims/claim-8.jpg)
 
 A green box will appear telling you the amount to claim with a "Claim" button to make the claim.
 Click on the "Claim" button and click "Submit (no signature)" to complete the claim.
 
-![claim-9](assets/new-claims/claim-9.png)
+![claim-9](assets/new-claims/claim-9.jpg)
 
 If this claim succeeded, then you will see a success message and your DOT will be in the account
 that you claimed to.
@@ -113,7 +113,7 @@ immediately.
 
 Having trouble? Get support in the DOT [Claims Support][] channel.
 
-![claim-10](assets/new-claims/claim-10.png)
+![claim-10](assets/new-claims/claim-10.jpg)
 
 Congratulations, you have now completed the process for claiming and signing for your DOT.
 
@@ -152,7 +152,7 @@ entering it directly to the Apps page.
 After entering your account, you should see a red counter appear on the "Claim Tokens" tab on the
 left navigation drawer.
 
-![claim-attest-1](assets/new-claims/new-attest-1.png)
+![claim-attest-1](assets/new-claims/new-attest-1.jpg)
 
 Click on the "Claim Tokens" tab and you will see a large notification at the top of the page that
 tells you that you need to sign an attestation.
@@ -167,15 +167,15 @@ free to reach out for help in the [Claims Support][] channel.
 
 Click "Continue" and you will see a green box appear on the right.
 
-![claim-attest-3](assets/new-claims/new-attest-3.png)
+![claim-attest-3](assets/new-claims/new-attest-3.jpg)
 
-![claim-attest-4](assets/new-claims/new-attest-4.png)
+![claim-attest-4](assets/new-claims/new-attest-4.jpg)
 
 Click on "I Agree" and then "Sign and Submit" to make your free attest transaction. When the
 transaction is included in the block, you will see a green success box appear in the upper right
 corner and the DOT will be in your account.
 
-![claim-attest-5](assets/new-claims/new-attest-5.png)
+![claim-attest-5](assets/new-claims/new-attest-5.jpg)
 
 ## Using Parity Signer
 
@@ -197,7 +197,7 @@ the Accounts page first.
 
 ### Make the Attestation
 
-![ps-claim-1](assets/new-claims/ps-claim-1.png)
+![ps-claim-1](assets/new-claims/ps-claim-1.jpg)
 
 Click "Add via Qr" on the right side.
 
@@ -220,9 +220,7 @@ Polkadot-JS Apps can decode it.
 
 Once decoded successfully, input the name for your address and click "Create".
 
-![ps-claim-4](assets/new-claims/ps-claim-4.png)
-
-You will notice that the digit beside the "Claim Tokens" menu changed to 2. It means the number of
+You will notice that the digit beside the "Claim Tokens" menu increased by 1. It means the number of
 addresses on the Accounts page that need to do attestations.
 
 Go to the [Claim Tokens](https://polkadot.js.org/apps/#/claims) page and and you will see a large

diff --git a/docs/learn-identity.md b/docs/learn-identity.md
@@ -22,11 +22,11 @@ information, so the data must be less than that. When inputting the data manuall
 The easiest way to add the built-in fields is to click the gear icon next to one's account and
 select "Set on-chain identity".
 
-![Gear icon provides the option to set identity](/img/identity/01.jpg)
+![Gear icon provides the option to set identity](assets/identity/01.jpg)
 
 A popup will appear, offering the default fields.
 
-![Identity field setup popup](/img/identity/02.jpg)
+![Identity field setup popup](assets/identity/02.jpg)
 
 To add custom fields beyond the default ones, use the Extrinsics UI to submit a raw transaction by
 first clicking "Add Item" and adding any field name you like. The example below adds a field
@@ -37,18 +37,18 @@ it with the "None" option still selected. That is to say, every time you make a
 identity values, you need to re-submit the entire set of fields: the write operation is always
 "overwrite", never "append".
 
-![Setting a custom field](/img/identity/03.jpg)
+![Setting a custom field](assets/identity/03.jpg)
 
 Note that custom fields are not shown in the UI by default:
 
-![Only built-in fields are shown](/img/identity/04.jpg)
+![Only built-in fields are shown](assets/identity/04.jpg)
 
 The rendering of such custom values is, ultimately, up to the UI/dapp makers. In the case of
 PolkadotJS, the team prefers to only show official fields for now. If you want to check that the
 values are still stored, use the [Chain State UI](https://polkadot.js.org/apps/#/chainstate) to
 query the active account's identity info:
 
-![Raw values of custom fileds are available on-chain](/img/identity/05.jpg)
+![Raw values of custom fileds are available on-chain](assets/identity/05.jpg)
 
 It is up to your own UI or dapp to then do with this data as it pleases. The data will remain
 available for querying via the Polkadot API, so you don't have to rely on the PolkadotJS UI.
@@ -86,7 +86,7 @@ Here's how to submit a proposal to become a registrar:
 Go to the Democracy tab, select "Submit preimage", and input the information for this motion -
 notably which account you're nominating to be a registrar in the `identity.setRegistrar` function.
 
-![Setting a registrar](/img/identity/12.jpg)
+![Setting a registrar](assets/identity/12.jpg)
 
 Copy the preimage hash. In the above image, that's
 `0x90a1b2f648fc4eaff4f236b9af9ead77c89ecac953225c5fafb069d27b7131b7`. Submit the preimage by signing
@@ -97,7 +97,7 @@ field needs to be at least 10 KSM. You can find out the minimum by querying the
 [Chain State](https://polkadot.js.org/apps/#/chainstate) -> Constants -> democracy ->
 minimumDeposit.
 
-![Submitting a proposal](/img/identity/13.jpg)
+![Submitting a proposal](assets/identity/13.jpg)
 
 At this point, DOT holders can second the motion. With enough seconds, the motion will become a
 referendum, which is then voted on. If it passes, users will be able to request judgement from this
@@ -135,7 +135,7 @@ for the `max_fee` put the maximum you're willing to pay for these confirmations.
 If you don't know which registrar to pick, first check the available registrars by going to
 ["Chain State UI"]() and selecting `identity.registrars()` to get the full list.
 
-![Showing all registrars](/img/identity/14.jpg)
+![Showing all registrars](assets/identity/14.jpg)
 
 The image above reveals two registrars:
 
@@ -146,23 +146,23 @@ To find out how to contact the registrar after the application for judgement or
 are, we can check their identity by adding them to our Address Book. Their identity will be
 automatically loaded.
 
-![Gav is a registrar](/img/identity/15.jpg)
+![Gav is a registrar](assets/identity/15.jpg)
 
 Gavin Wood is registrar #0.
 
-![Chevdor is registrar #1](/img/identity/16.jpg)
+![Chevdor is registrar #1](assets/identity/16.jpg)
 
 Chevdor is registrar #1. We pick that one.
 
-![Requesting judgement](/img/identity/08.jpg)
+![Requesting judgement](assets/identity/08.jpg)
 
 This will make your identity go from unjudged:
 
-![An unjudged identity](/img/identity/07.jpg)
+![An unjudged identity](assets/identity/07.jpg)
 
 To "waiting":
 
-![A pending identity](/img/identity/09.jpg)
+![A pending identity](assets/identity/09.jpg)
 
 At this point, direct contact with the registrar is required - the contact info is in their identity
 as shown above. Each registrar will have their own set of procedures to verify your identity and
@@ -171,7 +171,7 @@ values, and only once you've satisfied their requirements will the process conti
 Once the registrar has confirmed the identity, a green checkmark should appear next to your account
 name with the appropriate confidence level:
 
-![A confirmed identity](/img/identity/10.jpg)
+![A confirmed identity](assets/identity/10.jpg)
 
 _Note that changing even a single field's value after you've been verified will un-verify your
 account and you will need to start the judgement process anew. However, you can still change fields
@@ -194,7 +194,7 @@ parent sender account. The value to put into the Data field of each parent is th
 the sub-account. If omitted, the sub-account will inherit the parent's name and be displayed as
 `parent/parent` instead of `parent/child`.
 
-![Sub account setup](/img/identity/06.jpg)
+![Sub account setup](assets/identity/06.jpg)
 
 Note that a deposit of 2.5KSM is required for every sub-account.
 
@@ -203,7 +203,7 @@ Note that a deposit of 2.5KSM is required for every sub-account.
 **Clearing:** Users can clear their identity information and have their deposit returned. Clearing
 an identity also clears all sub accounts and returns their deposits.
 
-![Clearing an identity](/img/identity/clear.gif)
+![Clearing an identity](assets/identity/clear.gif)
 
 Clearing is done through the [Extrinsics UI](https://polkadot.js.org/apps/#/extrinsics).
 

diff --git a/docs/learn-treasury.md b/docs/learn-treasury.md
@@ -95,15 +95,15 @@ One way to create the proposal is to use the Polkadot-JS Apps
 `proposeSpend` and enter the desired amount and recipient, or use the
 [Treasury tab](https://polkadot.js.org/apps/#/treasury) and its dedicated Submit Proposal button:
 
-![An example of a proposal being created](/img/treasury/propose.jpg)
+![An example of a proposal being created](assets/treasury/propose.jpg)
 
 The system will automatically take the required deposit, picking the higher of the following two
 values: 20 KSM or 5% of the requested amount.
 
 Once created, your proposal will become visible in the Treasury screen and the council can start
 voting on it.
 
-![A pending proposal](/img/treasury/proposal.jpg)
+![A pending proposal](assets/treasury/new-proposal.jpg)
 
 Remember that the proposal has no metadata, so it's up to the proposer to create a description and
 purpose that the council could study and base their votes on.
@@ -114,7 +114,9 @@ After being turned into a council motion, the proposal needs 51% of the council
 pass, or 51% to reject it to fail. If majority is not reached, the proposal remains in limbo -
 neither accepted nor rejected until more council members weigh in.
 
-![Motion in action](/img/treasury/motion.jpg)
+![Council](assets/treasury/new-council.jpg)
+
+![Motion in action](assets/treasury/new-motion.jpg)
 
 ## Tipping
 

diff --git a/website/static/img/identity/01.jpg b/website/static/img/identity/01.jpg
diff --git a/website/static/img/identity/new1.jpg b/website/static/img/identity/new1.jpg
diff --git a/website/static/img/identity/new2.jpg b/website/static/img/identity/new2.jpg