See Ruby one point nine.

It is written here: https://github.com/slash-lang/slash

I don't understand how you switch from “wow, guy wrote a language I can use in my projects” to “why should I switch from PHP, I need a more compelling reason” and stuff.

And yeah, PHP sucks. And your career path is something you should not think about at all.

Wiki doesn’t download with your repo. I think that’s the reason.

I don’t know. I just don’t feel approriate to use Wiki for projects that are smaller than 6000 LOC, I don’t know.

Maybe you’re right.

You can always put the wiki as a submodule in the git repo since the github wikis are just git repos too:

git clone git@github.com:whatever/whatever.wiki.git

And what is the format of Wiki pages?

GitHub uses Gollum [1] for wikis.

[1]: https://github.com/gollum/gollum/wiki

Because it is not designed for this purpose?

Sure! You’ve got the idea.

Not really far-fetched. Look at Sinatra README for example: https://github.com/sinatra/sinatra

There are 11 versions of Sinatra’s README which don’t share any general templates. They should be manually edited after each release. This is kind of thing that needs automatization.

Plus, it is much easier to inject badges by a mixin, not by copypasting and manually changing some elements from your old READMEs.

Good point about those many versions. It's actually the first time that I've seen multiple READMEs in one project.

Zero configuration (no config.rb), a lot of preprocessors besides Sass/Compass supported (like LESS, HAML, Slim, CoffeeScript and so on).

Not really.

Yep, fixed now. Thanks.