I think it makes sense to first create the content.
Then anyone can fork the repo and just roll it out themselves.
As the project progresses there will be more user friendly and fast ways to deploy the org/dao.
[x] Mirror the basic structure of 1Hive.org into the 1Hive DAO Kit Docusaurus
contributing
docs
guides
blog
etc...
[ ] Create generic/standard templates for documentation and guides.
[ ] Go through everything and rewrite it to conform to the be generic/standard templates. Also re-write the content so that any DAO/organization can use the same roles/features/architecture without the hive specific names/themes.
[ ] Create a web based DAO deployment template like what Aragon and Autark created. This will make creation of the 1Hive DAO model as accessible as possible to a wide audience (web > CLI).
[ ] Create a CLI based DAO deployment template so that people can easily and quickly set up the 1Hive DAO permissions and accounts without spending a day clicking through everything.
I think it makes sense to first create the content. Then anyone can fork the repo and just roll it out themselves. As the project progresses there will be more user friendly and fast ways to deploy the org/dao.