Todos before defi hackathon

[barbaraliau]

Putting this in a more public place than my notebook. This is a living issue so I don't make n number of issues for every single one.

"Claim" an item by putting your name in front of it in bold and the status.

Homepage

• Update so CTA goes to Getting Started

ERTP

• Complete ERTP glossary

  • path: /ertp/glossary/README.md

• Move ExtentOps API into own file and place underneath UnitOps in the sidebar

• Pull Assay, Payments, Purse sections into own files

  • Assay
  • Payments
  • Purse

• Pull out definitions from UnitOps and place into /ertp/guide/. Makes much more sense to put it there. API should only contain the methods.

• Pull out 'Gotchas' from ERTP guide and put into own sections

• Complete any missing examples in ERTP

• Add the following methods to Payments API - A payment's balance can only fall, through the action of `depositExactly()`, `claimExactly()` or `burnExactly()`. Payments can be converted to Purses by getting a verified assay and calling `assay.makeEmptyPurse().depositAll(payment)`;

• BAR: starting Finish default-configuration file

• DOM: PR pending. Almost complete. Have questions/comments (see red text). ContractHost API [contractHost.chainmal)(https://github.com/Agoric/ERTP/blob/master/core/contractHost.chainmail)

• Finish unitOps.make(allegedExtent) params definition

• line 106 /ertp/api/contract-hosts.md - write and verify example - Chris

• line 128 /ertp/api/contract-hosts.md - verify description -Chris

Zoe

• KATE: STARTING Complete Zoe glossary
  • path: /zoe/glossary/README.md
• DOM: in progress zoe.chainmail -> Zoe API
• Check this: Zoe and ZoeContractFacet have some similar methods so those examples are the same. Those should be double-checked to make sure they are accurate in both locations. Methods: getInviteAssay, getEscrowReceiptAssay
• verify zcf.getSeatAssay() example - Couldn't find an example in the code, this needs checking.
• verify zoe.getInviteAssay()

Add Other Projects
Projects Reference
The most relevant of these project's documentation should be pulled out and placed into the site. The less relevant projects can have external links

• Add definitions for each project (maybe in like a master project list page? not sure yet)
• Make nested navbar

Site

• BAR: in process Add favicon

Proofreading:

• Add missing code markdowns
• Review for typos
• Verify links
• Verify navbar
• Verify sidebars