1Hive DAO Kit brainstorm

[yeqbfgxjiq]

https://github.com/1Hive/grants/issues/8

1Hive DAO Kit summary:

• rewrite the model described in the handbook (roles, responsibilities, etc...) to something generic that can be applied to any community/organization
• create a DAO Template for that generalized organization
• create a Docusaurus around it explaining what it does, why, and how to customize and extend it

This will allow Aragon DAO developers to:

• read the guides on the 1Hive Template website (note: this is not 1Hive.org, but a different Docusaurus website for the 1Hive Template)
• fork the repo
• deploy and configure their DAO
• update and publish the Docusaurus website in the repo, but then update it information on their DAO vs the information describing the template (kind of like how currently docusaurus-init launches a template that you customize)

All in one sentence:

• A 1Hive DAO Template that allows Aragon DAO developers to deploy a 1Hive style DAO for their organization along with a Doucsaurus that provides user guides/onboarding, application docs, and a community hub for all your social channels including a built in blog.

This would accomplish a few things:

• it would make the 1Hive model accessible to the world
• it would create a standard docs template for all 1Hive apps
• it would be provide a foundation to do the same thing again when we ship the MolochDAO Suite

[yeqbfgxjiq]

Question

Maybe it makes more sense to create this as a monorepo?

• README as high level intro
• docs where the docs go
• apps where the code for the apps goes and gets automagically ported to the docs
• dao where the framework to deploy the DAO goes

Open Questions:

• would the apps folder actually need to live inside of the dao folder in order to be accessible to the DAO?
• is there a better way to roll this besides just forking the Autark TPS Launcher and modifying it to become a 1Hive DAO Launcher?

Answer to the question

Not rolling this as a monorepo. Instead using a sync script to pull docs/data in from other repos. This allows every repo to maintain their own code and docs, and then any DAO or Docusaurus can sync that in.

[yeqbfgxjiq]

Eventually something like the 0x Launch Kit would be ideal

• https://0x.org/launch-kit

And a GitHub page as cool as this

• https://github.com/nestjs/nest

[yeqbfgxjiq]

@lkngtn keeping this open as maybe some of this is relevant to the DAO template stuff?