# MolochDAO Documentation Specs

###### tags: `MolochDAO` `RaidGuild`

## Scope

* A raid party formed to research DAO handbooks and write technical docs for the ReallyBoringGuild of MolochDAO
* Spearheaded by Travis Wyche and earth2travis of the Wordsmiths RG working group, but open to other contributors (rangers, scribes, etc.)
* Documentation work will be performed throughout October
* Possibly leading to design/dev work: MolochDAO design system, website reboot, docusaurus/git handbook, identification of new working groups within MolochDAO, etc.

## Deliverables

### Initial Research:

* UX and content audit of existing DAO handbooks, to glean specific information from each, in a form TBD (research report tailored to Moloch's needs):
* **MetaCartel**: grant pipeline procedures
* **RaidGuild**: structuring internal working groups, compensation flows
* **DAOhaus**: technical tutorials on how to operate a v2 Moloch on their platform
* **UberHaus**: DAO-to-DAO relations
* **MetaGame**: lore, mythology of the Ethereu world computer, how the vision/poiesis manifests into utilitarian action/praxis
* **LexDAO/the LAO**: legal considerations, MC-style "grimoire"?
* Very open to other DAO docs or even outside/obscure references for inspiration!

### Documentation > Handbook Components

* **Technical operating procedures** of a v2 Moloch, written for existing and new MolochDAO members so they know how to operate the DAO, tutorials (appropriated from DAOhaus docs)
* MolochDAO **membership policies** (appropriated from other influential/successful DAOs like Metacartel, RG, etc., but adapted to our specific needs): codes of conduct, brand management, and clearly articulated (user friendly) procedures for:
* onboarding to the DAO
* onboarding to RBG (if it still exists) and articulate relation to the DAO
* applying to RFPs (via RBG)
* applying for grants (via the DAO)
* RBG policies separate from DAO policies? (informed by sub-DAOs or working groups operating in other DAOs)
* concrete research to identify potential **DAO/cultural relations** for existing and future MolochDAO members

### Budget

* TBD, but coming from the ReallyBoringGuild ops treasury (not a separate MolochDAO grant).
* Elastic: can support many contributors if needed; quality and crafting an impactful, lasting legacy is highest priority

---

Appendix

## Sample Documentation 'Audit'
> A sample framework to audit documentations, so we can standardise and draw meaningful similarities and differences across different docs

* Profile/Objective: What does the organisation do? (Non-mutually exclusive)
* Product: The organisation provides software or product to users / developers.
* Guilds/Community: The organisation is a community/guild for community members
* Objective: What does the documentation aim to do
* Manifesto/Vision: Mission, vision, manifestos
* User Education: Feature explainers, glossary, how things work
* Instructions: Tutorials, handbook
* User Persona
* Users (New users? Advanced users?)
* Developers
* Community Members
* Contributors (Developers? Non-devs?)
* Docs Platform
* Docusaurus / Gitbook / README on Github
* Docs Structure
* Contribution Processes: Does the process exist if any?
* Process
* Platform
* Incentives
* Any other analysis

## DAOhaus Documentation 'Audit'
* **Profile**
* DAOhaus is mainly a product organisation creating and providing the DAOhaus software for its users
* While it has a UberHaus (a community/DAO), documentation is kept separate
* **Objective**
* DAOhaus' docs serve all 3 purposes, but have a stronger slant towards user education & instructions
* **User Persona**
* Users: The DAOhaus docs caters to different savviness and personas for users
| Persona/Advancements | New | Advanced |
| ----------------------- | ---------------------------------- |:--------------------------------------------------------------------- |
| Users | https://daohaus.club/docs | FAQ pages [(example)](https://daohaus.club/docs/users/proposals-faq) |
| Devs | https://daohaus.club/docs/devs | - |
| Summoners (Handbook) | https://daohaus.club/docs/handbook | - |
| Contributors (Handbook) | https://daohaus.club/docs/handbook | - |
* **Docs Platform**: Docusaurus (Github Repo: https://github.com/HausDAO/daohaus-website)
* **Docs Structure**:
* The docs structure is split up into 3 user personas: User, Devs & Handbook (Special user types, e.g. Summoners/Contributors)
* The User Docs have general information for all users of DAOhaus, while the Handbook dives into more specific information for a particular persona (e.g. Contributors / Summoners)
* Within each section, there are Features, Tutorials and FAQ
* Features are for general explainers for user education, tutorials are instructions for user support, and FAQ are catch-alls (which are meant to be constantly pruned into Features / Tutorials)

>Here's a diagram, labels are a bit outdated though

* **Contribution Process**: A documentation process was set up, but the push to recruit & decentralise contributors was paused to prioritise the actual updating of docs with new feature updates.
* Team: Mainly maintained by arentweall & bau
* Process: Yes
* Platform: Via Github Issues
* Incentives: Not set up yet

**Analysis**
Pros
Cons