diff --git a/index.html.markdown b/index.html.markdown
new file mode 100644
index 0000000..82e0fb5
--- /dev/null
+++ b/index.html.markdown
@@ -0,0 +1,36 @@
+---
+layout: default
+title: "Jasmine: BDD for Javascript"
+---
+
+# BDD for your JavaScript
+
+Jasmine is a behavior-driven development framework for testing your JavaScript code. It does not depend on any other
+JavaScript frameworks. It does not require a DOM. And it has a clean, obvious syntax so that you can easily write tests.
+
+{% highlight javascript %}
+describe("Jasmine", function() {
+ it("makes testing JavaScript awesome!", function() {
+ expect(yourCode).toBeLotsBetter();
+ });
+});
+{% endhighlight %}
+
+## Adding Jasmine to your Rails project
+
+{% highlight sh %}
+ $ gem install jasmine
+ $ script/generate jasmine
+ $ rake spec
+{% endhighlight %}
+
+Jasmine can be run by on a static web page, on your Continuous Integration environment, or with [node.js](http://nodejs.org).
+See more in the documentation.
+
+## Support
+
+__Discussion:__ [Google Group](http://groups.google.com/group/jasmine-js)
+__Group email:__ [jasmine-js@googlegroups.com](mailto:jasmine-js@googlegroups.com)
+__Current Build Status:__ [Jasmine at Pivotal Labs CI](http://ci.pivotallabs.com)
+__Project Backlog:__ [Jasmine on Pivotal Tracker](http://www.pivotaltracker.com/projects/10606)
+__Twitter:__ [@JasmineBDD](http://twitter.com/JasmineBDD)
\ No newline at end of file
diff --git a/matchers.md b/matchers.md
new file mode 100644
index 0000000..48050dd
--- /dev/null
+++ b/matchers.md
@@ -0,0 +1,4 @@
+---
+ layout: default
+ title: Jasmine Matchers
+---
diff --git a/release-notes.html.markdown b/release-notes.html.markdown
index 1b8fa3c..fe581f2 100644
--- a/release-notes.html.markdown
+++ b/release-notes.html.markdown
@@ -2,100 +2,99 @@
layout: default
title: Jasmine Release Notes
---
-
Release Notes
-
+# Release Notes
-
-
Release 1.0 — September 14, 2010
-
Jasmine Core
+-----
+## Release 1.0 — September 14, 2010
+-----
-
Features
-
-
waitsFor() arguments can now be specified in any order. Timeout and message are optional.
-
The default waitsFor() timeout period is now specified in env.defaultTimeoutInterval; the default value is 5 seconds.
-
Added link to jasmine site from html runner.
-
Added license file to standalone distribution.
-
New friendly version number.
-
+### Jasmine Core
-
Bugs fixed:
-
-
waitsFor() hanged forever if latch function never returned true.
-
The not.toThrow() matcher threw an exception when used with no args.
-
The toThrow() matcher, when inverted, gave misleading failure messages.
-
Spy matchers, when inverted, gave misleading failure messages.
-
+#### Features
+
+
waitsFor() arguments can now be specified in any order. Timeout and message are optional.
+
The default waitsFor() timeout period is now specified in env.defaultTimeoutInterval; the default value is 5 seconds.
+
Added link to jasmine site from html runner.
+
Added license file to standalone distribution.
+
New friendly version number.
+
-
Deprecations
-
-
Deprecated waits() block in favor of waitsFor(); waits() will be removed in a future release.
-
Deprecated toNotBe(), toNotEqual(), toNotMatch(), and toNotContain() matchers; they will be removed in a future release.
-
Console X was removed from the distribution as it was no longer used.
-
To give us some flexibility for future features, wrapped matcher functions now return undefined (they previously returned true or false, but this was undocumented).
-
+#### Bugs fixed
+
+
waitsFor() hanged forever if latch function never returned true.
+
The not.toThrow() matcher threw an exception when used with no args.
+
The toThrow() matcher, when inverted, gave misleading failure messages.
+
Spy matchers, when inverted, gave misleading failure messages.
+
-
Jasmine Gem
-
Features
-
-
Jasmine now supports JRuby.
-
Jasmine now supports Ruby 1.9.
-
+#### Deprecations
+
+
Deprecated waits() block in favor of waitsFor(); waits() will be removed in a future release.
+
Deprecated toNotBe(), toNotEqual(), toNotMatch(), and toNotContain() matchers; they will be removed in a future release.
+
Console X was removed from the distribution as it was no longer used.
+
To give us some flexibility for future features, wrapped matcher functions now return undefined (they previously returned true or false, but this was undocumented).
+
-
Bugs fixed:
-
-
Various generator issues fixed.
-
+### Jasmine Gem
-
Known issues:
-
-
Rails 3 and RSpec 2 are not yet fully supported.
-
-
+#### Features
+
+
Jasmine now supports JRuby.
+
Jasmine now supports Ruby 1.9.
+
+#### Bugs fixed
+
+
Various generator issues fixed.
+
-
-
Release 0.11.1 — June 25, 2010
-
Jasmine Core
+#### Known issues
+
+
Rails 3 and RSpec 2 are not yet fully supported.
+
-
Features
-
-
Jasmine no longer logs "Jasmine Running…" messages to the log by default. This can be enabled in runner.html by adding 'trivialReporter.logRunningSpecs = true;'.
-
The wasCalled(), wasCalledWith(), wasNotCalled() and wasNotCalledWith() matchers have been deprecated. The new matchers toHaveBeenCalled() and toHaveBeenCalledWith() have been added. You can use the not prefix to achieve equivalent of the wasNot…() expectation (e.g. not.toHaveBeenCalled()).
-
+-----
+## Release 0.11.1 — June 25, 2010
+-----
-
Jasmine no longer logs "Jasmine Running…" messages to the log by default. This can be enabled in runner.html by adding 'trivialReporter.logRunningSpecs = true;'.
+
The wasCalled(), wasCalledWith(), wasNotCalled() and wasNotCalledWith() matchers have been deprecated. The new matchers toHaveBeenCalled() and toHaveBeenCalledWith() have been added. You can use the not prefix to achieve equivalent of the wasNot…() expectation (e.g. not.toHaveBeenCalled()).
The version number has been removed from the generated single-file /lib/jasmine.js. We're also now uploading this file, with the version number in the filename, to github's Downloads page.
-
Old-style matchers (those using this.report(), from before 0.10.x) are no longer supported. See the README for instructions on writing new-style matchers.
-
jasmine.log pretty-prints its parameters to the spec's output.
-
Jasmine no longer depends on 'window'.
-
HTML runner should show number of passes/fails by spec, not expectation.
If multiple beforeEach blocks were declared, they were executed in reverse order.
-
Specs with duplicate names confused TrivialReporter output.
-
Errors in describe functions caused later tests to be weirdly nested.
-
Nested specs weren't reported properly by the JsApiReporter.
-
+#### Features
+
+
The version number has been removed from the generated single-file /lib/jasmine.js. We're also now uploading this file, with the version number in the filename, to github's Downloads page.
+
Old-style matchers (those using this.report(), from before 0.10.x) are no longer supported. See the README for instructions on writing new-style matchers.
+
jasmine.log pretty-prints its parameters to the spec's output.
+
Jasmine no longer depends on 'window'.
+
HTML runner should show number of passes/fails by spec, not expectation.
+
Small modification to JsApiReporter data format.
+
-
Known issues:
-
-
If you turn on the mock clock, you'll get a spurious log message at the end of your spec.
-
-
-
+#### Bugs fixed:
+
+
If multiple beforeEach blocks were declared, they were executed in reverse order.
+
Specs with duplicate names confused TrivialReporter output.
+
Errors in describe functions caused later tests to be weirdly nested.
+
Nested specs weren't reported properly by the JsApiReporter.
+
+
+#### Known issues:
+
+
If you turn on the mock clock, you'll get a spurious log message at the end of your spec.
+
diff --git a/spies.html.md b/spies.html.md
new file mode 100644
index 0000000..c203350
--- /dev/null
+++ b/spies.html.md
@@ -0,0 +1,4 @@
+---
+ layout: default
+ title: Jasmine Spies
+---
diff --git a/suites-and-specs.html.md b/suites-and-specs.html.md
new file mode 100644
index 0000000..42537a9
--- /dev/null
+++ b/suites-and-specs.html.md
@@ -0,0 +1,4 @@
+---
+ layout: default
+ title: Jasmine Suites & Specs
+---
diff --git a/user-guide.html.markdown b/user-guide.html.markdown
index 1d39d74..b9adcec 100644
--- a/user-guide.html.markdown
+++ b/user-guide.html.markdown
@@ -2,24 +2,21 @@
layout: default
title: Jasmine User Guide
---
-=======
-Quick Start
-----------
+# Quick Start
-#### For JavaScript-only projects:
+## For JavaScript-only projects:
1. Get the latest standalone release from the [downloads page](index.html).
2. Open `SpecRunner.html` in your favorite browser.
-#### Other distributions:
+## Other distributions:
* For integration with the Ruby environment, including automated execution with Selenium, please use the [jasmine gem](http://github.com/pivotal/jasmine-gem).
-### Which Release Should I Use?
+# Which Release Should I Use?
Please use the latest version unless you have a good reason not to. Some of this documentation may not be applicable to older versions. Please see [Release Notes](release-notes.html) for change information.
-Why Another JavaScript TDD/BDD Framework?
------------
+# Why Another JavaScript TDD/BDD Framework?
There are some great JavaScript testing frameworks out there already, so why did we write another?
@@ -27,33 +24,31 @@ None of the existing frameworks quite worked the way we wanted. Many only work f
So we decided to start from scratch.
-Enter Jasmine
-------------
+# Enter Jasmine
Jasmine is our dream JavaScript testing framework. It's heavily influenced by, and borrows the best parts of, ScrewUnit, JSSpec, [JSpec](http://github.com/visionmedia/jspec/tree/master), and of course RSpec.
Jasmine was designed with a few principles in mind. We believe that a good JavaScript testing framework:
-* should not be tied to any browser, framework, platform, or host language.
-* should have idiomatic and unsurprising syntax.
-* should work anywhere JavaScript can run, including browsers, servers, phones, etc.
-* shouldn't intrude in your application's territory (e.g. by cluttering the global namespace).
-* should play well with IDEs (e.g. test code should pass static analysis).
+ * should not be tied to any browser, framework, platform, or host language.
+ * should have idiomatic and unsurprising syntax.
+ * should work anywhere JavaScript can run, including browsers, servers, phones, etc.
+ * shouldn't intrude in your application's territory (e.g. by cluttering the global namespace).
+ * should play well with IDEs (e.g. test code should pass static analysis).
Some of our goals while writing Jasmine:
-* it should encourage good testing practices.
-* it should integrate easily with continuous build systems.
-* it should be simple to get started with.
+ * it should encourage good testing practices.
+ * it should integrate easily with continuous build systems.
+ * it should be simple to get started with.
The result is Jasmine, and we love test-driving our code with it. Enjoy.
-How To
-------
+# How To
There is a simple example of how to use Jasmine in the /example directory, but here's more information.
-### Specs
+## Specs
Each spec is, naturally, a JavaScript function. You tell Jasmine about a spec with a call to `it()` with a description string and the function. The string is a description of a behavior that you want your production code to exhibit; it should be meaningful to you when reading a report.
@@ -62,7 +57,7 @@ Each spec is, naturally, a JavaScript function. You tell Jasmine about a spec w
foo++;
});
-### Expectations
+## Expectations
Within your spec you will express expectations about the behavior of your application code. This is done using the `expect()` function and any of various expectation matchers, like this:
@@ -75,7 +70,7 @@ Within your spec you will express expectations about the behavior of your applic
Results of the expectations will be reported to you when the spec is run.
-#### Expectation Matchers
+### Expectation Matchers
Jasmine has several built-in matchers. Here are a few:
-