The README contains almost zero information as to why the project was created, which problems it aims to rectify, and why you might want to use it. That this information may or may not be contained in an embedded video is of no relevance to someone (like myself) who has neither the time nor ability at this particular moment to watch anything on video that could have been more succinctly explained in 2-3 sentences. It won't be bookmarked or favorited for later perusal -- just ignored.
Please understand I mean this as constructively as possible: it's hard to create something and share it with the world, and for that your efforts are most highly commended. I suggest adding a general introduction/description and some use cases to both the project site and README file. That will go a long way toward garnering the attention of those who might otherwise simply shrug and walk away.
https://github.com/freshshell/fresh/commit/4ebf599aa61b54b66... and https://github.com/freshshell/fresh/commit/000d7ce00b9029881...
For example, @twe4ked uses my tmux configuration but also has his own additions using the following:
fresh jasoncodes/dotfiles tmux.conf --file
fresh config/tmux.conf --fileYour webpage doesn't have any explanation other than a video. I can read a paragraph or two in a couple of seconds--I'm not going to take a minute and a half (and stop listening to the music I'm listening to) to watch a video. The GitHub README doesn't really have any information about what it is either.
I haven't actually tried this, because I have no idea what it is. The other comment in here linked to an example .freshrc file--I noted that every line that's not a comment starts with the string 'fresh ', which seems like an obvious annoyance. Even if you want it to just be a shell script you can execute, you could support a batch mode to do something like this, for example:
fresh batch <<'BATCH'
config/vimrc --file
config/gemrc --file
config/pryrc --file
BATCHWe will add some more info to the home page but we were trying to keep most of the info in the README.
> The GitHub README doesn't really have any information about what it is either.
What else would you like to know?
The batch mode is a good idea, however the way we're doing it is a tried and true method used by many dev tools Bundler, Vundle, etc.
Edit: I don't mean to discourage you, by the way. The more variety in dotfile management the better.
[1]: http://bugsplat.info/2012-08-11-task-oriented-dotfiles.html
One of fresh's major features is being able to source a subset of another's dotfiles (at a per file level). For example, in my office we are all using fresh to source common git aliases.
This module/task idea is certainly interesting and is something we have been thinking about. Thanks for your feedback.
Edit: woops it was already a ticket, closed mine.