-
Notifications
You must be signed in to change notification settings - Fork 7
Description
Issue summary
Decrease the barrier for entry to use by having a folder of common example tasks;
- Installing homebrew
- Installing global node modules
- etc.
After reading the README back, it doesn't feel instantly easy to pick up and use, maybe show an example task within the README showing how easy it is to create a task for kody to pick up.
Also, link to personal set ups. For example; github.com/jh3y/kody_env has my personal tasks for doing various things like running shell scripts etc.
There is potential to raise awareness of kody and make it a go to solution for maintaining dotfiles. It has been picked up and shown on different blogging platforms but I still feel the barrier to entry may be holding it back.
Expected behavior
User should feel at ease to give kody a spin and not think about passing it up because it's too much overhead to get started.
Actual behavior
It's not super intuitive or doesn't come across as something that can be just picked up quick without major knowledge.
Steps to reproduce
Read the README as if you've never heard of kody or .files.
Resolution
Improve the README so that kody is easier to pick up and get going. Add examples into the repo so potential users can see how easy it is to get started with kody.