Release Readiness

[jaredmorgs]

Just opening a thread to track status. Unless there's a better way, I figured a thread with a terse summary of remaining tasks could help watchers keep tabs.

We could set milestones, but I gather you guys are so close to release that a running list might be easier.

When you consider it ready for release, I'll fork it and do a real life test following the readme.

Thoughts?

[johncarl81]

Cool. Here's the todo list:

• [x] README.adoc
  • [x] Welcome content (explain project, etc)
  • [x] Instructions to get started
• [x] LICENSE (MIT)
• [x] Starting point CSS
  • [x] Foundation
  • [x] Coderay
  • [x] Asciidoctor default
• [x] Blog content
  • [x] Home page with next steps
  • [x] Example blog post

Here's the PRs:

• [x] #3 Rake-jekyll
• [x] #5 Update config to ruby 2.2.0 for Travis
• [x] #6 Foundation css and content
• [x] #8 README updates

[jirutka]

Why Apache License? Asciidoctor and related stuff are licensed under MIT license.

[johncarl81]

Not all of the Asciidoctor libraries are licensed under MIT. That being said, jekyll-asciidoc is under the MIT license, so I'll follow that. Thanks for pointing that out @jirutka.

[johncarl81]

Looks like we're getting pretty close. I went ahead and rebased and created a couple of sites off of this quickstart: http://androidtransfuse.org http://parceler.org http://johncarl81.github.io

Would appreciate feedback.