doc update structure

docs/repository-setup.md

@@ -0,0 +1,42 @@
+# Repository setup
+
+Either create a repository on your prefered platform and clone it or create one locally.
+This repository will contain two main elements, dotdrop's config file (`config.yaml`)
+and a directory containing all your dotfiles managed by dotdrop.
+```bash
+## clone your repository (my-dotfiles)
+$ git clone <some-url>/my-dotfiles
+$ cd my-dotfiles
+
+## within the repository create a directory to store your dotfiles
+## (refered by "dotpath" in the config, which defaults to "dotfiles")
+$ mkdir dotfiles
+```
+
+Then add a config file. You can get a
+[minimal config file](https://github.com/deadc0de6/dotdrop/blob/master/config.yaml)
+from dotdrop's repository with
+```bash
+$ wget https://raw.githubusercontent.com/deadc0de6/dotdrop/master/config.yaml
+```
+It is recommended to store your config file directly within your repository
+(*my-dotfiles* in the example above) but you could save it in different places if you wish,
+see [config location](config.md#location) for more.
+
+```bash
+$ tree my-dotfiles
+my-dotfiles
+├── config.yaml
+└── dotfiles
+```
+
+If your config file is in an exotic location, you can add an alias
+in your preferred shell to call dotdrop with the config file path argument.
+```
+alias dotdrop='dotdrop --cfg=<path-to-your-config.yaml>'
+```
+
+For more info on the config file format, see [the config doc](config.md).
+
+Finally start using dotdrop with `dotdrop --help`. See the [usage doc](usage.md)
+and [the example](https://github.com/deadc0de6/dotdrop/blob/master/README.md#getting-started).