# Notes on Handbook Repo with Jonathan(jp)

* Changes are made through PR (pull requests)
* Can designate multiple reviewers, akin to multiple signers on a multisig - this is a threshold that needs to be considered for efficiency
* Docusaurus allows for greater visual variables than Gitbook - requires some knowledge of CSS and React
* For policy changes: consensus is gathered on Discord, discussed internally, and relayed to reviewers to set alignment for how to review PR to the repo
* RBG needs to figure out how the reviewer submissions will work: who will we nominate?
* Let's pull in earth2travis and Amos (arentweall) to consult as well - they set up the DAOhaus docs. Do they use command line or the Github UI?

#### Visual Design Elements for the Docusaurus
* Color Palette
* Typography
* Logo in png and svg
* Reference: Figma Chakra UI and Felipe's UberHaus design system + mood board **Contact Felipe for perms using the UH design system**
#### Technical Junk
* Nextra? or Next.js? or Docusaurus? Let's stay away from Gatsby
* Integration with RG's token-gated access? via Nextra
* Next.js is a full customizable framework, docs are markdown. Might be more flexible than Docusaurus
* Docusaurus supports MDX