Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

SproutCore Guides

These are the official guides for the SproutCore framework. You can see them live at the SproutCore Guides homepage.

This document contains a brief overview of how to contribute changes and additioins to the SproutCore Guides. For an in-depth explanation, see the Contributing Guide.

Getting the Source Code

  1. Fork the SproutCore Guides repository on GitHub.

  2. Clone the fork on to your local machine.

    $ git clone git://<yourname>/guides.git
  3. Add the main SproutCore Guides repository as a remote so you can fetch updates.

    $ cd guides
    $ git remote add upstream git://

Installing Prerequisites

The SproutCore guides use the Node-powered DocPad framework. In order to contribute to the guides, you will first need to install Node from

Next, install the docpad framework (note: you may need to use sudo for this):

$ npm install -g docpad

Finally, change into the guides directory and install the necessary development dependencies:

$ cd ~/my/dev/directory/sproutcore/guides
$ npm install

You should see a plethora of output similar to the following:

npm http 304
npm http 304
npm http 304
npm http 304
npm http 304
npm http 304
npm http 304

Before Making Changes

Before you make any changes, you'll want to pull in any upstream changes and create a new topic branch for your changes.

$ git checkout master
$ git pull
$ git checkout -b <branchname>

Create the Avatar Cache

Our sproutdown plugin will attempt to cache the avatars so that we do not hit GitHub more than necessary. Run the following command to initialize the file.

echo '{}' > plugins/sproutdown/src/.avatar_cache.json

Creating or Modifying a Guide

Guides reside in the src directory and are written in a modified version of the Markdown markup language. The best way to familiarize yourself with how to use Markdown is to check out the other guides.

Docpad makes it easy to see what the guides on your local machine will look like when they're published to To preview your changes, run the following command from the guides directory:

$ docpad run

Now point a web browser to localhost:9778. This preview will keep itself updated as you make changes to the guides; all you have to do is refresh your browser window to see your latest changes.

Submitting Your Changes

You can get your changes and additions included by creating a pull request on GitHub using the topic branch you created above.

Deploying a Release

In order to deploy a release, you'll need to have the repository checked out into a local directory. All you need to do is use DocPad to generate the guides, copy that to the checked out live repo and then commit and push. It should looks something like this:

cd ../
git status
git commit -am "New release of guides..."
git push

More Information

For more information on the SproutCore Guides, including a more in depth look at committing your additions and changes, see the contributing guide.

If you have any questions, the team can be reached at @sproutcore on Twitter, in the #sproutcore IRC channel on Freenode, or at the SproutCore Google Group.