Jasmine doc site

1. Fork the repo
2. Create your feature branch (git checkout -b my-new-docs)
3. Ensure ruby and bundler (gem install bundler) are installed
4. Install ruby dependencies (bundle)
5. You can install them in the local folder, instead of globally for the system with (bundle install --path vendor/bundle)
6. Install JS dependencies (npm install)

You're ready to make some changes to the documentation!

.
├── _api/                   # Auto-generated API documentation - don't edit by hand!
├── _faq/                   # Various FAQ pages
├── _includes/              # Jekyll snippets (headers, footers, etc.)
├── _layouts/               # Jekyll layouts (overall page structure)
├── _tutorials/             # Tutorials / How-to Articles
│   ├── src/                # Docco source files for "side-by-side" tutorials
│   ├── *.html              # Auto-generated docco tutorials - don't by edit by hand!
│   ├── *.md                # Newer markdown tutorials
├── css/                    # Stylesheets (SCSS)
├── examples/               # Raw javascript examples of jasmine tests (rare)
├── pages/                  # Various documentation pages

Note the auto-generated files _api/** and _tutorials/*.html, don't edit these files as any changes you make to them will be lost the next time the documentation is generated.

First, update the jasmine API docs:

• Update local copies of jasmine using bundle exec rake update_edge_jasmine bundle exec rake update_edge_jasmine_npm, and/or bundle exec rake update_edge_jasmine_browser as appropriate
• Run npm run jsdoc to update the API documentation

Then, regenerate the tutorials:

• bundle exec rake tutorials

Now preview your changes locally:

• bundle exec rake serve

• Update the edge API docs as described in the previous section
• Copy the edge docs to the new version for each package, e.g. cp -r _api/edge _api/4.4
• Set the sort key in _api/<new version>/global.html>, _npm-api/Jasmine.html, and/or _browser-runner-api/module-jasmine-browser-runner.html. The sort key should be a string with three digits for the major and minor versions, e.g. "004.003" for version 4.3.
• If the new version is a prerelease (e.g. alpha, beta), add a prereleaseFor tag (e.g. prereleaseFor: "5.0") to every generated HTML page for the new version. This will prevent it from being treated as the current version and add the correct banner to each page.
• Archive the oldest non-archived version by adding archived: true to _api/<old version>/global.html>, _npm-api/Jasmine.html, and/or _browser-runner-api/module-jasmine-browser-runner.html. This will remove the version from the listing on the docs home page. It will still be published at the same URLs and can still be reached through the Archived Documentation link.

• Commit your changes (git commit -am 'Add some docs')
• Push to the branch (git push origin my-new-docs)
• Create new Pull Request

If you're making complicated or potentially controversial changes to the documentation, it may make sense to provide a live demo that the reviewer can use to compare side-by-side with the current production site.

From the terminal in your local fork of jasmine.github.io, create the branch gh-pages:

• git checkout master
• git checkout -b gh-pages
• git push -u origin HEAD

Next, enable GitHub Pages for your fork:

• Open your browser and navigate to your fork in GitHub
• Click the Settings link
• Under the GitHub Pages header, select Source -> gh-pages branch
• The page will reload. Wait a few minutes, then click the link provided
• You now have a personal live demo under https://<username>.github.io/jasmine.github.io/

Now that you've configured your live demo link to show the gh-pages branch, you can update what is shown at any time by resetting that branch to your newest changes. For example, if you've just pushed up the branch my-complicated-change, update your live demo by entering the following in your terminal:

• git checkout gh-pages
• git reset --hard my-complicated-change
• git push -f

Wait a few minutes, and you live demo will now be showing your changes in the my-complicated-change branch. You can then include a link to the demo in your pull request.