Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 44 lines (27 sloc) 2.105 kB
41a924d @qrush Updating readme
qrush authored
1 # Git Ready
2
faa8008 @qrush Adding breaks and fixing some issues with the readme.
qrush authored
3 > There is only one way to *get ready* for immortality, and that is to love<br />
4 > this life and live it as bravely and faithfully and cheerfully as we can.<br />
f4b24b1 @qrush Funny enough, I used git add . on the interactive adding post.
qrush authored
5 > ~ Henry Van Dyke
948c719 @qrush Initial commit
qrush authored
6
41a924d @qrush Updating readme
qrush authored
7 ## About
8
faa8008 @qrush Adding breaks and fixing some issues with the readme.
qrush authored
9 This repository hosts the HTML, CSS, images, and posts for [gitready.com](http://gitready.com)<br />
0cfa75c @qrush Updating README and adding MIT license for the code
qrush authored
10 Git Ready publishes (was daily, then tri-weekly, and now) weekly tips for those who want to learn more about the VCS or just get started.<br />
11 The blog as a whole started as a journey to learn more about Git and show others how useful it is. If you find issues with the content, just send [qrush a message on GitHub](http://github.com/qrush) or email him at [nick@quaran.to](mailto://nick@quaran.to).
41a924d @qrush Updating readme
qrush authored
12
13 ## Publishing
14
0cfa75c @qrush Updating README and adding MIT license for the code
qrush authored
15 This blog is generated with the [Jekyll](http://github.com/mojombo/jekyll) engine.<br />
41a924d @qrush Updating readme
qrush authored
16 Simple and easy formatting that sticks to the basics. All static HTML too, so worrying about scalability is non-existent.
17
18 ## Contributing
19
faa8008 @qrush Adding breaks and fixing some issues with the readme.
qrush authored
20 If you have ideas about new pages, layouts, or what have you, fork away!<br />
5cf6973 @qrush Phoning this one in
qrush authored
21 If you want to submit tips, [please do so here](http://gitready.com/submit.html).
41a924d @qrush Updating readme
qrush authored
22
23 ## Translating
24
25 If you are interested in translating posts into another language, great! Here's what to do:
26
27 * Fork the project.
28 * Create a branch with the ISO code for your language
0cfa75c @qrush Updating README and adding MIT license for the code
qrush authored
29 * Translate the front page headers, footers. Check out the other translated sites for an example, such as the [german one](http://de.gitready.com).
41a924d @qrush Updating readme
qrush authored
30 * Translate as little or as many posts as you so desire.
31 * The posts that aren't translated, add this to the YAML front matter (this way, untranslated posts don't show up):
32
faa8008 @qrush Adding breaks and fixing some issues with the readme.
qrush authored
33 published: false
41a924d @qrush Updating readme
qrush authored
34
faa8008 @qrush Adding breaks and fixing some issues with the readme.
qrush authored
35 * Submit a pull request to the main repository.
41a924d @qrush Updating readme
qrush authored
36
37 Once that's done, I'll add your language's subdomain and get it published.
f4b24b1 @qrush Funny enough, I used git add . on the interactive adding post.
qrush authored
38
0cfa75c @qrush Updating README and adding MIT license for the code
qrush authored
39 ## Licensing
40
41 The actual content of the articles is licensed under Creative Commons. The code that this project consists of is licensed under MIT.
42
43 Basically, if you're going to redistribute a blog post, just make sure to link back. If you'd like to publish the content, that's fine too, just please keep the licensing information in.
Something went wrong with that request. Please try again.