README.md in mtif-0.0.1 vs README.md in mtif-0.0.2

@@ -1,8 +1,8 @@
 # MTIF
 
-A gem to read Movable Type Import Format
+A gem to read Movable Type Import Format, as documented at [TypePad.org](https://movabletype.org/documentation/appendices/import-export-format.html) and also in the [Wayback Machine](https://web.archive.org/web/20210105063407/https://movabletype.org/documentation/appendices/import-export-format.html)
 
 ## Installation
 
 Add this line to your application's Gemfile:
 
@@ -18,12 +18,23 @@
 
     $ gem install mtif
 
 ## Usage
 
+Boy, it'd be smart to put something here. One day I will. Or maybe you will? See "Contributing" below.
 
-
 ## Contributing
+
+[![Build Status](https://travis-ci.org/purp/mtif.svg?branch=master)](https://travis-ci.org/purp/mtif) [![Maintainability](https://api.codeclimate.com/v1/badges/a52b50316f369a5baa8f/maintainability)](https://codeclimate.com/github/purp/mtif/maintainability) [![Test Coverage](https://api.codeclimate.com/v1/badges/a52b50316f369a5baa8f/test_coverage)](https://codeclimate.com/github/purp/mtif/test_coverage)
+
+Looking to get involved but don't have a particular itch to scratch? There are plenty of other ways to help!
+
+* A bit of documentation
+* A tutorial to help someone else along
+* More test coverage
+* Improving the overall code health by addressing Code Climate issues
+
+Meanwhile, you can get started the usual way:
 
 1. Fork it ( https://github.com/[my-github-username]/mtif/fork )
 2. Create your feature branch (`git checkout -b my-new-feature`)
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)