Update collections/dy_intro/dunia_yetu/dunia_yetu.md

* 'development' of git.ourworld.tf:tfgrid/info_tfgrid:
  s

CODEOWNERS

@@ -0,0 +1 @@
+* @despiegk @mik-tf @gosam @scott

README.md

@@ -6,7 +6,11 @@
 - [Basic Hero mdBook Commands](#basic-hero-mdbook-commands)
 - [Install and Use Hero](#install-and-use-hero)
 - [Create a New mdBook](#create-a-new-mdbook)
-- [Notes for Repo Owners](#notes-for-repo-owners)
+- [Use Hero with Docker](#use-hero-with-docker)
+- [Contribute](#contribute)
+  - [Branches and Forks](#branches-and-forks)
+  - [Overview](#overview-1)
+  - [Content Update Procedure](#content-update-procedure)
 
 ## Overview
 
@@ -36,12 +40,49 @@ Once Hero is set on your machine, you can run the following commands to preview
 
 ## Install and Use Hero
 
+install hero as follows
+
+```bash
+curl https://raw.githubusercontent.com/freeflowuniverse/crystallib/development/scripts/installer_hero.sh | bash /tmp/hero_install.sh
+```
+
+you can also do it on a VM (experts only)
+
 To install and use Hero on a full VM running on the grid, read the [full VM guide](https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/docs/hero_mdbook_fullvm.md).
 
 ## Create a New mdBook 
 
 To create a new mdbook, read the [mdbook creation guide](https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/docs/hero_create_mdbook.md).
 
-## Notes for Repo Owners
+## Use Hero with Docker
 
-> todo: kristof some content does not belong here, move to other repo
+You can use Hero with Docker. Read the docs [here](https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/docs/hero_mdbook_docker.md).
+
+## Contribute
+
+To optimize updates to this repository, we propose a uniform way to collaborate.
+
+### Branches and Forks
+
+To contribute to this repository, make a pull request of your changes. There are two main methods.
+
+1. Fork the repository and make a pull requests with your changes
+2. If you have access, create a new branch in this repo and make a pull request with your changes
+
+### Overview
+
+- The production-ready content is published on the **main** branch
+- The staging content is published on the **development** branch
+- Any changes to development must go through a pull request (PR) and its associated review from a different branch with the prefix `development_`. 
+  - The name of the branch should indicate the work being done, e.g. working on the readme, `development_readme_work`
+- Once staging is done on development, the code owners will merge development branch to main branch.
+  - The mdbooks will be updated online.
+
+### Content Update Procedure
+
+- Create new branch out of development (e.g. `development_work`)
+- Make changes to the files
+- Make a PR to merge to development
+  - Get reviewed and adjust accordingly
+- PR is approved and the content is merged to development
+- Code owners will merge development to main to update the books online

_archive/technology/concepts/img/.done

@@ -0,0 +1 @@
+tft.png